inc-lib-vendor - Walk-ins
Subject: InC-Lib-Vendor
List archive
- From: "Kent Percival" <>
- To: <>
- Subject: Walk-ins
- Date: Fri, 7 Aug 2009 14:02:56 -0400 (EDT)
In the 2007 12 version of eduPerson
(see http://middleware.internet2.edu/eduperson/docs/internet2-mace-dir-eduperson-200712.html),
Library Walk-ins are described through the following note. I’m not
sure it really helps the case since it seems to suggest that the definition
could vary depending on license terms with vendors! Libraries certainly
use the term in different ways. At Guelph, “walk-in” us
mostly used to describe users from outside the University community – those
without a University ID. "Library-walk-in:" This value is intended to
facilitate the handling of a fairly widely encountered agreement between an
institution and licensed resource providers that e-resources may be made
accessible to students, faculty, staff and library walk-ins. This term
originally indicated people who were physically present in a library facility.
In recent years the library walk-in provision has been extended to cover other
cases such as library users on the campus network, or those using on-campus
workstations. Licensed resource providers have often been willing to interpret
their contracts with licensees to accept this broader definition of
"library-walk-in," though specific terms may vary. Under appropriate
licensing terms, it is valid to assert an affiliation of
"library-walk-in" for members of this broader class of users. The
affiliation "library-walk-in" is independent of any other affiliation
value. In other words, having the affiliation "library-walk-in" has
no effect, positive or negative, on any of the other defined affiliation
values. Similarly, no other affiliation value implies or precludes the
affiliation "library-walk-in." David’s agenda made the case
for documenting best practice around protocol use conventions. I think
our discussion of who’s responsible for implementing licensing policy,
what attributes are needed, and appropriate values for those attributes are all
part of a Community of Practice best practices documentation that is also needed. ....Kent _ |
- Vendor subgroup call, 1PM, David Kennedy, 08/07/2009
- Walk-ins, Kent Percival, 08/07/2009
Archive powered by MHonArc 2.6.16.