Lockss at cornell
Download
1 / 10

lockss at cornell - PowerPoint PPT Presentation


  • 177 Views
  • Uploaded on

LOCKSS at Cornell. DLF Spring 2005 Forum Bill Kehoe, Cornell University Library. Topics. System Administration Adding a journal—Plug-ins Retrieving items from the local system Costs Another use for LOCKSS. System Administration. It’s a snap to install First time: couple of hours

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'lockss at cornell' - Samuel


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Lockss at cornell l.jpg

LOCKSS at Cornell

DLF Spring 2005 Forum

Bill Kehoe, Cornell University Library

Bill Kehoe – DLF Spring 2005 Forum


Topics l.jpg
Topics

  • System Administration

  • Adding a journal—Plug-ins

  • Retrieving items from the local system

  • Costs

  • Another use for LOCKSS

Bill Kehoe – DLF Spring 2005 Forum


System administration l.jpg
System Administration

  • It’s a snap to install

    • First time: couple of hours

    • After that, almost automatic—the install process uses the previous, site-specific configuration

    • watch over it, do what it asks—write protect the floppy

    • ½ to 1 hour—one eye on the process.

Bill Kehoe – DLF Spring 2005 Forum


Story acl horrors l.jpg
Story—ACL Horrors

  • Early days—Cornell had no firewall

  • ACL put on individual subnets

    • ACL is the list of holes through the firewall

    • A list—specific protocols allowed at specific ports

      • TCP/IP—8080, 8081/ UDP – 5555, 5554

    • Intent: Block Off-campus traffic into Cornell

  • Changed the machine IP—no more incoming traffic

    • Bad for the LOCKSS system, but I’m not worried—it repairs itself

    • Central IT folks say it,s not their fault; Tom says it’s not the LOCKSS system

    • Two months of back and forth, not every day, because I don’t want to insult anyone

    • Email from CIT: “Oops.”

Bill Kehoe – DLF Spring 2005 Forum


Anecdotal plug in writing experience l.jpg
Anecdotal plug-in writing experience

  • First time—maybe two hours, as I learned how the harvesting rules worked, and a back and forth with Tom

  • After that—less than half an hour

  • I don’t do it frequently enough to remember what’s required for each element

  • The Building a Plug-in tutorial is very helpful.

Bill Kehoe – DLF Spring 2005 Forum


What s not so clear about plug in writing l.jpg
What’s not so clear about plug-in writing

  • What is the atomic unit for the journal—a volume, an issue, a year?

  • Should there be a plug-in for each unit?

  • Some publishers change directory naming conventions over the years.

  • How many plug-ins to build?

Bill Kehoe – DLF Spring 2005 Forum


Retrieving items from the local system l.jpg
Retrieving items from the local system

  • The LOCKSS Winter 2005 Card

  • http://libdev.library.cornell.edu/lockss

Bill Kehoe – DLF Spring 2005 Forum


Time costs l.jpg
Time Costs

  • Time

    • Selector

      • Selection decision—15 minutes to 1 hour

      • Conversation with publisher—30 minutes to 1 hour

    • Techie

      • Evaluate journal for technical feasibility—30 minutes to 1 hour

      • Write plug-in—15 minutes to 1 hour

      • Converse with publisher techie and LOCKSS team—30 minutes

  • Total—2 to 4 ½ hours

Bill Kehoe – DLF Spring 2005 Forum


Network costs l.jpg
Network Costs

Bill Kehoe – DLF Spring 2005 Forum


Another use for lockss l.jpg
Another Use for LOCKSS

  • Ensuring Access to Mathematics Over Time

    http://www.library.cornell.edu/dlit/EATMOT

  • OAIS information model lacks a level of metadata that describes partnerships in collaborative archives.

  • EATMOT repository: XML-encoded metadata about the partnership members, rights agreements, storage capabilities, preservation policies.

  • LOCKSS for the repository—inexpensive, format-agnostic, self-repairing, no one owns it.

Bill Kehoe – DLF Spring 2005 Forum


ad