2017-10-19 Resource Access Meeting Notes
Date
Oct 19, 2017
Attendees
@Andrea Loigman
@Mark Canney
@Deb Lamb
@Cheryl Malmborg
@Tania Hewes
@Cate Boerema (Deactivated)
@Sharon Wiles-Young
@David Larsen
@David Bottorff
@Joanne Leary
@Kimie Kester
@Maria Grzeschniok
@Rameka Barnes
@Peter Murray
@Charlotte Whitt
@William Weare
@Marc Keepper
@Darcy Branchini
Discussion items
Time | Item | Who | Notes |
|---|---|---|---|
5min | Housekeeping | @Andrea Loigman |
|
| Location model review | @Cate Boerema (Deactivated) | Location UX/UI model-
ACTION ITEM: GIVE CATE SOME LOCATION: SHELVING locations
|
| Requests | @Tania Hewes | Starting with holds and recalls as examples - tabled 'til next meeting |
Notes
I've attached some lists of our locations and screen shots of the UI's for adding locations and assigning a location to an item.
There are 5 possible levels (uc_loc_levels) of which we use 3. The design is hierarchical. Each level below the institution has to have a parent level.
For example, Regenstein Library's (JRL) is a Library level location; its parent is the Institution level location UC. JRL is the parent level for many locations at the Shelving level. The location assigned to a particular item or holdings record explicitly has all the levels. The item in the example, uc_stored_loc has the location UC/JRL/Gen. The item or holdings record for each item also stores the levels used to define the location in the location_level column. In this case, the levels are Institution/Library/Shelving.