Usage@Ingest

• Usecase: direct ingestion of a SIP package

In ARCLib data can be ingested in two ways. The first one is by using an ingest routine that automates the triggering of ingest for a batch of packages in a certain period of time. The second one is a direct ingestion of one SIP package, in this way the ingest workflow starts immededitaly.

Attribute	Description
Sip content	users selects a .zip file from filesystem that stores the archived content to be ingested
Hash value	value of the hash of SIP
Hash type	type of the hash of SIP
Producer profile external ID	producer profile to be used in the ingest process
Workflow configuration	JSON configuration of the ingest workflow
Transfer area path	file path to a folder where the SIP should be saved before starting the ingest process, this path is relative to the path of the transfera area of the producer. If empty, the SIP is stored to the root folder of the transfer area of the producer.

Note: ARCLib computes the resulting ingest workflow config by merging producer and batch ingest configs. If there are two equally named attributes the batch config has the priority over the producer config.

To start the ingest, user clicks the Submit button and waits until the SIP package is uploaded (that can take up to several minutes depending on the internet connection). After the successfull upload user gets a message about the success (unsuccess respectively).