Transfer and SIP creation

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

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

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

Approve transfer

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: \.

The dashboard showing a SIP that has completed the ingest process