Crosswalk ASpace Fields

uhlibraries-digital / bcdams-map

Metadata Application Profile for the Bayou City DAMS

MIT License

6 stars 5 forks source link

Crosswalk ASpace Fields #5

Closed metaweidner closed 7 years ago

metaweidner commented 8 years ago

Add EAD/ASpace column to crosswalks

metaweidner commented 8 years ago

@rmrichardson @librarycard @lisacruces: I've added an EAD/ASpace column to the DPTF & DAMSTF crosswalk documents:

librarycard commented 8 years ago

For DPTF Crosswalk (collection-level data)

Original Collection: archdesc > did > unittitle
Repository: archdesc > did > repository
Creator: archdesc > did > origination
Date: archdesc > did > unitdate
Description: archdesc > scopecontent
Publisher: this field does not really exist, at least not at the collection level, for an archival collection
Use & Reproduction: archdesc > userestrict
Title: archdesc > did > unittitle (again?)

metaweidner commented 8 years ago

Thanks @librarycard. I've added the EAD mappings to the crosswalk. I split out the EAD/ASpace column into 'EAD (archdesc)' and 'Aspace.'

metaweidner commented 7 years ago

@librarycard @rmrichardson @lisacruces Can we consider this issue closed, or is there still work to be done on this with relation to the MAP?

metaweidner commented 7 years ago

@librarycard @lisacruces @rmrichardson Some notes from today's DMWG meeting to guide your investigations into how we might map harvested descriptive metadata from the ASpace API:

General rules for configuration at the application level

Item level description: -- Title -- Date
Folder level description: -- Title + Item # -- Date
Additional fields require further investigation: -- Description (Scope and Contents Note) -- Inherited levels of data