Bug #802

Move /logs data into PREMIS Events in METS.XML

Added by Peter Van Garderen over 11 years ago. Updated almost 9 years ago.

Status:InvalidStart date:
Priority:CriticalDue date:
Assignee:Evelyn McLellan% Done:


Target version:Release 0.7
Google Code Legacy ID:archivematica-147 Pull Request:
Sponsored: Requires documentation:


Parse the data in the /logs directory into the appropriate PREMIS Events in
the METS.XML manifest that is included with each AIP

[g] Legacy categories: PREMIS


#1 Updated by Evelyn McLellan almost 11 years ago

  • Status changed from New to In progress

[g] Labels added: Component-PREMIS
[g] Labels removed: Component-DataManagement
[g] New owner: berwin22

#2 Updated by Joseph Perry almost 11 years ago

acquireSIPDateTime.log is used to store the acquire SIP time until the Premis file is created, for the ingesting files. After that, this file can safely be rm'd, although we may desire to store some SIP information, and I'm sure this will be part of it.

The extraction log is difficult to parse, because of the multiple extractors used by easy extract.

File UUIDs.log is needed by the archivematica replacement dictionary to determin the UUID of a file, based on it's file name, without having to search each of the xml files. This is needed to reduce processing time.

normalization log. Useful for debugging failed normalization, but the derived premis entities exist. Potentially removable before AIP is created.

SipNameSanitization.log: Premis holds no place for the SIP getting it's name sanitised.

Verify checksum: depends on what type of checksum we are using and how we want it to behave.

[g] New owner: epmclellan

#3 Updated by Evelyn McLellan almost 11 years ago

  • Status changed from In progress to Invalid

Closing this issue because it's a bit too broad - instead we are recording issues relating specifically to PREMIS and workflow

Also available in: Atom PDF