New experimental features in LOCKSS

The LOCKSS development team have been working hard over the summer to implement new functionality to assist collection administration and management.  Three new experimental features are available for use.

Note, these new features are being tested by the user community and if you enable these features you may encounter minor problems.  We’d appreciate your help in testing and improving them:  please send feedback to  Please send comments on usability, bug reports, and additional feature requests.  Expanded documentation will be released in future months.

Subscription Manager

To reduce collection management requirements, system administrators will use the Subscription Manager to register institutional ‘holdings’ for each title so that when new volumes are released, these are configured automatically for collection by the institution’s LOCKSS box.

To enable the SubscriptionManager feature, add the following parameters to ExpertConfig and restart LOCKSS:

  • org.lockss.subscription.enabled=true
  • org.lockss.metadataManager.indexing_enabled=true
  • org.lockss.dbManager.enabled=true

Initial and draft documentation for the SubscriptionManager feature is now available.  If you have comments on the documentation, please contact

Display Content Status

To assist with collection management the Display Content Status function shows you what content is configured for collection and, within that, what has been collected successfully and where problems have arisen. 

To enable the DisplayContentStatus feature,  add the following parameters to ExpertConfig and restart LOCKSS:

  • org.lockss.ui.transitional=true

COUNTER reports

LOCKSS can now generate reports compliant with the latest COUNTER Code of practice for e-resources.  It is possible to generate both a JR1 and JR5 report. Each report appears in two versions, one of them with the postfix “L” (for “L”OCKSS). 

  • Reports with the “L” postfix include all the usage requested through the LOCKSS box. By default, when content is requested through a LOCKSS box the request is forwarded to the publisher. If the publisher’s content is different or newer than that preserved by the LOCKSS box, the publisher’s version is served. The “L” report includes these usages.
  • The reports without the “L” postfix include only usage where the LOCKSS box could not involve the publisher (which is rare) to avoid double-counting the hits. The underlying assumption is that the publisher will include, in its own COUNTER report, the hits of which it is aware .

We suggest enabling this feature once you have integrated LOCKSS with your institutional link resolver system.

To enable the COUNTER reports feature, add the following parameters to ExpertConfig and restart LOCKSS:

  • org.lockss.metadataManager.indexing_enabled=true
  • org.lockss.dbManager.enabled=true

Comments are closed.