DAWG Metadata Recommendations

The DAWG invites MWG to help us flesh the metadata portion of their project plan prior to sending the informal plan to David and Kevin for feedback.

• Draft outline:  https://drive.google.com/file/d/1-tb-pyyty9985I3WtvreAxPmoR6qccfJ/view?usp=sharing. 

• Data modeling spreadsheet: https://docs.google.com/spreadsheets/d/1ap39ghmU33M92xEnPeIaMV7yT8oB5GCmRasLkPfcSxk/edit?usp=sharing

• MWG Recommendations - submitted 06/05/2020

• Carmen M./Aaron Collier IR metadata assessment: or2017/OR2017_DEV.pdf at master · aaron-collier/or2017

REVIEW

https://drive.google.com/file/d/18-LRmQB3Q-WOrUUUfmaLCoCfd2s3B4WO/view?usp=sharing

A few notes on the data (from @Kevin Cloud (Unlicensed) ):

• I've tried to capture data from each campus. Some campuses only host IR materials and therefore are not included. Some campuses that haven't migrated yet may be over/under excluded from the set.

• Take the crosswalking/mapping with a grain of salt, but it should approximate a CSU-wide aggregated set.

• The campus field has both the campus name AND collection/community handle id. You should be able to validate a record against the identifier_uri field (Dspace Handle service) or append the collection/community to a handle id,, eg. CSUN Archives is https://hdl.handle.net/10211.2/311

• This is data available via the public interface. These are editable fields, fields available via discovery services, OAI-PMH, etc.  Archival DSpace data is available via a separate packages that provide preservation and other kinds of metadata (PREMIS, METS, MODS, etc).

ACTION ITEMS