Download presentation
Presentation is loading. Please wait.
Published byNathan Hamilton Modified over 6 years ago
1
Metadata Frameworks ADN - for online/offline resources
DLESE-IMS - for online resources Annotation - resource reviews, comments Collection - collection characteristics News-Opps - announcements NSDL-DC - NSDL’s own Dublin Core OAI-DC - Dublin Core supported by OAI
2
Annotation records Are the gatekeeper to the Reviewed Collection
Are the gatekeeper as to whether library users can read or contribute reviews Can exist without ADN records Can only have 1 annotation type per record Can capture the annotation in the record or send library user to a new site for the anno.
3
Collection records (1) Overall collection characteristics
Provides for DPC tracking of collections (key and metadata format) Indicates how a collection arrives at the DPC Is the collection OAI harvestable & the OAI info Is the collection generated at the DPC Is the collection ed
4
Collection records (2) Indicates if/how collections can be redistributed Info about item-level catalog record #’s Indicates super/sub/associated collections Can indicate ADL buckets for a collection Captures the additional info needed for NSDL Tracks accessioning and alignment with DLESE collection policies per requirement of the Collections Accessioning Taskforce
5
Purposely Blank
6
Script Processing Order
Illegal characters check Transform DLESE-IMS to ADN Validate ADN, Annotation or Collection Transform & validate ADN to Annotation Transform ADN to ADN with no cataloger Transform & validate ADN to NSDL-DC (1x on new Transform & validate ADN to OAI-DC (1x on new) Shell script to move records from library prep area to real library
7
Illegal Character Check
Uses a Python (2.0) script (badchars.py) invoked at the command line Characters greater than Unicode decimal 127 are considered invalid (e.g. ©) Works on directories of records Output indicates every record scanned and if bad characters are found, prints the line and line number
8
Transforms Changes metadata formats
Know semantic map between both frameworks before creating XSLT Uses XSLT 1.0 and Xerces 2.4.1 Uses shell script invoked at the command line Understand Spy and Xerces are different transformers (design envir. is different than operating envir.) Output indicates number of transformed records, number successful and remarks
9
Transforms supported (XSLTs)
DLESE-IMS 1.2 to ADN ADN to OAI-DC ADN to NSDL-DC 1.01 ADN to ADN cataloger out Namespace out - suppress record namespaces Collection specific transforms to create annotation records for various collections Collection specific transforms to get to ADN
10
Validation Uses XML Schema 1.0 and Xalan 2.4.1
Understand Spy and Xalan are different validators and act differently Use the metadata framework specified in each metadata record Uses shell script invoked at the command line Output gives total number of files scanned, number valid/invalid and invalid remarks
11
Record Locations Harvesting & gathering on several machines
Manipulations: quake: devel/ginger/work/ /adn, /dlese_anno, /collect, /dlese_ims, /adn_catout, /nsdl_dc, /oai Lib. prep (Idmapper): quake: devel/ginger/records /adn, /dlese_anno, /collect Real library: cutterjohn: webroot/records /adn, /dlese_anno Note: collection keys needed for subdirectories
12
Info Shared with Collection QA’er
Transform report - tend to be cryptic Validation report - tend to be cryptic Illegal character report Idmapper - link/dups report All are separate documents
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.