- Joanne Leary
|5min||User and request expiration||Cate Boerema||Both user and request records now can expire. User records expire when expiration date is today or in the past. Request records expire when request expiration date is in the past.||Determine which expiration formula is preferred?|
|15min||New "On order" status impact on request whitelist||Cate Boerema||- A new item (availability) status has been added called "On order"||Update the request whitelist to account for this status: https://docs.google.com/spreadsheets/d/1jaID-HGft3q4YzJq6Ycy2ejWByAIvou3Zyyw4ko87YI/edit#gid=0|
|35min||Remote storage requests||Cate Boerema||- Update SIG on the planned design for ASR requests and collect feedback/answer questions. See https://issues.folio.org/browse/UXPROD-1516 for write-up|
- Discuss Remote storage requests and what might be needed to support them.
-- Could the ASR request or Page request be leveraged for this purpose?
-- See https://issues.folio.org/browse/UXPROD-498 for Tania's feature writeup
|Planned Release (if known)|
|e.g. loans, fees/fines||Name||e.g. Q4 2018, Q1 2019||Clearly stated decision|
|Requests||User and request expiration|
|Requests||New "On order" status impact on request whitelist|
|Requests||Remote storage requests|
RA SIG 3-7-19
Cate led a discussion of several issues concerning details of expiration times for requests and users; allowable request types on newly ordered items; ASR requests; and standardizing location terminology.
Expiration time of day for Users, Requests, and items on hold
We agreed that the following time settings would apply to expiration dates:
- Requests: if unfilled, the request would expire at 11:59pm on the date of expiration (= end of day)
- Hold Shelf: if not picked up, the on-hold would expire at 11:59pm on the last day of hold (= end of day)
- User record: the expiration would become effective at 12:00am on the date of expiration (= start of day)
White List matrix of allowable actions for items on order, in process and [newly] available (see https://docs.google.com/spreadsheets/d/1jaID-HGft3q4YzJq6Ycy2ejWByAIvou3Zyyw4ko87YI/edit#gid=0):
- On order: can place hold request, but not recall or page request (DB noted that placing a hold should not require a barcode)
- In process: can place hold request, but not recall or page request
- Recently returned: cannot place hold or recall request, but can place a page request
ASR requests (automated storage retrieval):
- After some discussion, we agreed that it would be best to create a new request type for ASR items. The status sequence, controlled by FOLIO, would be “Available in ASR,” “Retrieving from ASR,” “In transit” or “Awaiting pickup.” When the item is returned, it would go to “In transit” or “Recently returned,” then “Available in ASR.” The only type of request that could be placed would be an ASR request.
- There needs to be a discussion with ASR point people about integration of FOLIO with their ASR systems. Andrea agreed to call a meeting with stakeholders. SMEs should send Andrea an email to let her know who in each institution should be part of this discussion.
In Inventory, the term used is “Effective location.” In Loans, the term used is “Location.” Did we have a preference? The group did not express a strong preference; the deciding factor might be labeling space. Cate will investigate.