Difference between revisions of "Archivists Toolkit integration"

From Archivematica
Jump to navigation Jump to search
Line 28: Line 28:
  
 
==ATmetadata.txt file==
 
==ATmetadata.txt file==
The tab-delimited file ATmetadata.txt will contain one row of metadata per digital object in the DIP. On DIP metadata upload, all of the metadata will be used to populate the digital object instances in AT  as follows:
+
The tab-delimited file ''ATmetadata.txt'' will contain one row of metadata per digital object in the DIP. On DIP metadata upload, all of the metadata will be used to populate the digital object instances in AT  as follows:
  
 
*'''restrictionsApply''': TRUE or FALSE (see also '''RestrictionsApply: Base on PREMIS''', below)
 
*'''restrictionsApply''': TRUE or FALSE (see also '''RestrictionsApply: Base on PREMIS''', below)

Revision as of 17:12, 7 February 2013

Main Page > Development > Requirements > Integration with Archivists' Toolkit

This feature will re-format a DIP for import into Archivists' Toolkit.

Workflow

  1. The user sets AT upload configuration options in the admin tab, via a menu called Archivists' Toolkit settings (see Settings, below)
  2. The user processes a SIP the same way that all SIPs are processed
  3. At the Upload DIP micro-service, the user selects "Upload to Archivists' Toolkit"
  4. A tab-delimited file generated from the settings called ATmetadata.txt is placed in the DIP
  5. The DIP is placed in /uploadedDIPs/AT/.
  6. The user can edit the metadata in the text file if desired
  7. The user manually imports the text file into Archivists' Toolkit


DIP requirements

  • A DIP formatted for upload to Archivists' Toolkit consists of the objects plus a tab-delimited text file called ATmetadata.txt.
  • The tab-delimited text file contains field values derived from the user-supplied settings or automatically generated during processing.


Settings

This screenshot shows the settings form in the admin tab, with some default settings:


Metadata entry.png


ATmetadata.txt file

The tab-delimited file ATmetadata.txt will contain one row of metadata per digital object in the DIP. On DIP metadata upload, all of the metadata will be used to populate the digital object instances in AT as follows:

  • restrictionsApply: TRUE or FALSE (see also RestrictionsApply: Base on PREMIS, below)
  • isComponent: TRUE or FALSE
  • eadDaoActuate: onRequest
  • eadDaoShow: new
  • useStatement: Image-Service [for example]
  • objectType: If no data entered, leave emtpy
  • conditionsGoverningAccess: If no data entered, automatically populate from PREMIS <rightsGrantedNote>. If there is no content in <rightsGrantedNote>, leave empty
  • conditionsGoverningUse: If no data entered, leave empty
  • digitalObjectID: If isComponent is TRUE, populate from Parent digital object ID field in settings; if isComponent is FALSE, automatically populate with file UUID
  • title: Automatically populate with filename (without UUID)
  • uri: Automatically populate with eg www.myinstitution.org/[UUID]-filename
  • existenceLocationOriginals: automatically populate with AIP UUID


RestrictionsApply: Base on PREMIS

  • If PREMIS <act>= Disseminate and PREMIS <restriction> = Allow, restrictionsApply = FALSE
  • If PREMIS <act>= Disseminate and PREMIS <restriction> = Conditional, restrictionsApply = TRUE
  • If PREMIS <act>= Disseminate and PREMIS <restriction> = Disallow, restrictionsApply = TRUE
  • In addition, when restrictionsApply=TRUE, both eadDaoActuate and eadDaoShow will be set to “none.”