Date post: | 11-Nov-2014 |
Category: |
Education |
Upload: | electronic-resources-libraries |
View: | 554 times |
Download: | 1 times |
A Study of License Terms for Electronic Resource Management
ER&L Conference 2010
Mingyu Chen
University of Houston Library
1
Outlines Background and objectives ERMS at UH ERMI & ONIX-PL Libraries’ needs Vendors’ story E-Resource service provider Crosswalk (Mapping) Solution Proposal Future Research
2
Background
ERMS Storing data Tracking and smoothing workflows Early stage
Rights information Imperative to be available Clear and concise
3
Research Objectives
To provide an overview of the trends and standards of ERMS, its accompanying specifications and applications and to suggest further actions libraries, vendors and ERMS providers can take to implement new license term standards.
4
Research Objectives
To assess whether all the identified issues of ERMS are addressed by the current practices
To identify and prioritize steps to promote better ERMS practices
To illustrate necessary functions needed so that librarians can easily handle growing collections of licensed e-resources
To identify and promote appropriate standards to support data elements and data interchange
5
ERMS at UH Discovery Investigation Trial Licensing Ordering/Payment Access set-up Access verification Cataloging/Database Notification of library
6
License Terms
Rights information License terms
ERMI (Electronic Resource Management Initiative)
ONIX-PL (ONline Information eXchange for Publications License)
7
ERMI
DLF sponsorship of ERMI, started 2002 - published 2004. Workflow Functional requirements ERMS Data Structure Data Element Dictionary 350 License terms Widely used Too complex
8
ONIX-PL
ONline Information eXchange for Publications Licenses
Machine-readable format Directly loaded Linked to Electronic Resources Key usage terms communicated to users Simplified to 108 license terms
9
ERMI vs. ONIX-PLERMI
Not “standard” Implemented in
ERMS Only has data
dictionary Granularity 350 license terms
ONIX-PL
Emerging standard Developed in ERMS Encoding format (XML) Simplified 108 license terms
10
Rights Info Process in UH ERMS
ERMS Serials Solutions 360 Resource Manager
Wish list
Alerts to notes Customizable fields Input more smoothly
11
Crosswalk (Mapping)
ERMI ONIX-PL
License terms: Metadata
ERMI metadata ONIX-PL metadata
MARC DC
12
Crosswalk (Mapping)
ONIX-PL terms
PerpetualAccess AccessBySecureAuthentication InterLibrarySupplyControlledElectronic
ERMI terms
Perpetual Access Right Concurrent Users Interlibrary Loan Secure Electronic
13
Mapping ONIX-PL to ERMI
Simplified or confusing?
New definition vs. Difficult to map reversely
Interpretation issues
14
Example1 Simplified
ONIX-PL
AccessBySecureAuthentication
ERMI
Concurrent Users: number Pooled Concurrent Users: number Concurrent User Note: text
15
Example 2 New Definition
ONIX-PL
CopyAndDistribute
LicenseeRightsAfterTermination
DepositDigitalCopy
ERMI
No equivalent
No equivalent
No equivalent
16
Example3 Interpretation
ONIX-PL
ReproduceIndigitalinstrutionalMaterials
Reproduce a resource in a digital learning object or course reserve
ERMI
Course Materials Electronic
The right to use licensed materials in collections or compilations of materials assembled in an electronic format by faculty members for use by students in a class for purposes of instruction.
17
Libraries’ Needs
Licensing terms
Rights statement always follows Machine readable way User friendly More relevant Easy to manage Compatible with other metadata standards More flexibility Growth of electronic resources
Can vendors help?
18
Story on Vendors’ Side
Willing to satisfy libraries’ needs Waiting for a signal to start Joint efforts among vendor-library-ERMS provider
19
ERMS Provider’s Concern
20
Serials Solutions
Defined a project to implement ONIX-PL No immediate development plan Right time Limited “pilot” study
21
What’s next?
Challenges Direction Yes or No Intermediate solution?
22
PROPOSAL
Additional time for all three parties No major change in ERMS Easy system implementation Adaptability & Flexibility Metadata: XSLT conversion
23
Intermediate Solution
24
Solution Flow
25
Pros and Cons
Pros:◦ Low Cost/Less efforts◦ Leave time for all parties to adapt themselves to changes
◦ Cons:
◦ Intermediate solution◦ Extra work for libraries◦ Both libraries and vendors need expertise for both
license terms
26
Future Research
Continue data collection from libraries, vendors and ERMS providers
Balancing between ERMI and ONIX-PL XSLT conversion Prototype system update Prototype system analysis Vendor feedback ERMS provider feedback
27