Difference between revisions of "Appraisal Arrangement tab"

From Archivematica
Jump to navigation Jump to search
Line 27: Line 27:
 
=== ArchivesSpace resources ===
 
=== ArchivesSpace resources ===
 
See also [[ArchivesSpace_integration|ArchivesSpace integration requirements]]
 
See also [[ArchivesSpace_integration|ArchivesSpace integration requirements]]
 +
 
How will ArchivesSpace resources be displayed for matching? Questions for requirements gathering:
 
How will ArchivesSpace resources be displayed for matching? Questions for requirements gathering:
  

Revision as of 13:14, 13 April 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?

Mockups

Technical architecture