PKP Private LOCKSS Network
Current status: pilot phase
The Public Knowledge Project Private LOCKSS Network (PKP PLN) is currently in a pilot phase. Selected journals hosted at the University of Victoria, University of Pittsburgh, University of Alberta, University of British Columbia, Indiana University, and Simon Fraser University are participating. When the pilot is completed by Fall 2015, all journals using Open Journal Systems will be able to join the PLN provided they meet the following criteria:
- The journal must be running the most current version of OJS (at least version 2.4.5)
- The journal must have an ISSN
- The journal must have published at least one year’s worth of content
Note that the PKP PLN is only one of several Private LOCKSS Networks that preserve OJS content. Information on other LOCKSS networks that preserve OJS content is available on the LOCKSS website.
The PKP Private LOCKSS Network (PLN) will:
- provide preservation services for any OJS journal that meets minimum requirements. These are yet to be determined but may include having published one year’s worth of content and having an ISSN
- allow OJS journal managers to register their journals for inclusion in the PLN by simply enabling a plugin in their OJS instance and agreeing to a small number of terms in the Preservation Agreement
- on registration of a journal, automatically determine if the registered journal meets the minimum inclusion requirements
- preserve the raw journal content as generated by OJS’s existing export tools
- automatically harvest new content from registered journals and add the content to the PLN, eliminating manual staff intervention at PLN member sites
- provide access to preserved content after a “trigger event” has been communicated to PKP by the journal manager or PKP staff cannot contact the journal manager and the journal is no longer accessible.
How your journal content is preserved, and how it will be made available for use
An overview is available of how journal content is preserved in the PKP PLN, and how it is made available for use after a trigger event.