Difference between revisions of "Transfer and SIP creation"
|Line 40:||Line 40:|
Revision as of 18:24, 22 August 2011
- Generic (i.e. unstructured)
- TRIM export
- Dspace exports
Workflow (Generic Transfer)
In these workflow diagrams, the white ovals are manual steps and the grey ovals are automated steps.
Transfer and create SIPs
- keyword & pattern matching for privacy/security sensitive information (e.g. social insurance numbers, credit card numbers, 'private', 'confidential')
- list of PDFs that have not been OCR'ed
- (sub)directory size
- Should we move file format identification forward in the pipeline? To offer visualizations on:
- file extension
- (from FITS report): DROID identification, JHOVE identification, EXIF identification, etc
Dashboard showing list of transfers
Click the metadata icon to add transfer metadata
A completed transfer
Create SIPs using file manager
In this mockup, the user has completed a transfer, has created SIP folders in ingestSIP and is preparing to move objects from the completed transfer into the SIP folders.
Add Dublin Core metadata to a SIP during ingest =
- All fields are simple Dublin Core except for Relation: Is Part Of, which is designed to upload the SIP to a pre-existing archival description in the access system.
- Multi-value entries are separated by a backward slash: \.