Difference between revisions of "Transfer and SIP creation"
Jump to navigation
Jump to search
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[[Main Page]] > [[Development]] > [[:Category:Development documentation|Development documentation]] > Transfer and SIP creation | [[Main Page]] > [[Development]] > [[:Category:Development documentation|Development documentation]] > Transfer and SIP creation | ||
| + | |||
| + | <div style="padding: 10px 10px; border: 1px solid black; background-color: #F79086;">This page is no longer being maintained and may contain inaccurate information. Please see the [https://www.archivematica.org/docs/latest/ Archivematica documentation] for up-to-date information.</div><p> | ||
| + | |||
| + | [[Category:Feature requirements]] | ||
= Use Cases = | = Use Cases = | ||
* Standard (i.e. unstructured) | * Standard (i.e. unstructured) | ||
| − | * Bag | + | * Bag (zipped and unzipped) |
| + | * Maildir | ||
* TRIM export | * TRIM export | ||
* [[Dspace exports]] | * [[Dspace exports]] | ||
| Line 101: | Line 106: | ||
[[File:Ingest2.png|680px|thumb|center|]] | [[File:Ingest2.png|680px|thumb|center|]] | ||
| − | |||
| − | |||
| − | |||
Latest revision as of 16:28, 11 February 2020
Main Page > Development > Development documentation > Transfer and SIP creation
This page is no longer being maintained and may contain inaccurate information. Please see the Archivematica documentation for up-to-date information.
Use Cases[edit]
- Standard (i.e. unstructured)
- Bag (zipped and unzipped)
- Maildir
- TRIM export
- Dspace exports
Mockups[edit]
1.0 Mockup for Create SIP
Workflow (Standard Transfer)[edit]
In these workflow diagrams, the white ovals are manual steps and the grey ovals are automated steps.
Transfer and create SIPs[edit]
0.9 Transfer workflow
0.9 Create SIP workflow
Media:createSIPWorkflow0.9.pdf
0.8 Transfer workflow
Transfer indexing requirements 0.9 and beyond[edit]
- Full text content
- File embedded metadata
- Formats - by folder, by transfer
- Keyword & pattern matching for privacy/security sensitive information (e.g. social insurance numbers/social security numbers, credit card numbers, email addresses security keywords like 'private', 'confidential' - find or generate list)
- list of PDFs that have not been OCR'ed
- list of password protected / encrypted files
- duplicates with their file paths
Reports for these indexing requirements will be available via the Examine Contents windows, accessible from the Create SIP browser window in the Ingest tab
Examine contents splash page[edit]
- information about the transfer or selected file group (number of files, size, name, uuid, accession #, and?)
- pie graph showing file type distribution overall and bargraph showing file type by folder and ordered by size)
- clickable links: file type opens into new tab with file browser interface of all of specified format), folders opens into new tab with file browser interface of entire folder in context of rest of transfer)
- search box to search index (opens in new tab)
- Report options (each opens in new tab):
- See duplicates with locations
- See Security keywords, CC numbers, SIN/SS#s, Email addresses (with distribution graph)
- See password protected files with distribution (graph?)
Ingest SIPs[edit]
Workflow (DSpace export)[edit]
In these workflow diagrams, the white ovals are manual steps and the grey ovals are automated steps.
Transfer and create SIPs[edit]
Ingest SIPs[edit]
Dashboard design[edit]
Dashboard showing list of transfers[edit]
Click the metadata icon to add transfer metadata[edit]
Add transfer metadata[edit]
A completed transfer[edit]
File visualization reporting page[edit]
Create SIPs using file manager[edit]
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[edit]
- 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: \.
