Oct 22, 2013 - Publisher creator- contrib author/creator subject subject rsrctype lds03. ldsXX ... system as a repositor
Rosetta DCMI-Burbia
Metadata Underground: Visualizing metadata transfers from repository to end-user
OAI-PMH Downtown
Search Midtown
dc:title
dc:relation
title
dc:description
addtitle
dc:source
in the title
Description
dcterms:hasFormat
Source
dc:description
Edward M. Corrado (
[email protected]) Rachel Jaffe (
[email protected])
Related Titles
IsPartOf
dcterms:isPartOf
dcterms:conformsTo
Dropdown Search Park
Title
dc:title
dc:relation
Display Uptown
dc:source
local digital collection searchscope
Creation Date
dc:date dc:date
Abstract: An increasing number of academic and research libraries are implementing discovery layers that search multiple systems such as integrated library systems and institutional repositories. Out of the view of the end-user, metadata travels within and between systems, like trains on the NYC subway. This poster session will provide librarians with an easy-to-use map illustrating the flow of metadata and its transformations, as it journeys to its final destination – the end-user's screen.
ldsXX
dc:publisher
publication date dcterms:modified
dc:creator
description
Publisher
dc:publisher Creator
Background: At Binghamton University Libraries we use the Rosetta digital preservation system as a repository to store and preserve digital objects. Rosetta does not have a builtin discovery layer; we use Primo as the primary means by which end-users are able to search and discover digital objects preserved in Rosetta (as well as items from the Libraries' integrated library system and the Primo Central Index). In order for Primo to make the digital objects in Rosetta discoverable, it is necessary for the descriptive metadata to be transferred from Rosetta to Primo. This is a multi-step process: 1. Rosetta needs to be configured to allow Primo to harvest the metadata 2. Primo harvests the metadata 3. Primo indexes the metadata 4. Primo creates display fields based on the metadata mapping tables The process is complicated by multiple factors. There are a limited number of locallydefined search and display fields in Primo. These fields need to accommodate metadata coming from multiple systems, in multiple formats. For example, the descriptive metadata in Rosetta is based on Dublin Core while the integrated library system uses MARC. Additionally, it is important to get by-in from various stakeholders within the library.
dc:contributor
dc:subject
dc:creator
Contributor
dc:contributor creation date
dc:type
dc:format
dc:subject
author/creator
Subject
Type
dc:type
subject dc:language
dc:rights
dc:format
lsrXX
Format
Language
dc:language
Legend Existing metadata route
dc:rightsHolder
Rights
dc:rights
Planned metadata route
creatorcontrib dc:provenance
dc:identifier
lds03
dc:rightsHolder
Provenance
dc:provenance subject
dc:coverage
notes
Qualified Dublin Core field Primo search field
Identifier
dc:identifier
Primo display field Coverage
dc:coverage
notes
Simple Dublin Core field
rsrctype
ldsXX
Primo dropdown search field
