Difference between revisions of "Transfer and SIP creation"
Jump to navigation
Jump to search
| Line 19: | Line 19: | ||
==file visualizations== | ==file visualizations== | ||
* (sub)directory size | * (sub)directory size | ||
| − | * | + | * Should we move file format identification forward in the pipeline? To offer visualizations on: |
**file extension | **file extension | ||
**(from FITS report): DROID identification, JHOVE identification, EXIF identification, etc | **(from FITS report): DROID identification, JHOVE identification, EXIF identification, etc | ||
| − | + | ||
===Ingest SIPs=== | ===Ingest SIPs=== | ||
Revision as of 12:38, 16 August 2011
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
Create SIPs
indexing
- keyword & pattern matching for privacy/security sensitive information (e.g. social insurance numbers, credit card numbers, 'private', 'confidential')
file visualizations
- (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
Ingest SIPs
Dashboard design
Dashboard showing list of transfers
Click the metadata icon to add transfer metadata
Enter transfer metadata and click "Save"
Transfer is finished after a virus scan shows no viruses
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.
