11/5/2008 Updated 1/12/2009 Zack Lane ReCAP Coordinator

Slides:



Advertisements
Similar presentations
Zack Lane ReCAP Coordinator July 2013 ReCAP Columbia University.
Advertisements

Zack Lane ReCAP Coordinator July 19, 2012 ReCAP Columbia University.
Business Library and ReCAP: Update and Statistics
Zack Lane ReCAP Coordinator July 2013 ReCAP Columbia University.
Zack Lane ReCAP Coordinator July 2013 ReCAP Columbia University.
ReCAP Request Mechanisms 9/15/2008 revised 1/12/2009, 11/4/2010 Zack Lane ReCAP Coordinator.
Zack Lane ReCAP Coordinator August 30, 2011 ReCAP Columbia University.
Zack Lane ReCAP Coordinator July 2013 ReCAP Columbia University.
Zack Lane ReCAP Coordinator July 2013 ReCAP Columbia University.
Barcode Tracking At ReCAP ReCAP LAS CUL “Big File” + - Pending Directory SubmitTracking Database Request Directory + Columbia University 2/6/09 Zack Lane.
Zack Lane ReCAP Coordinator September 2012 ReCAP Columbia University.
Impact Theories: Trends in Off-site Shelving Facility Use Zack Lane, ReCAP Coordinator, Columbia University Libraries | Colleen Major, Networked E-Resources.
Zack Lane ReCAP Coordinator July 2013 ReCAP Columbia University.
Zack Lane ReCAP Coordinator July 2012 ReCAP Columbia University.
ReCAP Summary: East Asian Library Zack Lane ReCAP Coordinator 7/12/2010.
Zack Lane ReCAP Coordinator July 2012 ReCAP Columbia University.
Zack Lane ReCAP Coordinator ReCAP Columbia University.
Zack Lane ReCAP Coordinator July 2013 ReCAP Columbia University.
Zack Lane ReCAP Coordinator August 10, 2012 ReCAP Columbia University.
Zack Lane ReCAP Coordinator July 2012 ReCAP Columbia University.
Outline of ReCAP Accession Zack Lane Recap Coordinator 9/12/08 rev. 12/6/2010.
Zack Lane ReCAP Coordinator February 2012 ReCAP Columbia University.
Zack Lane ReCAP Coordinator July 2013 ReCAP Columbia University.
Zack Lane ReCAP Coordinator August 5, 2011 ReCAP Columbia University.
Zack Lane ReCAP Coordinator May 2011 ReCAP Columbia University.
Zack Lane ReCAP Coordinator July 2013 ReCAP Columbia University.
Zack Lane ReCAP Coordinator July 2012 ReCAP Columbia University.
Zack Lane ReCAP Coordinator September, 2012 ReCAP Columbia University.
Zack Lane ReCAP Coordinator April 2011 ReCAP Columbia University.
Zack Lane ReCAP Coordinator July 31, 2012 ReCAP Columbia University.
ReCAP Topics: Access and Request Columbia University Libraries 10/27/2009 Zack Lane ReCAP Coordinator.
Requesting in the Catalogue : from carbon paper to online service Lynne Billington Systems Librarian State Library of New South Wales.
Columbia University and ReCAP July 24, 2008 Zack Lane ReCAP Coordinator (212)
RBML and ReCAP: Summary of Progress Zack Lane ReCAP Coordinator 4/12/2010.
Impact Theories: Trends in Off-site Shelving Facility Use Zack Lane and Colleen Major Columbia University 12/5/2008.
Zack Lane ReCAP Coordinator August 13, 2012 ReCAP Columbia University.
Zack Lane ReCAP Coordinator July 2013 ReCAP Columbia University.
ReCAP Shelving Facility Research Collections and Preservation Consortium.
Zack Lane ReCAP Coordinator August 5, 2011 ReCAP Columbia University.
ReCAP Update: Tech Services Librarians Zack Lane ReCAP Coordinator Columbia University 4/29/2010.
Zack Lane ReCAP Coordinator July 2012 ReCAP Columbia University.
Zack Lane ReCAP Coordinator April 5, 2011 ReCAP Columbia University.
Zack Lane ReCAP Coordinator July 2013 ReCAP Columbia University.
Clio Interlending Management System FIL Interlend 2006 University of Southampton 11 July 2006 Larry Perkins, Clio Software Dorothy Perkins, Clio Software.
Zack Lane ReCAP Coordinator February 16, 2011 ReCAP Columbia University.
Zack Lane ReCAP Coordinator September 16, 2013 ReCAP Columbia University.
Business Library and ReCAP: Update and Statistics
11/5/2008 Updated 1/12/2009 Zack Lane ReCAP Coordinator
7/18/2008 Updated 1/16/09 Zack Lane ReCAP Coordinator
Zack Lane ReCAP Coordinator February 2012
Circulation Data: East Asian Library
Current ReCAP Projects: A Review
ASCC: Answers to ReCAP-related Questions
Columbia University 1/8/09 Zack Lane ReCAP Coordinator
ReCAP Data Part 4: EDD (Electronic Document Delivery)
Zack Lane ReCAP Coordinator June 21, 2010 rev. May 2, 2011
ReCAP Collections Analysis: Music Library
Circulation Data: Health Sciences Library FY13
Social Work Library and ReCAP: FY13 Update and Statistics
Circulation Data: The Burke Library
ReCAP Data Part 2: Requests
Butler Media Center: ReCAP Statistics
ReCAP Data Part 5: Request Rate
ReCAP Shelving Facility
ReCAP Collections Analysis: East Asian Library
The Off-site Request Button: How it works and when it appears
The Off-site Request Button: How it works and when it appears
ReCAP Data Part 2: Requests
Geology Library and ReCAP: FY13 Update and Statistics
ReCAP Data Part 6: High-Use Titles
Presentation transcript:

