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 an the docuteam feeder API (docuteam feeder API).
In this tab feeder displays a list of all depositions with filename of the deposition, package format, creation date and the state of the deposition:
| State | Description |
|---|---|
submitted | The deposition was created in the feeder web interface or via docuteam feeder 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. |
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 API.
Delete depositions
At this moment depositions can only be deleted using the Depositions API of docuteam feeder API. This only means that the deposition was removed from the bridge API, not from the repository if it was already stored.
Optional features
The tab "Depositions" was introduced with the feeder release 5.4. In the tab Features, the depositions tab can optionally be deactivated (option deposition_ui). In that case SIP can be directly uploaded when a workflow is executed.
With the option manage_depositions_with_feeder it is possible to specify if the state of depositions is set by feeder itself (option activated) or needs to be manipulated using bridge API calls or actions steps manually (option deactivated).