Bug #899

Create entry of when a SIP enters the archivematica MCP to include in the AIP

Added by Joseph Perry almost 11 years ago. Updated almost 9 years ago.

Status:VerifiedStart date:
Priority:CriticalDue date:
Assignee:Joseph Perry% Done:


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


Because we shouldn't write anything to logs directory until we know that the logs directory exists; I suggest we create a small file in the logs directory to say when the SIP compliance has been verified. It will contain

If we did this, the time difference between the actual acquire and the compliance verification would depend on what was in the queue of tasks before the SIP entered.

Alternatively, we could modify the archivematica replacement dic to create a connection to the database, read and parse the date create for the assign job with the job uuid matching the SIP uuid. (The job assigns it's uuid to the sip.)
Then create a job/task to write this information to a file as desired.

[g] Legacy categories: Ingest, Data management


#1 Updated by Joseph Perry almost 11 years ago

  • Priority changed from Medium to Critical
  • Target version set to Release 0.7

As soon as the SIP hits 1-receiveSIP this event is recorded in the database. The event needs to be added to the PREMIS file for each object as the event "Receive SIP".

[g] Labels added: Priority-Critical, Milestone-Release-0.7, Component-Ingest, Component-DataManagement
[g] Labels removed: Priority-Medium

#2 Updated by Joseph Perry almost 11 years ago

Committed r706.
Time is based on job created for asssign SIP UUID.
Placed in logs/injestedDateTime.log

#3 Updated by Joseph Perry almost 11 years ago

  • Status changed from New to Verified

Also available in: Atom PDF