Post-Ingest Aleph Workflows: Difference between revisions

From CJH Wiki
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
Required steps in Aleph after ingesting material into Rosetta. For information on how to add these fields to Aleph in a batch, [http://wiki.cjh.org/index.php/File:How_to_batch_add_a_field_containing_different_info_for_each_record.docx download this tutorial].
Required steps in Aleph after ingesting material into Rosetta. For information on how to add these fields to Aleph in a batch, [http://wiki.cjh.org/index.php/File:How_to_batch_add_a_field_containing_different_info_for_each_record.docx download this tutorial].


== Add Two Fields to Record ==
If you are synchronizing a Rosetta record with Aleph, do NOT use the system number for a collection-level EAD record. The synchronization does not add fields, rather it replaces the entire Dublin Core record in Rosetta with the record coming out of Aleph. This means that a collection-level system number will replace the specific folder name with collection-level metadata.
 
== Add Two Fields to Aleph Record ==


=== Add 856 Link ===
=== Add 856 Link ===
Line 18: Line 20:
* $$a Y
* $$a Y
* $$b [Aleph System Number]
* $$b [Aleph System Number]
'''NOTE''': If you are synchronizing a Rosetta record with Aleph, do NOT use the system number for a collection-level EAD record. The synchronization does not add fields, rather it replaces the entire Dublin Core record in Rosetta with the record coming out of Aleph. This means that a collection-level system number will replace the specific folder name with collection-level metadata.

Revision as of 15:02, 13 November 2018

Required steps in Aleph after ingesting material into Rosetta. For information on how to add these fields to Aleph in a batch, download this tutorial.

If you are synchronizing a Rosetta record with Aleph, do NOT use the system number for a collection-level EAD record. The synchronization does not add fields, rather it replaces the entire Dublin Core record in Rosetta with the record coming out of Aleph. This means that a collection-level system number will replace the specific folder name with collection-level metadata.

Add Two Fields to Aleph Record

Add 856 Link

  • Field = 856
    • Indicators
      • ind1 = 4
      • ind2
        • ' ' = no information
        • '1' = digitized material
        • '0' = born-digital material
  • $$z Digital Form
  • $$u http://digipres.cjh.org:1801/delivery/DeliveryManagerServlet?dps_pid=[Insert IE PID Here]

Add ROS Field

  • Field = ROS
  • $$a Y
  • $$b [Aleph System Number]
Retrieved from "https://wiki.cjh.org/index.php?title=Post-Ingest_Aleph_Workflows&oldid=654"