Recent changes to Canada’s Copyright Act have propelled copyright and licensed use into the spotlight at colleges and universities in Canada. This session will look at Queen’s and University of Toronto libraries’ experience implementing a licensing permissions workflow using OCUL Usage Rights database (OUR). The systems will be covered are: 360 Link, Summon, Voyager OPAC, Endeca. We will explain how to implement the license links with and without using API.
Transparent Licenses: Making user rights clear (OLA Super Conference 2015)
1. 1
Transparent Licenses: Making user
rights clear
Amaz Taufique, Assistant Director, Systems and Technical
Operations, Scholars Portal, OCUL
Christina Zoricic, Metadata Management Librarian, Western
University
Jenny Jing, Information Systems Librarian, Queen’s University
Marc Lalonde, Digital Library Coordinator, University of Toronto
2. 2
• Shared technology service of the 21 university libraries
of the Ontario Council of University Libraries founded
in 2003
• Provides content aggregation and preservation services
for member libraries
• Journals – 16,461 and 40 M articles
• Books – 610,000 ebooks
• GeoPortal – GIS Data
• ODESI – Numeric Data
• Dataverse – Research Data
• OUR – Licenses
What is Scholars Portal
3. 3
Summer 2011
• Events Surrounding Access Copyright =
Major Impact to University Library Systems
• Investigate available options
– Available systems (Verde/homegrown) didn’t cut it
• Ideal Solution
– Easy to implement/use/share
– Multilingual
– Cheap/Free
4. 4
UBC Mondo License Grinder
• Designed to be a back end tool
• Was being used at UBC as license cataloging software
• Open Source
• University of Windsor was using it and linking it into SFX
• OCUL started investigating if it could be re-purposed
• Lots of Potential and was simple to Develop (LAMP
stack)
5. 5
Consultation
• Lawyers
– Helped with legalese
• Librarians
– display usage rights directly in OpenURL menu
– bilingual
– share the work of capturing usage rights for
consortial licenses
– Make it ours
14. Licensing Project Plan
Mandate:
Provide users with access to information about licensed
use for all electronic content at Western Libraries
Timeline:
8 months (May-December 2014)
15. Licensing Project Plan (… cont’d)
Project Goals:
Find and identify all active signed licenses
Link to information about licensed content across all
access points (catalogue, discovery layer, external
databases)
Embed licensing element into existing workflows
Create a manual/procedures for the process
16. Licensing Project Team
Two Librarians
Two Library Assistants
Support from:
Other library staff
Library ITS
Customer Service Standing Committee
Western’s Copyright Advisor to the Provost
17. Library Assistant Training Plan
Compiled list of resources
How to read a license
No interpretation allowed
Double blind method
Weekly meetings to discuss questions and issues
20. Some project numbers:
Started with 1819 ERM records
31 obsolete records deleted
Focused on records with holdings attached: 898
893 records link to licensed use information
(over 360 000 access points!!!)
95 problem records unlinked
Side benefit:
Fixed over 100 broken links and access problems!
25. The problems of (trying) to maintain two
knowledge bases
Serials Solutions holdings management and
coverage loads into the catalogue
SFX link resolver
26. Next steps…
Mapping OUR records to SFX
Work in progress
More committees and working groups
Evaluating link resolvers
28. To OpenURL Link Resolver: 360 Link
To OPAC: Voyager 8.2 & Voyager 9
To Discovery System: Summon 1& 2?
29.
30. SP OUR
DBs
360 Link
DBs
DBs
matched
by names
Title _360 Title_SP License URL in SP OUR
ABI/Inform ABI Inform Global http://base/ABI_Inform
Springer Springer eBooks http://base/Springer_eBooks
ACM Digital
Library
ACM Digital Library
http://base/ACM_Digital_Lib
rary
31. 360 Link
- ABI/Inform
- Springer eB
ProQuest
DBs
Matched
- ABI Inform
- Springer
A Queen’s
internal DBABI Inform global
+ URL
SP OUR
Springer+ URL
Queen’s ERM
Maintained DBs
SP OCUL
Maintained DBs
DB names
+ URLs
URLs
DB of DBs
• Springer
Queen’s ERM
Maintained
DBs
DB names
Matched
- ABI Inform
- Springer
DB names
+ URLs
URLs
Assign URL
using a
mapping tool
32.
33.
34.
35.
36.
37. But using the Publisher Info is not accurate to get
the license links for some resources
41. 三人行,必有我师.
There must be a teacher
for me among
any three companions.
•UBC: Teresa Lee
•360Link: Matthew Reidsma
•Summon: Wittawat Meesangnil
•Scholars Portal: Amaz Taufique
•University of Toronto: Marc Lalonde
•Western University: Christina Zoricic
Acknowledgements
42. • Associate University Librarian: Michael Vandenburg
• Copyright Specialist: Mark Swartz
• E-Resources Librarians: Anne Brule & Ellen Symons
• Web Coordinator: Katie Legere
• Web Development Technician: Andrew DaCosta
• Application Support Technician: Alex Fletcher
55. 56
Managing Mappings Dilemma
• How do we manage mappings?
– Excel file/database to map databases->licenses
– Manually/programmatically enter license URLs in various
ERMs, Catalogs, OpenURL Menus, etc.
– Not easy to share
– Still very tedious
56. 57
Potential Solution
• UofT created mapping tool
• SP imported it into OUR
• For Serial Solutions, Catalogs, etc.
• Import Active DBs into OUR regularly and create mappings to licenses
• Use APIs to query OUR for license information directly from platform
• For SFX
– Active targets appear in real-time in OUR
– Create Mappings
– Automated process pushes out info into SFX note field
At OCUL we started to Investigate options to store and display our license information
CURRENT SYSTEMS:
VERDE –
ERM tool with a licensing component, not everyone was using it, Cumbersome, Difficult to use, Costs Money, Steep learning curve
HOMEGROWN
Needed development time, Not easy to share, Only feasible for larger universities
None of these options met the needs of the consortia WHICH WERE
Can Mondo be repurposed and further developed to fit the needs of OCUL?
We decided to give it a shot and develop requested features in house
Librarians Provided initial feedback on wish list of features
But the number one requested feature was for consortial licenses. So we re-wrote the application to support consortial instances that pushed out data to it’s members.
MAKE IT OURS, literally and acronymically. We called Online Usage Rights (OUR).
Here’s the model we used for license sharing:
CRKN staff enter CRKN negotiated licenses into OUR.
We enter licensing information once and that information would get propagated to appropriate Child instances?
In this example any licenses that CRKN staff create will automatically propagate to any schools with an instance in SP OUR.
Each consortia also has their own instance
These licenses appear as “READ ONLY” Licenses, schools cannot edit them. They can choose to activate/deactivate them.
A hot enhancement request was SFX integration. So we created an “SFX” view and called it from within an iframe that we embedded in an SFX targets’ note field
But the whole idea of creating these licenses was to be able to display them at the time of consumption. At SP, we started displaying OUR usage rights on our E-journals Platform (using the OUR API).
“one of these things is not like the others” How did I wind up in a presentation with a bunch of Systems people?
December 31st, 2013 marked the end of UofT and Western’s agreement with Access Copyright, and the launch of copyright@Western.
As Western stepped away from the Access copright deal, the university outlined three goals to help the Western community make informed decisions when using the published work of others in research and teaching:
Education
Information resources
Services
Harriet Rykse and I were responsible for leading the project and we received special funding to hire two Library Assistants on contract, May Dew-ong and Amberley Zavitz - they have been very valuable in the process - May has a legal assistant background and Amberley, an archival description background so together they’ve made an excellent team.
We also relied on support from our ITS department, the library’s customer service committee and the university’s copyright advisor, Tom Adam.
This is part of one of the first decision maps we developed for the whole project. As you can see, the process is quite complicated and labour intensive.
OUR Database was ready and waiting for us to implement, people were talking about this issue on listservs
Right before our two contract library asistants were set to start, we attended the OUCL workshop – “Thinking OCUL-y: Licensing and Collections Symposium” held at the university of toronto - by the end of the day, walking to catch our train home, Harriet and I had totally changed our plan for how the work would get done! Many thanks to Jen Robertson At UofT for sharing some of her processes loading licenses! :)
Photo credit: Daniel Torres Bonatto
In recent years, library collections shift from print version to e-resources, which means library ACQ changed from purchasing materials to license materials. It’s important for us to add the license information to library systems.
In the summer of 2013, we migrated our OpenURL Link Resolver from SFX to 360 Link. We managed to add the license lnfo. to our 360 Link result page August 2013.
In this session I will show you the following things:
First, let me explain how we made the license database.
- Scholars Portal is a service of the Ontario Council of University Libraries. It provides a shared technology infrastructure and shared collections for all 21 university libraries in the province.
One of SP’s service is to provide each member an instance of the OCUL Usage Rights (OUR) Database. Which we created with SP and they maintain for us.
I will show you what it looks like on the users’ end of the OUR DB in the next slide.
Then I will go over each library system which we added the license link and the issues/lessons we’ve learned.
This is the users’ interface of the Queen’s Library’s OUR DB. There are about 600 license pages for our e-resources.
The users can search and find the terms of use for each resource. And here is an example what the license page looks like.
The db names are called differently between SP and 360Link, first we need to match them in an internal db.
We also need to normalize the names and match them to make an internal database, which contains the names from the two resources and with the URLs of the license pages.
Here is what it looks like.
We have the SP’s OUR DB, and we have the 360 Link databases from our vendor ProQuest. The database names in these two resources are different.
In order to assign the license page links to the resources in 360Link, we need to match the titles in these two places and add the url of the license links to 360 Link dbs
We learned from University of British Columbia that we can add the license url manually in SS’s Client web site. Thanks to UBC. But we have about 2000 records so that we tried another approach.
The time frame for adding the license info to 360link (May to July)
After we talked to Western University about this project, we learned that they added the license links to their OPAC. So we tried to add it to our Voyager. Here is the Voyager Skin’s file structure and some of the config files we need to learn and modify in order to edit the Voyager skin.
Confucius
Dec 2013 The University of Toronto announced that it was unable to reach an agreement with Access Copyright
Library was committed to display usage rights on as many user interfaces as possible
UsingAPI an to query the Online Usage Rights (OUR) database using resource name or license name
Transform JSON to display on our various applications
Search for articles
Click on the search results page gives you summary
Click on the title and you get to the 360 Link helper window brings you to detail page
Click on more options link brings you permitted uses summary for each database
Click on catalogue link and you get to summary on catalogue record detail page
Click on details page and you get to HTML page hosted on Scholars Portal
Article search: Tony Judt
Catalogue search for eBook: Marmot Biology
eJournal search: Education
End goal is to deliver this info to users at time of consumption
We have to Manually/programmatically enter license URLs in various ERMs, Catalogs, OpenURL Menus, etc.
Because we host SFX, we have access to the database and so we can do a lot of cool things.
Use APIs to access this data…
By License Name:
By Database Name:
By Serials Solutions DB Code:
By Serials Solutions DB Code: