Date
12 June 2014
Attendees
- Vandy Henriksen
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:
Vandy's observations:
|
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