...
Last Revised: March 2018
Status: Final Draft Approved by:
Summary of Activity
The Deposit Functional Requirements Group’s charge was to provide system functional requirements related to different methods of deposit/ingest into the repository, such as end-user deposit, staff deposit, mediated submission workflows, and batch ingest. The first chartered deliverable instructed the group to:
...
- DLP implementation teams should coordinate with service owners to adapt existing pre-deposit activities and workflows as needed to work with future repository software: current state repository-related applications may provide more specialized and unit-customized SIP preparation functions than DLP/Hyrax will provide.
- Service owners should also adjust workflows and practices as needed relative to the new Digital Preservation Policy. The Digital Preservation FRG’s SIP Decision Document describes the elements required of a SIP:
- Content deposited to Emory’s preservation repository must include the primary characteristics identified in Emory’s Digital Preservation Policy. Secondary characteristics may be deposited alongside the primary characteristics.
- The Digital Preservation Policy further elaborates on these elements.
- The Archival Information Package (AIP) specification also describes required and optional files and datastreams for inclusion in the preservation object.
- Implementation teams should coordinate with service owners to investigate relationships between self-deposited content across self-deposit workflows (e.g. relationships between ETDs, OpenEmory, and research data created by Emory scholars)
- Implementation teams should investigate Hyrax roadmap for batch-upload capability for importing from spreadsheets
- Monitor impacts for current deposit activities relative to cloud hosting/storage (in scope for the Technology Implementation Working Group and Technical Design Phase)