Difference between revisions of "Transfer and SIP creation"
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
'''0.9 Transfer workflow''' | '''0.9 Transfer workflow''' | ||
| + | * grey steps are automated, white are manual | ||
[[File:transferWorkflow0.9.png|680px|thumb|center|]] | [[File:transferWorkflow0.9.png|680px|thumb|center|]] | ||
Revision as of 13:05, 17 May 2012
Main Page > Development > Development documentation > Transfer and SIP creation
Use Cases
- Generic (i.e. unstructured)
- Bag
- 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
0.9 Transfer workflow
- grey steps are automated, white are manual
0.8 Transfer workflow
indexing
- 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
- list of password protected / encrypted files
Ingest SIPs
Workflow (DSpace export)
In these workflow diagrams, the white ovals are manual steps and the grey ovals are automated steps.
Transfer and create SIPs
Ingest SIPs
Dashboard design
Dashboard showing list of transfers
Click the metadata icon to add transfer metadata
Add transfer metadata
A completed transfer
File visualization reporting page
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: \.
