Depositions
In the tab "Depositions" SIP can be uploaded directly using the feeder web interface, in order to process them with a workflow execution. Depositions can also be created by using the docuteam feeder API (Deposition API).
In this tab feeder displays a list of all depositions with filename of the deposition, package format, creation date and the status of the deposition:
| Status | Description |
|---|---|
submitted | The deposition was created in the feeder web interface or via the Deposition API. |
queued | The deposition has been queued for processing by feeder. |
processing | The deposition is currently being processed by a feeder workflow. |
archived | The deposition was successfully processed by a feeder workflow and the PID of the ingested objects have been added to the deposition data. |
error | The deposition was processed by a feeder workflow, which encountered an error. |
deleted | The deposition was deleted from feeder. |
The deposition state is automatically set by feeder.
By using the Filter button, you can filter the list by filename, package format, status and creation date.
In the detail view you can additionally see when and by whom the depositions was created and additional details about the processing by a feeder workflow.
Create new depositions in feeder
When creating a new deposition in feeder, a file from the local computer can be uploaded. It is necessary to specify the package format. Depositions can be uploaded regardless of the package format; usually a format which can be processed by docuteam actions is selected:
- Matterhorn METS v1.0
- docuteam dublin core v1.0: Converted by step Create SIP from DublinCore Bagit SIP
- eCH-0160 v1.1: Converted by step Create SIP from eCH-0160 SIP
- EDIDOC v1.0: Converted by step Convert an EDIDOC package into a Matterhorn METS SIP
- Single file or folder: Processed by steps Create SIPs from file or folder or Create SIP from Excel
- Generally data in a structured form for which a processing workflow has been created
Create new depositions using docuteam feeder API
Depositions can also be submitted using the Depositions API of docuteam feeder.
Archiving depositions
After a deposition has been successfully processed with a feeder workflow which contains a step for returning PIDs, its status is set to archived and and the binary data of the deposition is deleted, as it is now expected to be stored in the repository.
If the workflow finished successfully, but does not contain a step to report PIDs, the status of the deposition will remain at processing.
If the workflow execution fails the deposition status is set to error and the message field of the deposition response will contain error information.