How does Digital Collection Gateway identify records that need to be updated?
- Digital Collection Gateway
For a record to be flagged for an update by the Gateway when doing a complete sync, it must meet the following criteria:
- The 029 field of the existing record matches exactly to the record being harvested from your repository. Please note, if the URL in the existing record has http and the newly harvest record has https, this will not be considered a match and a duplicate record may be created.
- The record has an encoding level 3. If a record is enhanced through Connexion or Record Manager and the encoding level is updated, the record will be skipped.
- The record does not have holdings set through Connexion or Record Manager that are not the institution harvesting the records. If there are other holdings set through these processes, the record will be skipped.
Note: When the Gateway finds a matching record with an encoding level 3, enhancements that were made in Record Manager or Connexion will be overwritten. To prevent this from happening, the encoding level will need to be updated to something other than 3.