90 likes | 179 Views
Z39.87 at DCAPS Oya Rieger & Danielle Mericle Digital Media Group, DCAPS May 2005 CUL Metadata Forum. Images @ CUL. Managing Image Collections: Essential Layers of Information. IMLS DCC * Collection Registry. Collection attributes Project specifications Institutional profile. PREMIS
E N D
Z39.87 at DCAPSOya Rieger & Danielle MericleDigital Media Group, DCAPSMay 2005CUL Metadata Forum
Managing Image Collections: Essential Layers of Information IMLS DCC*Collection Registry • Collection attributes • Project specifications • Institutional profile PREMIS Preservation Metadata OAIS • Preservation metadata elements • Storing and managing metadata Z39.87 Basic Image Parameters Image Creation Image Performance Assessment Change History • Capture production metadata • Render images accurately • Support migration *Other examples include UKOLN Collection Description & DC Collection Description Profile
Implementing Z39.87 • General Policy Decisions • Does every project necessitate implementation? • Which elements are appropriate for a given collection (most are optional)? How much needs to be captured? • Challenges • New to the schema • Vocabulary--what does “YCbCrSubsampling” mean, anyway? • Fitting into overall workflow DCAPS Implementation Team: Marty Kurth, Danielle Mericle, Greg Nehler, Rick Silterra
Classics Department Kevin Clinton • Migrating an image collection of ancient Greek inscriptions from the Sanctuary of the Mysteries of Eleusis • 900 images to a Luna Collection. • Collection level metadata created using NISO MIX schema • Three different types of images • Kodak CD • Scanned In-house • Publication CD
Workflow • Start with sample MIX document • Pull Jhove records (image level data) • Eliminate variable information (for collection level records) • Annotate records (capturing information & eliminating any unnecessary fields) • Create xml files for each “image type” • Import xml into METS document
Challenges of Clinton Collection • Working with three different “image types” added complexity to the process- more information to gather and track • Issues associated with “Migrated Image” type • Unaware of original scanning set-up • Limitations to “change history” field- difficult to fully capture conversion method within this schema