...
Attendees
- Charlotte Whitt
- Cheryl Malmborg
- Joanne Leary
- Maria Grzeschniok
- Mark Canney
- Wendy Wilcox
- William Weare
- David Bottorff
- Matthew Sullivan
- Michael Winkler
- Rameka Barnes
Goals
- Finalize missing details related to proxy relationships
- Review wire-frames related to loan actions
Discussion items
...
| Time | Item | Who | Notes |
|---|---|---|---|
| 5 min | Andrea | Housekeeping |
|
| 5 min? | Cate , Harry and/or Vince | Locations continued |
|
Notes
Housekeeping: No meetings on 6/22 & 26 (ALA) but will meet while Andrea is on vacation (enjoy!) with Cate as our convener.
Location discussion with Harry, Vince and Cate
- Number of levels:
- 5, not all need to be configured
- VZG libraries currently use 5
- Is having 5 levels a workaround from past systems or needed?
- Would it be better to have 5 right now instead of trying to add one later
- trying to prepare ourselves for the future and flexibilities
- locations have to be associated with a circ desk so you know when an item is “home”
- Need to keep home location when adding a temp location
- Level Descriptions:
- each institution will want to define and name their own levels
- so name conventions could be Level A,B,C or Level 1,2,3
- Consortia needs:
- Has not yet been discussed in Consortia SIG
- many libraries are in more than one consortia
- how can this be handled
- Is there a level above consortia?
- Sits apart from institution
- Collections:
- Is collections more of a concept?
- Location as a purpose?
- Workflow as context
- What would happen if “collection” were not part of location hierarch?
- What would that do to loan rules?
- Adding another factor in loan rules (5 instead of 4) would make it more difficult
Seems reasonable to have a level between library and shelving but what would that be?
Will pick up discussion on Monday’s meeting
| and Matt | Proxy | Follow-up questions (if any) | |
| 50 min | Cate and Matt | Loan actions |
|
Notes
We began a discussion about the wireframes Matt produced for working with (viewing and updating) patron loan records. In order to work with these records, a great deal of information is required. Ideally, the crucial information should be displayed on one screen, and secondary information should be displayable via clicking on elements to a secondary screen in a new tab. Screens include the Current transactions (items currently checked out by the patron), and Closed transactions (patron checkout history) and Item Transaction History (not patron-specific). Because some institutions retain patron information in circ transaction history, and some do not, this has to be configurable.
Features that we need on patron transaction screens:
- Required fields include: full-detail call number, full-detail location, title, author, barcode number, due date, loan status (such as renewed, recalled/requested); action pulldown; item selection check boxes
- Secondary fields include:
- click to full-detail bib/holdings/item info;
- click to full-detail patron transaction history, including notices sent;
- click to full-detail item transaction history (not specific to a patron);
- click to requestor information
Functionality:
- We need to be able to apply the actions to one, several or all items
- There should be a way to enter transaction-related comments to one / many / all selected items
- We need to be able to filter and sort on field column headers; sorting and filtering applies to entire list, not just the items that can be displayed on one screen
- We should be able to print/export list of items (all or selected)
We will continue discussing these wireframes at the upcoming meeting (Thursday June 15).