Guest Lecture: Exchange and QA for Metadata at WSU

04/18/2023

Exchange & Quality Control for Wayne State Metadata

Meghan FinchMetadata Librarian

Wayne State University

04/18/2023

Meghan Finch• Metadata and Digital Media Librarian• Started in March 2011 (8 months into the job)• Job description:

– Managing and contributing cataloging and metadata for archival and digital projects

– Creating Encoded Archival Description (EAD) finding aids and associated style sheets for archival collections.

– Working collaboratively with the Digital Library Initiative Team to describe digital objects and create metadata formats appropriate to various delivery platforms

– Participating in library teams and special projects related to cataloging, digital projects, and bibliographic control

– Converting and preparing metadata for Electronic Theses and Dissertations (ETD) for import to the digital repository

04/18/2023

Projects I’ve worked on, Tools I useElectronic theses and dissertations (ETDs)

altered existing XSLT to transform data from Proquest to bepress for ingestion in

contributed to shell script to automate production of bepress xml and MARC records

working on new XSLT to convert existing MARC records to bepress

Digital Collections migrationassessed existing metadata for ~12

collectionsselected metadata scheme(s) for use

in new platformadding descriptive metadata to

improve collectionsOral histories

MARC recordsConverting files for use online

04/18/2023

Digital Commons

04/18/2023

Workflow of ETDS

Proquest FTPbox Digital Commons

Library ILS

04/18/2023

04/18/2023

04/18/2023

IR vs. Digital Collections

Digital Commons• Search Engine Optimization

managed by Bepress remotely

• Flexible metadata schema (Bepress created and managed)

• OAI repository

DLXS• Is NOT crawled by search

engine• Flexible metadata schema,

ugly and cruel load tables• OAI repository

04/18/2023

Standards and Guides I turned to• CDPDCMBP (the most incomprehensible of all

acronyms!)• The sources of the schemas: Dublin Core, VRA

Core, METS, etc.• NISO• Controlled vocabularies: LCSH, AAT, DCMITYPE• Digital initiative wikis: Ball State

04/18/2023

Process of Evaluation

• Determine standards that work for users AND work for the collections

• Take a sample of existing metadata and test out standards

• Find ways to make changes in batches, not individual records. Changes through data manipulation, not data entry.

04/18/2023

Issues

04/18/2023

WSULS Field Description CFAI Field Notes AFT Field NotesDetroit Historical Costume Field Notes

Dorthea June Grossbart Field

dc.contributor

Use for general people, corporations, organizations that were involved in the creation/developement of the item

CONTRIBUTORCONTRIBUTOR2CONTRIBUTOR3

dc.coverage

Use for general, non-specific locations, dates and times related to the resource. See dc.date, dcterms.spatial, dcterms.temporal and the VRA location elements for more specific dates and locations coverage

dc.creator

Use for the creator(s) of the item. Agents not considered responsible for the creation of the item can be described by the dc.contributor or the more specific marc relator codes

CREATORCREATOR2CREATOR3 dc: creator

dc.dateUse for date of creation. Can be specific, range, bulk

ORGDATEorgdate2 dc:date

EARLYDATELATEDATE DJG_do

dc.description

Use for general descriptions of the item; an account of the content of the resource DESCRIPTION dc: description DESCRIP

DJG_clDJG_coDJG_dlDJG_ds

dc.identifier

Use for any alpha-numeric identifier used with a physical object. Do not use with identifiers specific to the digital object. identifier dc: identifier OBJECTID DJG_fn

dc.language

Use to indicate the language(s) of the resource. Not to indicate the language of the descriptive metadata

languagelanguage2

dc.publisher Use for the identified publisherPUBLISHERPUBLISHER2 dc: publisher

dc.relation

Use to describe general relations. See DCTERMS relations for more specific relations

relationrelation2

dc.rights

Use to indicate rights. Can include name of rightsholder, contact information rights dc: rights

dc.source

Use to describe another resource from which the source is derived (i.e. the title of the journal where the article appears, the title of a book from which the image was scanned) source dc: source

dc.subject

Use for subject terms. Keywords or controlled vocabularies. Recommended LCSH, AAT, MESH

SUBJECT1SUBJECT2SUBJECT3

dc: subjectdc: relation

not sure if dc: relation is really a relation

COLLECTIONGPARENTPARENTSUBJECTS

dc.title Use for the primary title of the item. TITLE dc: title

dc.type

Use to describe the nature or genre of the resource (i.e. photograph). Do not use for file type

typetype2 dc: Item_Type

dcterms.alternative Use for alternative titles OBJNAME

dcterms.extent

Use to provide physical description. Can include measurement, dimensions, page numbers, number of pieces DIMNOTES

Only one example to base on. Could be a dc.description if all occurences of element are not heel measurements

dcterms.isformatof

dcterms.ispartofdcterms.isreferencedbydcterms.isreplacedbydcterms.isrequiredbydcterms.isversionof

dcterms.mediumUse to describe the material or physical carrier of the resource

DJG_fcDJG_fi

04/18/2023

Omeka

Dublin CoreItem Type MetadataWSU Marc Relator CodesWSU VRA Core

04/18/2023

The Current, the Future

• Controlling the vocabs with:– Google Refine– Excel– MARCEdit– Linked data authorities

• Admin & preservation data• FAST subject headings

04/18/2023

References

https://docs.google.com/document/d/1L9w-nIS4TlRWx9A3N9xpvD2dr0MSSlYLbwrnqcv8Ff0/edit