Skip to main content
OCLC Support

Criteria for new, update, delete and merged records (Fundamentals)

  1. Last updated
  2. Guardar como PDF
Transaction types are relevant to knowledge base collections. They help automate the maintenance of your records.

 Notes:

About

Files can be output in new, updates, or deletes folders on the server and therefore file names can have one of the following designations: New, updates, or deletes.

It is recommended that you process record files in date order.  When processing the files for a specific date, it is recommended that they are processed in the following order: Deletes, New, Merges, and Updates. See Download files in My Files and Download files with SFTP for more information.

Records in "New" files

The file of new records includes records for titles added to collections that have not previously been delivered via WorldShare Collection Manager Fundamentals (based on OCLC number).

You will receive a new record if an OCLC number is added to a title that did not previously have an OCLC number, and you will receive new records if a provider adds titles to a collection. 

Tenga en cuenta que no todos los títulos de la base de conocimientos de WorldCat tienen un registro de WorldCat o un número de OCLC correspondiente. Por lo tanto, es posible que reciba menos registros de los que están representados en la lista de títulos de la colección de la base de conocimientos.

Records in "Updates" files

Profile options define what types of changes trigger an updated record. Files of updated records can include records for titles in collections where there has been a change to knowledge base data, URL or proxy server data, or a change in a variable field in the WorldCat record.

When an OCLC control number changes, you will automatically receive an updated record. By default, the reason a record is updated will be included in your Updated Records record reports. See Reasons for updated records.

Including the reasons in your records is optional. If you would like the reasons in a field in your records, map in Customize Records, Add Fields the value "Reason for Updated Record."

Local holdings records (LHRs)

When enabling LHRs, you have the option to have a file of LHRs delivered, a file of LHRs and bibliographic records delivered, or a file of LHRs interleaved with bibliographic records delivered.

Updated records will be output if any associated LHR is deleted, added, or updated. You will receive an updated record and all associated LHRs, including those that have not been changed. This allows you to replace all LHRs for a record, without the need to figure out what has been changed.

Local bibliographic data (LBD)

When enabling LBD, you have the option to have local data embedded in or interleaved with your records. Changes to your LBD will trigger an updated bibliographic record.

Mejoras en el registro de WorldCat

Depending on your profile settings, changes to the WorldCat record data could trigger an updated record for any title in your collections or WorldCat holdings. You could receive an updated record for any change in the WorldCat record including:

  • Cuando se añade, actualiza o suprime una etiqueta MARC específica que usted ha elegido en el registro de WorldCat
  • Cuando un nivel de codificación cambia a un valor que ha elegido en su perfil
  • Cuando el registro ha sido actualizado a las reglas de catalogación RDA ("rda" se denota en el 040 $e)

Titles in knowledge base collections

If any of the collection-level or title-level metadata in the WorldCat knowledge base changes (such as a collection name, a collection note, coverage dates, and so forth) you will receive an updated record.

Records in "Merges" files

When two records are merged in WorldCat, Collection Manager will deliver an updated record if you have enabled MARC record delivery (regardless of whether or not you have enabled WorldCat updates).

Files of merged records will be delivered in a separate file that includes the word "merges" in the file name. If you enable the option for separate file delivery within a collection's record delivery settings, the file name will include both "merges" and the file name you defined.

All files of merged records will be delivered in Metadata > My Files. If you use file exchange, merged records will be in the Updates folder.

Example file of merged records (default):

metacoll.[XXX].merges.D20160829.T183013.1.mrc

Example file of merged records for a file with separate file delivery:

metacoll.[XXX].merges.D20160829.T183013.YourFileName.1.mrc

Registros en "Borra los archivos de"

Eliminar registros incluye sus personalizaciones. Los registros de un fichero de borrados son registros completos, como los de los ficheros de nuevos y actualizaciones, y se imprimen en un fichero aparte.

Los registros borrados contienen:

  • The record status code "d" in the leader
  • The URL from the last new or updated record that was delivered

Delete records will be triggered:

  • Para los títulos de las colecciones de la base de conocimientos a los que ya no tiene acceso, si no tiene acceso al título desde ningún otro proveedor (si tiene acceso desde varios proveedores y pierde el acceso desde uno solo, recibirá un registro actualizado para que sus enlaces en el registro sigan siendo actuales).

You have the option to select whether or not you want to receive delete records. The option will appear

  • If you turn off record delivery within the institution-level settings (Collection Manager Fundamentals > Institution Settings > MARC Records)
  • If you turn off record delivery within a collection's settings
  • If you remove a collection that had record delivery enabled