1 / 9

Linking electronic resources to their licence terms

Linking electronic resources to their licence terms. JISC Collections and ONIX for Licensing Terms. Linking electronic resources to their licence terms. JISC Collections and ONIX for Licensing Terms. Liam Earney. JISC Collections. Introduction. Why? How? Issues and Challenges Conclusions.

muniya
Download Presentation

Linking electronic resources to their licence terms

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Linking electronic resources to their licence terms JISC Collections and ONIX for Licensing Terms

  2. Linking electronic resources to their licence terms JISC Collections and ONIX for Licensing Terms Liam Earney JISC Collections

  3. Introduction • Why? • How? • Issues and Challenges • Conclusions

  4. Why? • Institutions facing a number of issues: • Managing an ever increasing number of licences and their terms and conditions • Correct interpretation of licences • Exploiting the licence terms and conditions that have been negotiated • Demonstrate the value of licensed electronic resources • Population of licence elements within ERMs • Communicate licence terms to users • Potential solution and assistance offered through provision of machine readable licences • Much time and effort put into the explanation of the Model Licence • Individual licences derived from the model require further interpretation and explanation • Ensure consistency of information to institutions

  5. How? • DLF-ERMI • Specification of elements for the mapping of licences • Restricted list that doesn’t capture the full complexity of licences • JISC Collections is constantly updating its licence to take account of changes in technology, user needs and institutional requirements • ONIX for Licensing Terms “a new set of formats that will enable the full range and complexity of licensing terms to be expressed in a structured machine readable form and communicated between systems using a standard XML-based schema” • ONIX for Licensing Terms funded as a project through JISC • Builds on DLF-ERMI work

  6. How? • JISC Collections and ONIX-PL • A standards based approach for widespread applicability and take up • Mapped JISC model licence • Developed ONIX Dictionary to cover usages and definitions • Allows full representation of the licence without omitting clauses • Also allows refinements to be added – not a static representation of licences • JISC Collections using ONIX-PL Editing tool to map licences • First licences now created! • JISC Collections procurement of an ERM with intention of distributing machine readable licences • Ability to work with ONIX-PL included in tender document

  7. Issues? • A standard in development • Will it be adopted? • Commitment from JISC and support from Library Expression Working Group • ONIX-PL adopted as basis for JISC Licence Registry project (RELI) • Ability of systems vendors to read the licences • Currently no demand for ONIX-PL from ERM purchasers, thus little intention to implement • JISC Collections and EDItEUR developing a web interface to display the licences • EDItEUR has produced a mapping of ONIX-PL to the ERMI specifications • Not ideal as lose licence elements • Push for development of the ERMI specification • ONIX-PL Editing tool • Usability • Most recent licence took one hour to create

  8. Conclusions • Clear demand and requirement for machine readable licences for: • Management • Communication • Compliance • Exploitation • Existing tools not able to meet the requirements of developing licences • ONIX-PL • Standard • Consistent • Flexible • Will systems vendors adopt?

  9. Thank you for listening Liam EarneyL.Earney@jisc.ac.uk

More Related