| USMAI Consortium of Libraries |
| University System of Maryland and Affiliated Institutions |
| Electronic Resources Management Task Group > Minutes for February 27, 2006 |
Minutes- February 27, 2006
1-4pm, ITD Conference Room
Homework and Next Steps were briefly discussed. Kari, Laura and Betty will be sending out to the ERM Task Group licenses to map out over the next two weeks. May need to flag some for renegotiation. We will meet again in two weeks to review the licenses and determine recommended practices and values for completion of licensing section of VERDE information.
Betty reported that staffing for the VERDE project will be a little lean over the next couple of weeks, as Dave Kennedy is on leave. We will keep focused on the licensing section of the project. When we move to the implementation stage, Frostburg will be the first campus to come up live.
We thanked Kari for all of her great work with ERM review and implementation planning, and for all of her work at ITD. She will be greatly missed!
Most of the meeting was spent reviewing the assigned licenses and mapping their values to VERDE fields. There were many interesting and detailed discussions on various terms in the VERDE fields and how they are interpreted.
The following are items that were generally agreed upon as best practices or defaults.
Kari noted that there is no place in the licensing terms to note any invoicing requirements and dates. Need to check the Acquisition record to see what is available to have a tickler for when licenses are up for renewal. Also, need to check workflow to verify that this information is available when needed.
General Terms- This is a catch all for anything important in the license that does not fit in any of the other designated fields. This may be blank.
Local authorized user definition- Only indicate Y, if the wording in the license is USMAI preferred language.
Under the section TERMS, ITD will speak with the campus legal counsel to obtain their opinion of what to do as a "best practice" if ILL is not specifically detailed in the license agreement. Also, ITD will obtain this legal review for terms dealing with Course Packs and Scholarly sharing. This will determine what we do for consortial licenses, if they are silent on ILL, Course Packs and Scholarly sharing. Each campus may get different opinions from their campus legal counsels for the unique campus licenses.
Until we receive advice from counsel, the following are the TG's recommended encodings:
ILL
Scholarly Sharing:
The Berkeley license said "for purposes of research, teaching, and private study" and didn't say anything else about not sharing, and we encoded that as 'permitted (interpreted)'-presumable on the basis of that 'research usage'. Question: what if it doesn't say any of those things? So far we haven't had an example like that. Is that also a 'permitted interpreted".
ILL term note- This field should explain why the ILL fields were coded a certain way.
Database Protection Override-This was discussed at the last meeting and Nathan obtained additional information on the term from Ivy Anderson. This is her explanation of the clause.
"If the Licensed Materials are database, compilation, or collection of information, Authorized Users shall be permitted to extract or use information contained in the database for educational, scientific, or research purposes, including extraction and manipulation of information for the purpose of illustration, explanation, example, comment, criticism, teaching, research, or analysis.
The intent is to pro-actively permit those activities that otherwise might be prohibited in database protection legislation should that be enacted in the U.S. (as it already has been in Europe). "
It was suggested that this needs to be a text field, instead of a Y or N field. Need text of statement if it listed in the license. In U.S. licenses it would probably be rare to have this listed in license/
Citation requirement detail- It was suggested that this needs to be a text field. Need to have the information here on what the detail is, not just a Y or N.
Course Pack- After discussion, it was agreed that we would not interpret on the Course Pack fields. If nothing is specifically noted in the license, it would be coded as Silent, and each campus should develop their interpretation of what that Silent means.
Termination Obligations- The term Silent should be added as one of the drop downs.
Achiving format- Need to add Portico.
Applicable copyright law- unless otherwise stated in license the default will be U.S.
Content warranty- Record the actual text from the license in this field.
| USMAI | ITD | Metalib/sfx | Aleph |
| © 2005 University System of Maryland and Affiliated Institutions. Privacy policy |