Skip to main content

How to identify which amended records have been updated

Find out about identifying which amended records have been updated in the legacy CSV files and XML files.

Published: 3 January 2018

Version: 1.0

In the legacy CSV files, amended records are identified by a binary flag held in a field in the organisation record. For example, ‘1’ means it is new or has been amended since the last version was published and ‘0’ means it
is unchanged. Within the XML file amendments are conveyed through providing the date on which the record was last changed in any substantive way.

‘Substantive change’ is defined as any previously existing value being displaced by a new one, within any data item that is exposed to users, or the addition of any new item that was not previously present in the record. Brand new records show the date of their creation.

The date information is contained in an element tagged ‘LastChangeDate’ in the organisation component of the XML file. Within this element is an attribute tagged ‘value’ that contains a date in the format ccyy-mm-dd (2019-01-01 for the 1 January 2019).

This element can be used to identify new records, or have been amended prior to or up to a specific date. As an example, this could be used to isolate records that have been changed or created since a system was last refreshed with organisation data, such as where the most recent LastChangeDate value against any records in a system is 2018-03-31, select all records where LastChangeDate is equal to or later than 2018-04-01.

This approach allows updates to be made using only amended data, rather than replacing the entire organisation data set. It also allows updates to be easily performed on an ad-hoc basis, if required.

Last edited: 16 July 2019 2:02 pm