2019-4-25 Resource Access Meeting Notes
- Andrea Loigman
- Joanne Leary
Date
Attendees
Discussion tems
| Time | Item | Who | Description | Goals |
|---|---|---|---|---|
| 5min | Housekeeping |
| Who is planning on attending?? | |
| 30min | Patron notices | Understand what reports for patron notices are needed and where they should be accessed from | ||
| Needs for loan, patron and notice history |
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 | |
Notes
FOLIO Conference, June 17 – 19, 2019 in Crystal City, VA – although there will be no full meetings for Resource Access, SIG members are encouraged to attend to provide input, especially with Metadata Management. ZOOM will be available. Register to attend through the FOLIO registration form in order to take advantage of rooms/conference discount at Hotel (no need to register if only attending by ZOOM). Let Andrea know if you will be attending (in person or by ZOOM). Jana will be there; David B can do ZOOM.
In-app reports needed: the name is misleading, but essentially these are reports that are needed for regular use, and use real-time data, as opposed to warehouse data (data about a day old). Developers are hard-coding the in-app reports first, and tabling development of the interface for ad-hoc (roll-your-own) reports from the data warehouse for later. Sharon Beltaine said we need to prioritize what we need without thinking of them as in-app or ad-hoc. Disregard the source, focus on the function.
Reports for patron notices – Darcy
- We need pull list reports (reports for paging from stacks for various purposes – filling a request, processing for course reserve, other)
- We need error reports for notices (notices that failed to be sent out)
- Related to this: we need to see notice data (type of notice, when sent out) included in overall Loan transaction history, integrated into the chronological sequence of actions related to that loan (e.g., check out date, reminder notice #1 date, renewal date, recall date, recall notice date, etc.). The complete history should be preserved even after the borrower information is scrubbed. Q: should this information be attached to the Item record? Circulation PO’s need to talk about this.
- We agreed that we need a holistic way to view information related to circulation operations, in a way that is not siloed into disparate apps. We use data from a lot of sources, and the concept of in-app reports (at least what is implied by the name) is problematic, since circulation is by its nature “cross-app.”
For next meeting: look at Cate’s whitelist; look at ILLiad’s way to display notice history (screenshots to be provided in advance).