11/5/2008 Updated 1/12/2009 Zack Lane ReCAP Coordinator Access Permissions 11/5/2008 Updated 1/12/2009 Zack Lane ReCAP Coordinator

Factors Controlling Access There are two main factors controlling access to ReCAP materials User permissions: Who is placing the request? Item Permissions: What restrictions does the object have?

User Permissions Who is placing the request? 1) Patrons: place requests in CLIO. Patrons may also have mediated requests placed by staff. 2) Staff: have several methods of placing requests. Access to the ReCAP Request Forms is controlled by UNI.

User Permissions cont. Patron access to online requests requires an active UNI UNI authentication is maintained by CUIT Any active UNI is sufficient to place requests, including printing UNIs Alumni may need to re-activate UNI Non-affiliates must contact the Library Information Office at lio@columbia.edu or (212) 854-7309

User Permissions cont. Staff place requests through one of several modes Access to staff request forms requires active employment and an active UNI Circulation staff will primarily place Mediated Requests on behalf of patrons Staff may place requests via CLIO for personal use See ReCAP Request Mechanisms for more information

What restrictions does the object have? Item Permissions What restrictions does the object have? All items at ReCAP must have two identifying pieces of information: 1) barcode and 2) customer code Most items at ReCAP have an assigned CLIO location; all records in CLIO must have an assigned location CUL controls request permission using CLIO location; ReCAP controls delivery location using customer code Managing collections at ReCAP requires coordination between two institutions, two databases

Item Permissions cont. The two databases are referred to in shorthand as Voyager (CUL) and GFA (ReCAP) Voyager and GFA contain different, but related, sets of data Voyager is an ILS, designed for library collection management GFA is a proprietary system designed for high-density library storage facilities Voyager and GFA do not “talk” directly to each other CUL staff periodically retrieve files from GFA

Item Permissions cont. Columbia University Libraries as an entity is divided into department libraries. Each department library may be divided into several different collections. Collections have one or more CLIO locations. Local access permissions are associated with collection/CLIO location Columbia University Libraries Avery Library Burke Library LC Stacks “uts” Ware Coll. “war” “war,ref” Van Ess Coll. “uts,essxx1” “uts,essxx2”

Item Permissions cont. See CPM-500 for a complete list of CLIO location codes; 484 total

Item Permissions cont. CLIO locations have an associated circulation status (Item Type). Loan period is determined by several factors. Loan period is a combination of owning library, patron group and tk.

Access Permissions CUL controls request permission using CLIO location ReCAP controls delivery location using customer code

Item Permissions cont. Customer code is the key element to understanding item permissions Customer code determine access permission and delivery location for collections at ReCAP Customer codes are loosely synchronized with both CLIO locations and barcode prefix

Customer codes represent one of three things: Item Permissions cont. Customer codes represent one of three things: Delivery Location Collection Delivery Location and Collection

Item Permissions cont. Requests are authenticated at ReCAP by comparing the requested delivery location to the customer code table If the requested delivery location is not permitted, the request is sent back as a failure This is the cause of most failed requests Staff are not aware of the delivery restrictions in the customer code table