SIL_Workflow

Metadata transfer: SIL-IA and back.

Comparison of what metadata is being given to whom from where....
IA will take the MARC record (via Z39.50 metafetch) at time of scanning. The MARC record is included along
with all the other files, however, there are some other things we get back. Is it enough?




Some questions from Keri:

• Where is the scanner-generated metadata, e.g., resolution, pixels, etc. – is not in the JP2!!
• What if we don’t want all those CDL fields in our metadata file? What if we do?
• Can we get our entire MARC record, PLUS the enumchron field with the volume info if not the entire fetch file?
• How are we getting the QA data back? We might want to incorporate the metadata/bibliographic bits it into our picklist as reason for rejection e.g., fragile , marc data missing, etc.
• Where are we putting any rejection codes when item is rejected by the scanner? Are they coming back on paper or as part of a report?

What else do we need to collect in our ‘picklist’ database before we cycle data back into SIRIS?

• handle/guid?
• stable url
• boilerplate for 853 or note field or whatever???