UKLA Roundup: April 2012

The April 2012 roundup from the UK LOCKSS Alliance support service is now available.

The intention of this roundup is to highlight ongoing system and content development, and to keep members informed of the activities of EDINA and other UKLA members.

Please note in particular the forthcoming UKLA Members’ Meeting, the newly published LOCKSS and SFX integration guide, and the newly released ‘how-to’ videos.

If you have comments, queries, or suggestions for future content please contact edina@ed.ac.uk.

Posted in Content, Documentation, Events, News | Comments Off on UKLA Roundup: April 2012

Removing items in LOCKSS

There is often confusion over the difference between removing an AU (Archival Unit), and deactivating an AU.

LOCKSS UI: Remove Titles option

LOCKSS User Interface, highlighting the "Remove Titles" option

What is the difference?

There is a subtle difference between these two options; deactivation does the same as removal, except that it retains a record of the titles that have been deactivated so that they can be more quickly reactivated later. When you deactivate a title, you will subsequently see the Reactivate Titles option in Journal Configuration. We hope to simplify the list of options in a future version of the LOCKSS software, as part of the upgrade and simplification of the user interface.

It is however important to understand the purpose and effects of the Remove Titles option. When you remove an AU, you are removing it from the configuration; it is no longer configured for collection and will not be available via LOCKSS in your OPAC. However if it has already been collected, the content will remain on your LOCKSS box. If you choose to add the AU again, it will not need to be downloaded again.

Why are AUs not easily deleted?

This two-step process (remove from configuration, remove content from drive) is designed to prevent an administrator from accidentally removing content via the user interface. Preventing accidental loss is important as not all archived content can be restored – for example if the publisher has since stopped providing it.

If you want to completely remove AUs from your drive to free up space, please contact LOCKSS support.

How would you use the remove function?

A common scenario where a user may remove content previously configured for collection is when:

  1. Your institution does not have access to the title.
  2. The title is no longer available from the publisher.

If the title has already been collected to your box, neither of the conditions above will matter; but if it has not been collected and access is not available for either of these reasons, your box will not be able to collect it from any other source. This is true even if you once had access. (This is an argument for prioritising at risk titles.)

The above scenario demonstrates the permission or availability problems that the LOCKSS software may encounter when trying to collect any of the AUs. Work is underway to update the LOCKSS user interface in both appearance and functionality, and as part of these improvements it will be easier to identify AUs which are suffering from permission problems, and to then remove them from the configuration directly.

Why is it necessary to remove AUs?

Many institutions simply add all available content to their LOCKSS journal configuration, regardless of which journals they are actually subscribed to. There is no harm in using this approach as LOCKSS will not collect content to which you are not permitted access, but establishing the lack of permission will inevitably take time that could be better used in collecting the content to which you do have access.

Once the system has established that it cannot collect the content, removing content will clean up your interface, making it easier to identify the content which has been successfully collected. The better reporting planned for the user interface will allow you to identify and remove problem titles easily.

Note that if you have previously had access to a title but have cancelled your subscription, you are still able to maintain a copy in your LOCKSS box and serve it to your users. This is a fundamental feature of LOCKSS.

Questions

As part of the planned UI improvements, we are looking at how to simplify the common processes that an institution needs to perform. As such, we would be interested to know when and why you use the Remove Titles option, if at all. Please feel free to add comments below to tell us:

  1. Do you ever use the remove titles function in the LOCKSS user interface?
  2. What institutional reasons would lead you to remove a title?

 

Posted in Documentation, News, Support | Tagged , , | 2 Comments

UK LOCKSS Alliance at UKSG Conference

Join us for a drink at the UKSG 35th Annual Conference and Exhibition!

The UK LOCKSS Alliance will be hosting an informal event between 17:00 and 18:00 on Tuesday 27th March, in the Morar seminar suite located on the upper floor of the SECC.  Unwind with us before moving on to the formal dinner later that evening.

Wine, juice and canapés will be served from 5pm.  We will take this opportunity to highlight recent developments to the LOCKSS e-journal archiving initiative, notably how integration with link resolver systems is helping institutions provide continuing access to archived scholarly content.  We also wish to introduce the Keepers Registry, the international facility which records who is looking after the world’s e-journal content.  This should take around ten minutes, leaving plenty of time for questions, discussion and networking with colleagues.

It would be helpful if you could register interest by emailing a.rusbridge@ed.ac.uk.  We look forward to seeing you there!

*****

  • Where: Morar Seminar Suite
  • When: Tuesday 27th March
  • Time: 17:00 – 18:00

*****

— About the UK LOCKSS Alliance —

