pass-data-model

Deposit

A Submission can have multiple Deposits, each to a different Repository. This entity describes the interaction of PASS with a target Repository for an individual Submission with the purpose of satisfying one or more Policies.

Field	Type	Description
id*	URI	Unique Deposit URI (autogenerated)
depositStatusRef	String	A URL or some kind of reference that can be dereferenced, entity body parsed, and used to determine the status of Deposit
depositStatus*	Enum	Status of deposit (see list below)
submission*	URI	URI of Submission this Deposit is a part of
repository*	URI	URI of the Repository being deposited to
repositoryCopy	URI	URI of the Repository Copy representing the copy that is reltaed to this Deposit. The value is null if there is no copy

*required

Properties automatically generated by the system are documented in System Properties. These are not available to client tools by default.

Deposit status options

These are the possible statuses for a Deposit in the order they could occur. Note that not all repositories will go through every status.

Intermediate status

A Deposit with an intermediate status indicates that the processing of the Deposit is not yet complete. At some indeterminate point in the future, the status may be updated to a terminal state.

Terminal status

A Deposit with a terminal status indicates that the processing of the Deposit is complete.

Value	State	Description
submitted	Intermediate	PASS has sent a package to the target Repository and is waiting for an update on the status
rejected	Terminal	The target Repository has rejected the Deposit
failed	Intermediate	A failure occurred while performing the deposit, it may be re-tried later.
accepted	Terminal	The target Repository has accepted the Files into the repository and they are pending publication if not published already

This site is open source. Improve this page.