Difference between revisions of "Appraisal Arrangement tab"

From Archivematica
Jump to navigation Jump to search
Line 38: Line 38:
  
 
What are the requirements for querying or filtering the data gathered above?
 
What are the requirements for querying or filtering the data gathered above?
 +
 +
=== Workflow questions ===
 +
 +
These are some questions related to workflow that have arisen since the early development of the Tab:
 +
 +
Given the ability to produce a refined list of digital objects in the File List pane:
 +
 +
1. Is it necessary to be able to filter by format or PUID from the backlog, or only from the refined list?
 +
 +
Sample workflow:
 +
* User performs search of backlog and populates backlog pane
 +
* User selects transfers relevant to their purpose
 +
* User '''then''' filters the selected transfers by a specific file type, which populates the File List pane?
 +
 +
2. From where does a user drag files in order to create a SIP? From backlog, the File List pane, or both?
  
 
== Mockups ==
 
== Mockups ==

Revision as of 17:05, 22 July 2015

Main Page > Development > Requirements > Appraisal and Arrangement Tab

Background

The Bentley Historical Library has a Mellon grant which is sponsoring development on the foundational project to create an Appraisal and Arrangement tab. This tab will function as a place between Transfer and Ingest where archivists can make archival appraisal decisions with material from Transfer, and structure an arrangement for the SIP before starting Ingest processes. As of the Archivematica 1.3.0 release, the arrangement/appraisal decisions are made at the top of the Ingest tab by selecting transfers from the backlog for arrangement. This process, including the transfer backlog search, is to be moved into the new Appraisal and Arrangement tab.

Older requirements for similar functionality:


Requirements

Data

Data gathered during the Transfer stage has the potential to be used in the Appraisal/Arrangement tab for reports and visualizations. Below is a (currently unordered) list of potentially required data:

  • What data points about the objects themselves? Filename, format, MIME type, other?
  • Bulk Extractor reports (which ones? how to view?)
  • Directory printer text file -or- METS.xml structMap (same info)
  • File format information (grouped by file extension? by PRONOM ID?)
  • Size of content (space on disk), number of files
  • Viewer based on format ID
  • logs (virus scan, format identification, etc)
  • Other?

ArchivesSpace resources

See also ArchivesSpace integration requirements

How will ArchivesSpace resources be displayed for matching? Questions for requirements gathering:

  • How many resources and at what level should be loaded in the tab?
  • What options does the user have to search for existing resources?
  • How does the user create a new resource?
  • What data points are displayed (labels, level of description, other)?

Querying/filtering

What are the requirements for querying or filtering the data gathered above?

Workflow questions

These are some questions related to workflow that have arisen since the early development of the Tab:

Given the ability to produce a refined list of digital objects in the File List pane:

1. Is it necessary to be able to filter by format or PUID from the backlog, or only from the refined list?

Sample workflow:

  • User performs search of backlog and populates backlog pane
  • User selects transfers relevant to their purpose
  • User then filters the selected transfers by a specific file type, which populates the File List pane?

2. From where does a user drag files in order to create a SIP? From backlog, the File List pane, or both?

Mockups

Version 1 of the transfer backlog/reporting pane:

Appraisal Arrangement tab pane mockups - Transfer backlog pane.png

Screenshots during interim development period, July 2015:

A a tab July2015 1.png

A a tab July2015 2.png

New functionality identified during this period includes tagging content while processing the backlog, as an "aide memoire"- in this example, a reminder that some material will be discarded from the accession.

A a tab July2015 3.png

Technical architecture

An initial mockup of the appraisal tab has been started, developed as an Angular.js app. The code is available on github.

The basic idea is to create an Angular app, that communicates with the Archivematica Dashboard via its REST api.

More details Appraisal Tab Architecture