2014-06-12 Meeting Notes AWG

Date

12 June 2014

Attendees

Agenda Items

ICA-Atom
customized microservices, including custom rules/tools and try breaking up a disk image file and ingesting it in chunks
instructions for customizing bag (e.g. including file for skipping over certain microservices?)
manual upload to CONTENTdm via Project Client.

Discussion Items

Item

Notes

ICA-Atom

Jessica walked us through her testing and exploration of the interface:

Test cases:

AtoM DIP upload settings in archivematica - argument w/ rsync-target location for DIP looks right, but is failing - “no such file or directory” message
admin>settings: turned on Sword plugin, but DIPS still not going from archivematica to AtoM
pulled EAD from TARO and put into AtoM - looks like it creates new collection on import - where/how to add DTD and stylesheet?

Configuration & Branding

AtoM is set up for multiple institutions' detailed profiles, including history, collecting policies, etc.
The interface is customizable via themes w/ php & css, but it isn't clear whether it provides separate themes for multiple institutions sharing an instance
It would help to determine where the the php and css is in the directory structure

Forms & Navigation

Help text for form fields reference specific cataloging rules - nice! Presumably customizable?
Required fields are indicated, but difficult to locate/populate in collapsible form sections
Form field mappings for describing archival series and sub-series is confusing
Accession records vs. archival descriptions - relationship between different menus in interface - navigation is not intuitive
Workflow feature - create/save/review drafts looks promising
Auto-linked data (e.g. creator names from authority files)
Only 1 digital object link is allowed in the collection level record - can this be changed? Multiple items can be added via file upload; why not multiple links?

Vandy's observations:

ELK stack, NGINX server, Symfony framework - learning curve, different from other software in use at UT Libraries
OAI settings/numbers?

archivematica customized microservices, including custom rules/tools

from Benn's post to the list-serv:

What I tested:

I created an identification tool and command named “simple Python script version 1.0” It’s just a simpler variation on the existing “” tool. I changed the Portable Network Graphics rule to use my script instead of the default one. Then, under Administration’s Processing configuration, I specified my script for use in all transfers. Ran a transfer test and the identify file format job was successful. Verified it used my script by positively matching STDOUT’s IDCommand UUID with my script’s UUID. Reset Administration’s Processing configuration to use default script (FIDO) in all transfers.

What my test means to me:

To me this test verifies that we can make customized identification tools, but unless we have good reason to not use FIDO and File Extension, there’s no need to customize identification tools (duh!). As far as identifying unknown file formats go with FIDO, I will look into FIDO’s use of PRONOMs registered with The National Archives technical registry of file formats. They don’t seem to have a disk image file format (e01) registered, but once they do, FIDO should be able to lookup the PRONOM identifier when it encounters a disk image, for example.

Other thoughts:

Administration’s Processing configuration uses FIDO in transfers. But all the format rules point to the command File Extension version 0.1. This confuses me.

CONTENTdm DIPs

Melanie downloaded and extracted .7z files generated by archivematica from upload DIP to CONTENTdm microservice - there is no apparent CONTENTdm-specific information therein, have yet to try manual upload via Project Client.

What is happening with recurring decision point loops in archivematica ingest? After Upload DIP to CONTENTdm job completes successfully, it returns to Upload DIP decision point again...

Action Items

Jessica Wesley Meyerson to contact Courtney Mumma at Artefactual re: AtoM form field mappings for describing archival series and sub-series
Ladd Hanson to investigate archivematica-AtoM pipe
Melanie Cofield to test DIPS with metadata and/or compound objects