The UK LOCKSS Alliance is a co-operative organisation whose goal is to ensure sustainable, continuing access to scholarly work over the long-term.  The Lots of Copies Keep Stuff Safe (LOCKSS) initiative ensures libraries remain central to the process of scholarly information management, providing libraries with tools to build local collections of material their readers care most about.  Learn more at http://www.lockssalliance.ac.uk and http://www.lockss.org

— About the Keepers Registry —

The Keepers Registry Beta service provides easily accessible information about the archiving arrangements for electronic journals.  The Keepers Registry is an output of the JISC funded project, Piloting an E-journals Preservation Registry Service (PEPRS), and has been jointly developed by EDINA, a national data centre based at the University of Edinburgh, and the ISSN International Centre in Paris.  Learn more at http://thekeepers.org

Posted in Events | Comments Off on UK LOCKSS Alliance at UKSG Conference

UKLA Roundup: February 2012

The February 2012 roundup from the UK LOCKSS Alliance support service is now available.

The intention of this roundup is to highlight ongoing system and content development, and to keep members informed of the activities of EDINA and other UKLA members.

If you have comments, queries, or suggestions for future content please contact edina@ed.ac.uk.

Posted in News | Leave a comment

Publishers and Titles in the Global LOCKSS Network

UK LOCKSS Alliance members have requested clearer information on the titles available in the Global LOCKSS Network.  Over recent months, development staff at EDINA have contributed effort to improve the process around this reporting.  Our ability to report has been assisted by significant metadata improvements made throughout 2011 by the Stanford LOCKSS team, and utilises output from the recent Title List feature.

Titles committed and preserved in the Global LOCKSS Network

An updated list is now available on the LOCKSS website.  The report lists all e-journal titles that are committed to the Global LOCKSS Network.  The “Preserved” columns lists the volumes that have been preserved in the Global LOCKSS Network.  The “In Progress” columns lists the volumes that publishers have given explicit permission to preserve and that are in-line to be processed and preserved.  We also report on those publishers that have committed their content but have not yet made available explicit permission statements; these titles are listed without an entry in either the “Preserved” or “In Progress” columns.

Posted in Content, News | Comments Off on Publishers and Titles in the Global LOCKSS Network

UKLA Roundup: January 2012

The January 2012 roundup from the UK LOCKSS Alliance support service is now available.

The intention of this roundup is to highlight ongoing system and content development, and to keep members informed of the activities of EDINA and other UKLA members.

If you have comments, queries, or suggestions for future content please contact edina@ed.ac.uk.

Posted in News | Comments Off on UKLA Roundup: January 2012

Updated Quick Start guide now available

An update to the UK LOCKSS Alliance QuickStart guide (version 1.2) is now available, with an extended section describing how to monitor content collection.

Posted in Documentation | Tagged , , , | Comments Off on Updated Quick Start guide now available

UKLA Roundup: December 2011

The December roundup from the UK LOCKSS Alliance support service is now available.

The intention of this roundup is to highlight ongoing system and content development, and to keep members informed of the activities of EDINA and other UKLA members.

If you have comments, queries, or suggestions for future content please contact edina@ed.ac.uk.

Seasons Greetings! Photo source: http://www.flickr.com/photos/webmink/3270983/

Finally, from all at the UK LOCKSS Alliance Support Service, EDINA and the Stanford LOCKSS team, Merry Christmas and best wishes for 2012!

Posted in News | Comments Off on UKLA Roundup: December 2011

LOCKSS Daemon 1.52.3 now available

LOCKSS Daemon 1.52.3 is now available, with accompanying release notes.

To check which daemon is running on your LOCKSS box, the simplest method is to login to the LOCKSS user interface.  The daemon version is listed at the bottom of each page, as indicated in the image below.


To manually upgrade to the latest daemon, run the following command as root:

yum update lockss-daemon

To configure your machine to upgrade automatically,  run the following commands as root:

chkconfig yum-cron on
service yum-cron start


OpenBSD users should note:  this is the final OpenBSD release! If your LOCKSS box is still running an OpenBSD platform, please contact the UKLA support service at edina@ed.ac.uk as soon as possible to begin the transition.

Posted in News | Tagged | Comments Off on LOCKSS Daemon 1.52.3 now available

UKLA Roundup: November 2011

The first regular roundup from the UK LOCKSS Alliance support service is now available. Regular communication was requested at November’s Steering Committee meeting and was a clear requirement from a recent review of membership.

The intention of this roundup is to highlight ongoing system and content development, and to keep members informed of the activities of EDINA and other UKLA members.

If you have comments, queries, or suggestions for future content please contact edina@ed.ac.uk.

Posted in News | Tagged , , , , | Comments Off on UKLA Roundup: November 2011