Difference between revisions of "Transfer backlog requirements"

From Archivematica
Jump to navigation Jump to search
m (Move to feature requirements category)
Line 2: Line 2:
  
 
Release 1.0
 
Release 1.0
 +
 +
[[Category:Feature requirements]]
  
 
== Transfer Backlog Management ==
 
== Transfer Backlog Management ==
Line 143: Line 145:
  
 
[[File:Transfer_search_files_v2.png|800px]]
 
[[File:Transfer_search_files_v2.png|800px]]
 
[[Category:Development documentation]]
 

Revision as of 13:42, 23 March 2017

Main Page > Development > Development documentation > Transfer backlog requirements

Release 1.0

Transfer Backlog Management

  • Related issues: Issue 951, Issue 1220, Issue 1141, Issue 1225, Issue 1257

Requirements for transfer backlog search

  • Add ability to search transfer backlog and send one or more transfers to Ingest
  • Add ability to download and/or view files/transfers (via right click)
  • Search the following fields: Any field, transfer name, file name, accession number, PUID, Mimetype, Date - Ingest

Mockup of transfer backlog search

1.0 TransferBacklogSearch.png
1.0 TransBacklogSearchResults.png

Transfer Workflow

  • Administration - allow MCP access to media or storage where transfer is located
  • Assign accession number to transfer
  • Remove transfer backup from workflow - no long processing configuration option
  • Add Send transfer to backlog microservice
  • Add Search transfer backlog tab from Ingest in Dashboard
  • Add ability to download and/or view transfers and files from Search tab
  • Add ability to send transfers from backlog search to Ingest/Create SIP (checkboxes, send button)
  • see workflow diagrams below

0.9 Transfer workflow

  • grey steps are automated, white are manual
TransferWorkflow0.9.png
TransferWorkflow0.9pt2.png

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 backlog locations (configuration is done outside of AM)
  • Assign source directories
  • Define transfer types
  • Assign report locations (post-1.0)
  • Set AIP storage location
  • Set DIP upload location

Accession metadata

  • PREMIS Event = Registration
        <event>
           <eventIdentifier>
             <eventIdentifierType>UUID</eventIdentifierType>
             <eventIdentifierValue>35cbe00d-d661-4174-b11a-e203f5608008</eventIdentifierValue>
           </eventIdentifier>
           <eventType>registration</eventType>
           <eventDateTime>2012-03-14</eventDateTime>
           <eventDetail></eventDetail>
           <eventOutcomeInformation>
             <eventOutcome></eventOutcome>
             <eventOutcomeDetail>
               <eventOutcomeDetailNote>accession#2012-029</eventOutcomeDetailNote>
             </eventOutcomeDetail>
           </eventOutcomeInformation>
           <linkingAgentIdentifier>
             <linkingAgentIdentifierType>archivist</linkingAgentIdentifierType>
             <linkingAgentIdentifierValue>Courtney Mumma</linkingAgentIdentifierValue>
           </linkingAgentIdentifier>
         </event>
  • Manually input metadata in template on dashboard (See File_Browser_Requirements) : accession number
  • Agent is the archivist logged in at the time doing the accession (post-1.0, for 1.0 this will still be repository)
  • Event name is "registration" (to be added to PREMIS events master list should we decide to implement)
  • UUID
  • Also see Issue 787 on the Archivematica issues list

Microservices Completed Before Move to Backlog

Handling of Submission Documentation

  • TAPER?
  • Normalized with objects in AIP (0.8)
  • Upload submission documentation with transfer in transfer tab - Issue 1255

Search transfers from Archival Storage

New sponsored development planned for Archivematica 1.6 or later will allow users to manage the transfer backlog through the Archival Storage tab, as outlined in general workflows described in these diagrams:

Transfer management workflows.png

As outlined above, users will be able to:

  • Search transfers from archival storage tab
  • Download copies of transfers or selected files from archival storage tab
  • Be able to perform transfer deletion requests from archival storage tab

Transfer search user stories

As an archivist, I need to find transfers by searching...

  • by the name of the transfer
  • by the date the transfer was stored in backlog
  • by names of files within the transfer
  • by....?

Mockups: Version 1

Search transfers from Archival Storage:

Archival Storage Transfer Search.png

Notes:

  • Click on "Show transfers" to search AIPs as well as Transfers
  • A new column in the table indicates whether a package is a Transfer or an AIP.
  • To trigger transfer deletion, click on red "remove" icon (same functionality as AIP deletion)

Search files from transfers in Archival Storage:

Archival Storage Transfer file search.png

Notes:

  • Clicking on both "Show files" and "Show transfers" before searching will load preview of files from transfer backlog.
  • The UUID of the package and an indication of whether the file is from a Transfer or an AIP is in the right column.

Mockups: Version 2

In this version, toggling between searching for AIPs/Transfers is done through a tab at the top. This makes the development significantly less complicated, as we would not need to combine the Elasticsearch indexes for transfer METS and AIP METS.

Transfer search:

Transfer search v2.png

Files within transfer search:

Transfer search files v2.png