Lee Library Information Systems Task List
| Description: | Change in ownership and project definition meeting |
| Projects: | LOCKSS |
| Priority: | 99 | Task ID: | 854 |
| Long Description: | This meeting was held on October 12th, 2004, to discuss change in ownership of the project and to define its scope. Our goal was to create a project definition statement. |
| Status: | Open |
| Owner: | Laycock, Grant | Contributors: | Murdoch, Robert |
| Due: | TBD | Opened: | 11/18/2004 |
| Changed: | 12/20/2004 | |
| 11/18/2004 | The following project definition statement was created:
The purpose of this project is to demonstrate support for the LOCKSS project, explore the value, opportunities and limitations of participating in a national digital archive, address questions concerning LOCKSS, and to provide an access path to LOCKSS data to test concept and functionality. |
| 11/18/2004 | The team was asked to think about questions we need answers for. We came up with the following, but will continue to develop this list:
- What journals are candidates for LOCKSS?
- Should we create a local network using the LOCKSS software?
- Can we use OpenURL to access journal articles in LOCKSS?
- When do we go to LOCKSS for a journal article? Because it is faster? Because the site is down? Because subscription has expired?
- How do we gain access to Journals in LOCKSS?
- What is the criteria for getting data into LOCKSS?
- What do we get for our subscription to LOCKSS?
- What is the process for negotiating with vendors to have journals put into LOCKSS?
- Can people remove content from LOCKSS? What do contracts say about this?
- How do we demonstrate we have access to a LOCKSS journal?
- How does a publisher verify a subscription?
- What BYU material would we want to put in LOCKSS? What are the contractual agreements involved in doing this?
|
| 12/20/2004 | Bill Lund writes:
At the CNI meeting on 12/7/04 there was a meeting of LOCKSS libraries, where I was able to get some answers.
- What journals are candidates for LOCKSS?
- At this point the only journal candidates for LOCKSS are those which are "born digital" meaning that they do not exist as a printed document. This actually leads to a larger discussion since the LOCKSS project is talking about LOCKSS as a repository for DSpace and ETDs. These are clearly not journals at all.
- Should we create a local network using the LOCKSS software?
- We can do this, but it would not be a part of the LOCKSS network administered by Stanford. We may want to consider this for non-document collections, building something that is distributed to UALC and CES as a single network.
- Can we use OpenURL to access journal articles in LOCKSS?
- That would depend on the OpenURL resolver. This is nothing in LOCKSS that would prefent this. In some respects it may even be transparent to the OpenURL resolver. One of the ways to configure the LOCKSS system is to use a proxy that will redirect all requests for specific journal items (not the vendor's search page) to LOCKSS, which will then try the vendor first, then the LOCKSS cache to resolve the request. In this case the OpenURL resolver wouldn't need to even know about LOCKSS.
- When do we go to LOCKSS for a journal article? Because it is faster? Because the site is down? Because subscription has expired?
- As outlined above, LOCKSS itself can make this decision, relying on the cache only if the vendor does not respond quickly, either because they are busy or down.
- How do we gain access to Journals in LOCKSS?
- I still don't have a clear answer on this one, but see the question below that is similar. This may be moot at this point.
- What is the criteria for getting data into LOCKSS?
- The process is to first build a "plug-in" that incorporates a digital journal into LOCKSS. The U is apparently doing this. We should probably talk to Kenning. Then we need to get other LOCKSS participants to "collect" that journal. We need more details here. Stanford has promised to provide some type of developer's guide.
- What do we get for our subscription to LOCKSS?
- Access to the journals on the LOCKSS list. Also we can assist in determing the direction of the project. For instance, one of the issues discussed was using LOCKSS for ETDs and as a long-term repository for DSpace. These are both very interesting. They are going to be listening to the subscribers when looking at future directions.
- What is the process for negotiating with vendors to have journals put into LOCKSS?
- This was one of the issues discussed at length. No one really seems to know what needs to be done with the publishers. In general terms they are asking that when we negotiate our contracts with the vendors, that we ask them to provide their content into the LOCKSS system with a clause in our contract that says that we have perpetual access to the content of the years when we have a subscription. Vicky Reich will be sending more information on what is needed.
- Can people remove content from LOCKSS? What do contracts say about this?
- The LOCKSS contract with the vendors does not permit them to remove content once it has been added.
- How do we demonstrate we have access to a LOCKSS journal?
- I don't know. Actually at this point I believe most if not all of the content in LOCKSS is open. No subscriptions are required.
- How does a publisher verify a subscription?
- I don't know. Actually I think that the LOCKSS administrators have to enable this. We have to demonstrate to them (in some way) that we have a subscription, but based on the previous question, this may be moot at this point.
- What BYU material would we want to put in LOCKSS? What are the contractual agreements involved in doing this?
- See the answers above for some answers to this.
|
| Description: | WebFeat Connector for DSpace |
| Projects: | DSpace |
| Priority: | 99 | Task ID: | 889 |
| Long Description: | If we don't make DSpace visible, it won't be very useful. We need a WebFeat connector so that it can be searched. |
| Status: | Open |
| Owner: | Murdoch, Robert | Contributors: | |
| Due: | TBD | Opened: | 2/25/2005 |
| Changed: | 2/25/2005 | |
| 2/25/2005 | Asked Robert Murdoch to have the connector made. |