Community:Collections and Metadata/TransformCases
From NSDLWiki
Use cases: Native metadata harvest, crosswalking, safe and collection-specific transformations, NSDL gold metadata
Use Case 1. Provider “F” is identified by NSDL Collection Developers as a relevant and useful addition to the library. A collection record is created in the CRS and harvest is initiated. Provider “F” exposes oai_dc and MARC records, and according to policy, NSDL harvests both formats for the MR. The long-suffering metadata specialist receives an email reporting the successful initial harvest and the location of csv files for the harvested metadata. Using Spotfire, she examines the files quickly and determines that the oai_dc files are very sparse, but the MARC files have exploitable information that would be useful to improve access to the resources of Provider “F.” Using a standard MARC crosswalk stored for this purpose, she initiates a transformation of the MARC file into nsdl_dc and examines the results quickly using Spotfire to assure that the appropriate elements are populated and the values appropriate. Lastly, she initiates an NSDL standard “safe” transform process (in this case primarily to associate standard encoding schemes with appropriate values) and approves the loading of the newly transformed data into the MR. NSDL then exposes the additional nsdl_dc format, along with the providers supplied oai_dc and MARC, via the NSDL OAI server. Additionally, the nsdl_dc elements become available via the augmented formats: nsdl_mudball and nsdl_gold.
Use Case 2. Provider “H” self-registers via the CRS, creates an initial collection record and initiates a harvest of metadata. Because this is an initial harvest, the long-suffering metadata specialist receives and email notification. She updates the collection record, and quickly examines the csv files for the two of the three harvested formats: nsdl_dc and ieee_lom. She notes that the crosswalk used by the data provider to move data from ieee_lom to nsdl_dc incorrectly interpreted “Type” and “Format,” so that the values, though correct, appear in the wrong element. She calls up a form to create a collection specific transform for that collection, to reverse the values in each element and add the appropriate encoding scheme. Since no other serious errors appear, she invokes the safe transformation and approves the data for the MR. She sends a notification to the provider, pointing out the error, and asking him to inform her when the error is corrected so that she can pull the collection-specific transform when the data can be correctly harvested.
Use Case 3: Provider “K” is identified by an approved NSDL Recommender as an appropriate collection for the NSDL. The Recommender creates a collection record, and through the CRS initiates a first harvest. Provider “K” exposes oai_dc and a new metadata format specialized for science museums that the MR has not yet encountered. The Metadata Empress receives notification that this new format has been harvested, and the schema provided allows the creation of a csv file so that the data can be reviewed. The schema also supports the creation of a crosswalk worksheet, allowing the Empress to set up a crosswalk from the richer format to nsdl_dc. When the crosswalk is completed, the data is transformed and made available through the NSDL OAI server, and the crosswalk itself is posted to the NSDL approved crosswalks page, for specific reference in the “about” data in the crosswalked records and for use by others. The provider is also notified about the presence of the crosswalk, and invited to comment or suggest improvements.
Use Case 4. Provider “S,” a long time NSDL data provider, makes substantive changes to their “metadata profile” as stored by the CRS. The Metadata Empress is notified of these changes, and takes a look at the csv files to see how these changes would affect access to the Provider “S” collection. One of the changes is the addition of Audience values. The ME determines that the provider is not using the available NSDL vocabularies but a mix of other available vocabularies and unattributed terms. She sets up a collection-specific transform that crosswalks the non-NSDL standard vocabularies to NSDL vocabularies as well as a quick crosswalk from the unattributed terms to NSDL vocabulary. She also sets up an nsdl_gold profile for the provider, so that appropriate ratings are established for the range of terms available.
Use Case 5. A routine crawl for item metadata is initiated via the CRS after the completion of a collection record for a resource without available metadata. The iVia Service makes machine-generated metadata available for harvest by the NSDL. Because a rights statement applying to all the resources on the site is available, but the iVia Service does not reflect that in the items, a collection-specific transform is initiated for the collection, and the appropriate statement is defaulted in the Rights element for the items.
