Transfer backlog requirements

Main Page > Development > Development documentation > Transfer backlog requirements

Release 1.0? Partial 0.9? (If so, determine minimum for 0.9)

Transfer Workflow

• Administration - allow MCP access to media or storage where transfer is located
• Administration - Manual - Assign accession number to transfer
• see workflow diagrams below

0.9 Transfer workflow

• grey steps are automated, white are manual

transferWorkflow0.9.pdf

Administration Tab in Dashboard

• Assign permission and access to the MCPServer to copy from transfer media (hard drives, optical media, USB, etc.) or network location.
• Assign transfer backup location
• Assign source directories
• Define transfer types
• Assign report locations
• Set accession management location
• Set AIP storage location
• Set DIP upload location

Accession metadata

• PREMIS Event = Accession

        <event>
           <eventIdentifier>
             <eventIdentifierType>UUID</eventIdentifierType>
             <eventIdentifierValue>35cbe00d-d661-4174-b11a-e203f5608008</eventIdentifierValue>
           </eventIdentifier>
           <eventType>accession</eventType>
           <eventDateTime>2012-03-14</eventDateTime>
           <eventDetail>accession#2012-029</eventDetail>
           <eventOutcomeInformation>
             <eventOutcome></eventOutcome>
             <eventOutcomeDetail>
               <eventOutcomeDetailNote></eventOutcomeDetailNote>
             </eventOutcomeDetail>
           </eventOutcomeInformation>
           <linkingAgentIdentifier>
             <linkingAgentIdentifierType>archivist</linkingAgentIdentifierType>
             <linkingAgentIdentifierValue>Courtney Mumma</linkingAgentIdentifierValue>
           </linkingAgentIdentifier>
         </event>

• Manually input metadata in template on dashboard (See File_Browser_Requirements) : date of accession, accession number
• Agent is the archivist logged in at the time doing the accession
• Event name is "Accession" (to be added to PREMIS events master list should we decide to implement)
• UUID

• Also see Issue 787 on the Archivematica issues list

Date to be preserved

from Issue 882

• Transfer name
• Transfer UUID
• Transfer size
• Transfer storage location
• Date placed in storage

Microservices Completed Before Backup / Move to Backlog

• All transfer microservices
• Indexing: See Transfer_and_SIP_creation#Transfer_indexing_requirements_0.9_and_beyond

Handling of Submission Documentation

• TAPER?
• Normalized with objects in AIP (0.8)
• Also see Issue 787 on the Archivematica issues list