This page describes the deposit process and all the various processing states of a deposit. Updated March 30, 2016 12:58
The life cycle of a deposit into the PKP PLN is:
the deposit is created by the journal when the issue is published.
the deposit is then transferred to the network’s staging server, where its contents are validated, checked for viruses, etc.
it is then transferred from the staging server to the LOCKSS network
when all of the copies on the LOCKSS network are proven to be identical, the journal deletes the deposit in order to save storage space.
The PLN Plugin’s Status page
Each deposit a journal makes to the PKP PLN has a row in the “PKP PLN Plugin - Status” page within the plugin’s admin pages. Below are brief explanations of what each of the columns in the status page mean.
ID: The deposit's internal database identifier.
Type: Whether the deposit is an issue or an article.
Checked: The date that the journal plugin most recently checked the status of the deposit in the staging server. Once a deposit is completed and all nodes in the LOCKSS network have reached agreement, the plugin will stop checking on its status.
This column describes the status of the deposit inside OJS. The posible states in this column are
New: the plugin is aware of the deposit, but has not generated a package file for the staging server.
Packaged: the package file has been created. The staging server has not been informed of the deposit.
Transferred: the deposit has been sent to the staging server for further processing and validation.
Received: The staging server has downloaded the deposit file from the journal.
Validated: The package has been validated and scanned for viruses and is now ready for sending to the LOCKSS network.
Sent: The staging server has informed the LOCKSS network that the deposit is ready.
Received: The LOCKSS network has acknowledged the deposit.
Syncing: Nodes on the LOCKSS network are downloading and verifying the deposit.
Agreement: The nodes on the LOCKSS network have checked that they all have a copy of the deposit.
Nodes in a LOCKSS network “vote” on whether they agree that a given deposit is a bit-for-bit copy of the original. This status indicates whether the nodes on the LOCKSS network are in agreement or not.
Yes: the deposit has been delivered to all nodes in the LOCKSS network and there is no further processing to be performed.
No: some processing or voting by the nodes is outstanding. It can take up to one week from the time a deposit is created to when “Yes” appears in the Complete column.
If there was a problem processing the deposit, it can be reset. Once a deposit is reset, it will be repackaged and sent to the staging server for processing again.