Date
...
@Patty Kishman
Discussion Items
| Time | Item | Who | Description | Goals/Info |
|---|---|---|---|---|
| 2min | Administrivia |
| ||
| 45Min | Title level requests | live Presentation & Live-Demo by Marie Widigsonfrom Chalmers → Slides Gathering requirements and accessing interest for title level requesting Title Level Requests - Technical information
Name: "Title level requests" vs. "Instance level " requests
|
Meeting Outcomes
Functional Area | Product Owner | Planned Release (if known) | Decision Reached | Reasoning | Link to supporting materials | Comments |
|---|---|---|---|---|---|---|
| e.g. loans, fees/fines | Name | e.g. Q4 2018, Q1 2019 | Clearly stated decision |
| e.g. mock-up, JIRA issue | |
Notes
David Bottorff, note-taker
...
In-app reports document -
we've gone through almost all of them other than 3 inventory reports (instance UUIDs via csv file, two others nonfunctional exports to MARC or JSON)
circulation log results export to CSV but not developed yet (Iris)
will need to revisit this at some point
feature requests being shared with POs
...
Documentation working group
need to collate glossary work from across SIGs, apps, etc.
contribute back to project a translation from Voyager, Sierra, Aleph and other systems to FOLIO
Erin will share around glossary for feedback, likely one of the first priorities to complete
Jira project so that documentation is part of the development project
this group needs to work on the Circulation Needs document - next step is how do we track this work and ensure it's documented, do people have ideas?
Cornell everyone on training group is doing 4 hours a week on FOLIO
Thursday meetings - time to review documents, or collective time to write documentation
Marc-breaking up into smaller working groups to write and review
Google technical writers style guide is what's being followed
but don't get nervous, as the working group can edit to follow the style guide
need for a roadmap for how to get through this in the next 4-6 months-Erin will work on this, play around with models
right now, if you want to pick up documentation, edit the Circulation documentation needs page and put your name next to it and we'll formalize this later
documentation intro to what's in the wiki, what's in Slack, what's in Jira, etc. onboarding is definitely lacking. Welcome to FOLIO; maybe a recording of welcome community member forum and a Q&A
roadmap-think about tasks that folks who don't have as much experience or time for documentation can help with
...
met for the first time Wednesday
...
met with Marsha Bornstein (consultant) and convener from Blackwater
...
a lot needs to be written, planning for that (most being tracked in draft in Google Drive OLF)
...
@Marie Widigson, provided a demonstration of requests at Chalmers with a discussion about title level requests. Title level requests are on the instance level. First person in the queue gets the first book returned. The patron places a request through discovery (EDS). If an item is available on the self the request is a Page. If the item is not on the shelf the request is a Recall. TRL logic from mod-circulation interprets the business logic. Non-requestable item and loan types are omitted. The item with the shortest queue gets the request. If equal queue length, the item with the soonest due date is used.
Chalmers' slides, screenshots and notes are available: https://docs.google.com/presentation/d/1l1rf_wkAD8b1utoIW4A9vvGmSEdRsTh5YTARR6B2I2E/edit?usp=sharing
Problems with using TRL logic?
- Another item not covered by TRL logic may be returned. Items may get returned earlier than due date; queue gets out of order.
- Students make multiple requests; other patrons have to wait longer.
Current necessary workarounds:
Script to move found items to available items
Manually move patrons to more fair place queue
Dummy patron to block item queue. Mainly when we reorder additional copies
Where should the setting for item versus title level request live?
item, holdings, instance?
circulation rules? For example, patron type "student" requesting loan type "textbook": apply title level request.
How are remote storage/asrs libraries planning to handle requests to items in those locations?
Requests now in folio entirely dependent upon itemids.