DAO Documentation
- Molly Bragg (old account) (Unlicensed)
- Noah Huffman (Deactivated)
A scratch space for corralling documentation on <dao>s and ASpace / DDR integration...
Existing Documentation
- Summary of metadata lifecycle for digitized Rubenstein collections (current and proposed): https://docs.google.com/document/d/1vwdkBWEdD_mJM1CKIGi-k4G4twDY0aPRn6YZtA2yLvU/edit
- DAO Use statements and behaviors: https://docs.google.com/spreadsheets/d/1x07i7yvWymMbkJ4EXMmwRRnVUBPJJVDoKfr0k1EP0wU/edit#gid=0
Issues to consider
- Need to develop / document strategy for storing ARKs in ArchivesSpace digital object records and EAD (intsead of digital collection URLs with slugs).
- Develop strategy for updating existing ASpace digital object records and corresponding <dao> elements in published collection guides
- Python script that does this (needs more testing): https://github.com/duke-libraries/archivesspace-duke-scripts/blob/master/python/asUpdateDAOs.py
- Discuss how to handle master vs. use vs. mezzanine
- Should we continue to treat derivatives as different file versions of the same digital object or should we create separate digital objects for each derivative
- How are these modeled in the repository?
- Can we rely on the repository to manage the derivatives and just store a "placeholder" digital object in ArchivesSpace that points to a DDR item that contains many derivatives?
- How to link from ASpace folder level description to groups of items from that folder in DDR (e.g. Gedney contact sheets and JWT Ford Ads)