Sébastien, will write to you about what changes we are proposing for PREMIS 3 for recording computing environments. There may also changes be coming for eventDetailExtension which will help recording these things. I just wanted to quickly send you some information on what we have done in the past.

You might find our paper helpful:

Developing a Robust Migration Workflow for Preserving and Curating Hand-held Media, Angela Dappert, Andrew N. Jackson, Akiko Kimura http://arxiv.org/abs/1309.4932

We recorded, amongst others:


Event Type Fields:

Clone: Copying the disk (CD/DVD) as a disk image (.iso; .mdf./.mds)

Checksum-Create: Checksum manifest should be created at the top project folder level as soon as disk cloning was completed, before copying data, or after extracting/curating files

Copy: Every time a set of data is moved/copied, source and target locations should be recorded. Checksum manifest should be always included in the data set

Checksum- Verify:  When the set of data was copied, checksum manifest should be verified at the destination location

Merge: Generally merger of separate sets of data should be only carried out by EAP curator after disk images were extracted as files

 Extract: Extracting the files from the disk image. Currently a java code created by DPT is operated by EAP

Curate: After files are extracted from disk images, EAP curator reorganise/rename the files and/or reject unwanted files Currently only TIFF files are curated, not AV files.

ServiceCopy-Create: Generating the service copies from the curated copies. Currently a Python script created by DPT is operated by EAP


For each data carrier in a batch to be processed we recorded for the Clone event:

Processing information (Event):

DiskOrder (FIFO, LIFO) – processing order of the robot



Status (closed-Successful, closed-Manual clone, closed-Partial clone, closed-Failed, open-Partial clone, open-Failed, Not attempted)

Comment (Duplicate ID)

Source information (Intellectual Entity Object):





Accompanying Information

Image information (Object):


ImageFileExtension (.iso, .mdf)

OtherFileExtension (.mds)





Agent information (Agents):      


HWAgent (DupliQ DQ-5610, Nimbie NB11, Plextor PX-B120U, PC's disk slot)


SWAgent (QQBoxxPro3 v., QQBoxxPro3 v., IsoBusterPro, IsoBusterPro


Cloning performance metrics:

ProjectID (M)   










Best wishes,

On Thu, Oct 17, 2013 at 4:13 PM, Roke, Elizabeth Russey <[log in to unmask]> wrote:
Hi all--

I'm looking for examples or advice on how others have recorded complex creation environments within PREMIS.  We're currently building functionality in our Fedora repository to store disk images for our digital archives work and need to record the original software/hardware configuration within the metadata somewhere.  I realize that <premis:environment> is designed to store how objects are rendered, not how they were originally created.  But we need more detail than premis:<creatingapplication> allows since we're recording operating system and original hardware.   I'm hesitant to store this type of information in an event-agent relationship because of the complexity.  I've also heard that there will be a revision of PREMIS at some point and I want to be sure whatever we decide to do can be easily mapped to the new schema.

I'm also open to non-Premis solutions if anyone has any suggestions for recording this type of information in some kind of standard way.  


Elizabeth Russey Roke
Digital Archivist
Manuscript, Archives, and Rare Book Library (MARBL)
Emory University, Atlanta, GA 30322

This e-mail message (including any attachments) is for the sole use of
the intended recipient(s) and may contain confidential and privileged
information. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution
or copying of this message (including any attachments) is strictly

If you have received this message in error, please contact
the sender by reply e-mail message and destroy all copies of the
original message (including attachments).