Date
Attendees
Discussion tems
Time | Item | Who | Description | Goals |
---|---|---|---|---|
5min | Housekeeping |
| Update on Off site storage development work and it is happening, Cate is handling this | |
30min | Call numbers | Display inconsistencies (con't from 3/28) | --clear explanation of enumeration, chronology, volume, and year, caption (from Charlotte Whitt) - slide deck: https://docs.google.com/presentation/d/1Z3Ce8BiesdXriZwpcs0hRaIYBUKtEL9G28ItBXPH5eI/edit#slide=id.p Enumeration - v. no.1 descriptive of serial item, Chronology; year, season, month can be expressed as a number as well Enum/Chronolgy- and can have only chronology Map inventory holdings to export holdings to other systems Monographs multi-part item can have year or volume information or both to describe item Implemented enumeration and chronology and Q2 to display concatenate both enumeration and chronology Item record: call number, volume, enumeration and copy Questions: Requests do we display item level data yes from the item record-Call number storage in holdings record - when temporary call number (reserve); do we have temporary location and permanent location for both item and holdings --can temporary and permanent call numbers be edited on both the item and holdings level Call number subgroup : need volunteers to work with Charlotte and Emma Continued: call number fields (from Charlotte Whitt) - slide deck: https://docs.google.com/presentation/d/152x27epGqEWxSUKSew8pK0lkWxB9ueNtZqFdMJqpARM/edit#slide=id.p | |
25min | Recently returned | Emma Boettcher | Trigger actions | decisions on what triggers the flip from recently returned to available & how that is scheduled Recently returned: switch from recently returned and then shelving lag time then change to available; when does timer start for recently return item at first scan or second scan; concern will the system have to scan for recently returned all day or should it be an overnight batch job- similar functionality for hold shelf expiration Cate will find out about this functionality–concerns about system performance if in "real time" |
Meeting Outcomes
Functional Area | Product Owner | Planned Release (if known) | Decision Reached | Comments |
---|---|---|---|---|
e.g. loans, fees/fines | Name | e.g. Q4 2018, Q1 2019 | Clearly stated decision | |