How to update or delete movements
This file can be used to update or delete animal movement records in the NAIT system.
Your CSV file will need to include all of the column headings, in the correct order. This includes headings for optional columns you are leaving blank.
| Column | Heading | Format |
|---|---|---|
| A | Action Required | Enter Update or Delete |
| B | NAIT Transaction Identifier | The transaction identifier of the original movement upload. This will have been sent to you after the movement was created. |
| C | Sending NAIT Number | Must be a valid NAIT number. |
| D | Receiving NAIT Number | Must be a valid NAIT number. |
| E | NAIT RFID | This is the unique 16 character code that relates to the NAIT tag. This information is provided by tag manufacturers or can be read with a scanner. It does not have to be provided if a NAIT Visual ID is provided. Examples that will be accepted include: |
| 00000 0 982 000196588496 | ||
| 942 000002422333 | ||
| 982 000161531687 | ||
| 9.82E+14 | ||
| 0982 000190869343 | ||
| F | NAIT Visual Tag Number | This is the information printed on the outside of the tag. It does not have to be provided if a NAIT RFID is provided. The number must already be registered to an animal in order to update the animal's details. |
| Find out how to correctly enter NAIT Visual IDs | ||
| G | External Record ID | You can choose to enter a reference number of your own, e.g. 1, 2, 3, 4. This will make it easier for you to identify which record (row of your spreadsheet) is incorrect if you make a mistake in your CSV. |
| H | Previous Date Sent | The previous date sent when updating a sending movement. Leave this blank if you are updating a receiving movement. |
| Date information must be in a recognisable format, e.g. dd/mm/yyyy, dd/mm/yyyy hh:mm:ss, yyyy-mm-dd etc. | ||
| Please note any time component will not be stored in the database. | ||
| I | Updated Date Sent | The new date of a sending movement. Leave this blank if you are updating a receiving movement. |
| Date information must be in a recognisable format, e.g. dd/mm/yyyy, dd/mm/yyyy hh:mm:ss, yyyy-mm-dd etc. | ||
| Please note any time component will not be stored in the database. | ||
| J | Previous Date Received | The previous date received when updating a receiving movement. Leave this blank if you are updating a sending movement. |
| Date information must be in a recognisable format, e.g. dd/mm/yyyy, dd/mm/yyyy hh:mm:ss, yyyy-mm-dd etc. | ||
| Please note any time component will not be stored in the database. | ||
| K | Updated Date Received | The new date of a receiving movement. Leave this blank if you are updating a sending movement. |
| Date information must be in a recognisable format, e.g. dd/mm/yyyy, dd/mm/yyyy hh:mm:ss, yyyy-mm-dd etc. | ||
| Please note any time component will not be stored in the database. |