Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The Ingest Monitoring offers an overview of the items for your organisation in MediaHaven. Each item in MediaHaven has a list identifiers and a particular status and is linked with a series of events. Firstly we describe these concepts of status, events and identifiers. Secondly we describe how these concepts are used in the design of the ingest into MediaHaven and the representation in three views in the MediaHaven Ingest Monitoring.

ArchiveStatus

Value

Remark

Status
colourBlue
titleon_ingest_tape

The item has been detected by the tape ingest server but has not yet been transferred to the ingest server.

Status
colourBlue
titlein_progress

The item has been detected on the ingest server and is being processed.

Status
colourRed
titlefailed

The item is not successfully processed. The events for this item contain one or more

Status
colourRed
titleNOK
events and these contain the reason for the failure.

Status
colourGreen
titleon_disk

The item is successfully archived on two or more disks. For files where the ultimate location is tape, this status will not appear.

Status
colourGreen
titleon_tape

The item is successfully archived on N tapes. Depending on the installation N can be 1 (archive), 2 (backup) or 3 (vault).

Status
colourGreen
titlecompleted

Only used for files of the type:

  • Ensemble (Collection, Set, Newspaper): all files in the ensemble have either ArchiveStatus 

    Status
    colourGreen
    titleon_disk
    Status
    colourGreen
    titleon_tape
     or 
    Status
    colourGreen
    titlecompleted
    .

  • Metadata Only: the ArchiveStatus is immediately 

    Status
    colourGreen
    titlecompleted
     upon creation

Events

MediaHaven logs the complete history of an item as a list of successive Premis events. The outcome of an event is either good 

Status
colourGreen
titleok
 or bad 
Status
colourRed
titlenok
.

Here we offer an overview of event types.

Event

Description

Status

colourGrey

titleCREATE

The item has been created in MediaHaven. From this point on the three identifiers (see below) are defined.

Status

colourGrey

titleSIP_DETECTED

The item has been detected by either the tape ingest server

Status
titletapeserver
or by the standard ingest service
Status
titlepretranscoder

Status

colourGrey

titleTAPE_ZIP

(tape ingest only) The item has been successfully packed into a ZIP archive.

Status

colourGrey

titleUPDATE

The metadata of the item has been updated in the database.

Status

colour

Grey

titlepublish

The file has been manually published by the user or has been automatically published.

Status

colour

Grey

titlepretranscoded

Event generated by the standerd ingest service

Status
titlepretranscoder
to typically log validation errors (e.g. MD5 checksum, archive validation) with outcome
Status
colourRed
titlenok
.

Status

colourGrey

titletranscode

The service

Status
titletranscoder
has started the transcoding and storage allocation of the item.

Status

colourGrey

titletranscoded

The service

Status
titletranscoder
has finished the transcoding and storage allocation of the item. For installations where the ultimate location is not tape, the item will have the status
Status
colourGreen
titleon_disk
from this point onward.

Status

colour

Grey

titlearchiveD_on_tape_ARCHIVE

(For installations that write to 1 or more tapes) The item has been successfully written to an

Status
titlearchive
tape. The comment of the event contains the barcode of the tape. If the item has been successfully written to all required tapes, the item will have the status
Status
colourGreen
titleon_tape
after the batch of tapes writes is complete.

Status

colour

Grey

titlearchived_on_tape_BACKUP

(For installations that write to 2 or more tapes) The item has been successfully written to a

Status
titlebackup
tape. The comment of the event contains the barcode of the tape. If the item has been successfully written to all required tapes, the item will have the status
Status
colourGreen
titleon_tape
after the batch of tapes writes is complete.

Status

colourGrey

titlearchived_on_tape_VAULT

(For installations that write to 3 tapes) The item has been successfully written to a

Status
titlevault
tape. The comment of the event contains the barcode of the tape. If the item has been successfully written to all required tapes, the item will have the status
Status
colourGreen
titleon_tape
after the batch of tapes writes is complete.

Status

colourGrey

titleexport

An export of the item has been requested by a user. The event can have outcome

Status
colourRed
titlenok
if permission was denied.

Status
titleexported

The export of the item has been completed with outcome

Status
colourGreen
titleok
or
Status
colourRed
titlenok
.

Examples of the sequence of events

  • An item submitted using the standard online ingest and stored on disk: 

    Status
    colourGreen
    titleSIP_DETECTED
     
    Status
    colourGreen
    titleCREATE
     
    Status
    colourGreen
    titleUPDATE
     
    Status
    colourGreen
    titletranscode
     
    Status
    colourGreen
    titletranscoded
     → 
    Status
    colourGreen
    titleon_disk

  • An item submitted using the standard online ingest with an MD5 checksum failure: 

    Status
    colourGreen
    titleSIP_DETECTED
     
    Status
    colourGreen
    titleCREATE
     
    Status
    colourRed
    titlepretranscoded
     → 
    Status
    colourRed
    titlefailed

  • An item submitted using the standard online ingest and stored on an archive and backup tape: 

    Status
    colourGreen
    titleSIP_DETECTED
     
    Status
    colourGreen
    titleCREATE
     
    Status
    colourGreen
    titleUPDATE
     
    Status
    colourGreen
    titletranscode
     
    Status
    colourGreen
    titletranscoded
     
    Status
    colourGreen
    titlearchived_on_tape_ARCHIVE
     
    Status
    colourGreen
    titlearchived_on_tape_BACKUP
     → 
    Status
    colourGreen
    titleon_tape

  • An item submitted using the standard online ingest and but which could not be written to tape due to an internal error:  

    Status
    colourGreen
    titleSIP_DETECTED
     
    Status
    colourGreen
    titleCREATE
     
    Status
    colourGreen
    titleUPDATE
     
    Status
    colourGreen
    titletranscode
     
    Status
    colourGreen
    titletranscoded
     
    Status
    colourRed
    titlearchived_on_tape_ARCHIVE
     
    Status
    colourGreen
    titlearchived_on_tape_BACKUP
     → 
    Status
    colourRed
    titlefailed

  • An item read from an ingest tape and stored on an archive and backup tape: 

    Status
    colourGreen
    titleSIP_DETECTED
     
    Status
    colourGreen
    titleCREATE
     
    Status
    colourGreen
    titleTAPE_ZIP
     
    Status
    colourGreen
    titleSIP_DETECTED
     
    Status
    colourGreen
    titleUPDATE
     
    Status
    colourGreen
    titletranscode
     
    Status
    colourGreen
    titletranscoded
     
    Status
    colourGreen
    titlearchived_on_tape_ARCHIVE
     
    Status
    colourGreen
    titlearchived_on_tape_BACKUP
     → 
    Status
    colourGreen
    titleon_tape

  • An item read from an ingest tape but with an MD5 checksum failure on the ingest tape:  

    Status
    colourGreen
    titleSIP_DETECTED
     
    Status
    colourGreen
    titleCREATE
     
    Status
    colourRed
    titleTAPE_ZIP
     → 
    Status
    colourRed
    titlefailed

Identification
Anchor
Identification
Identification

In order to unique identify items in the system MediaHaven uses three identifiers:

  1. Umid (aka MediaObjectId): This is a 64 character hex string uniquely representing the item in MediaHaven.

  2. FragmentId: This is a 96 character hex string representing a fragment of an item (e.g. a clip from a video, a page from a document). An item has always at least one fragment, termed the main fragment.

  3. ExternalId: (Advanced installations only) The field contains the identifier of the item provided by the customer. The ingest flow is tightly coupled with this field: it will reject or accept a item based on whether the ExternalId already exists in the system. In the design section below we go into detail about this.

Views

The Ingest Monitoring offers three views:

  1. SIPs: Offers an overview of items coupled with an ExternalId, showing only the most recent submission of each ExternalId.

  2. items: Offers a complete history of items submitted to MediaHaven, including failed or deleted submissions.

  3. Events: Offers the complete history of events in MediaHaven. When restricted to events of a single item, it shows the complete history of events that occurred to that item.

Design

The ingest views are designed around the following philosophy:

...

The screenshot below shows in the view 

Status
titleSIps
 the item with ExternalId 
Status
titleara_510_2242_00
 with status 
Status
colourGreen
titleon_tape
 that was successfully archived on .Image Removed

...

Files

The screenshot below shows in the view 

Status
titlefiles
 the complete history of submissions of the item 
Status
titleara_510_2242_00
. The most recent submission has status 
Status
colourGreen
titleon_tape
, while the previous submissions have status 
Status
colourRed
titlefailed
 and have been deleted (showed by a shaded or striped colour). In the example the item 
Status
titleara_510_2242_00
 has been submitted 8 times. Notice that each submission has its own FragmentId while they share the same ExternalId. Due to design of the ingest, there can be exactly only one non-deleted item for the same ExternalId.Image Removed

...

Events (succes)

If we look into the view 

Status
titleevents
 of the successful 
Status
colourGreen
titleon_tape
 submission we see the following events. Notice that the item has been successfully written to the 
Status
titlearchive
 tape 
Status
titlea00001L7
 and 
Status
titlebackup
 tape 
Status
titleB00001L7
. Afterwards it has been exported to an 
Status
titleexport
 tape 
Status
titleE00000L6
.Image Removed

...

Events (failure)

If we look into the view 

Status
titleevents
 of a 
Status
colourRed
titlefailed
 submission we see for example the following events.Image Removed

...

We notice that the event 

Status
titlepretranscodeD
 with outcome 
Status
colourRed
titlenok
. The comment contains the following error:

Warning

METS: referred file does not exist: OriginalData/510_2242_000_00049_000/510_2242_000_00049_000_0_0001.tif

The submitted item was an archive and the METS file linked with it, described a file which was not found inside the archive.