2022-10-10 Resource Access Meeting Notes

Administrivia

Permission should allow for renewal of Aged to Lost items, but generates error message

• Request Record Identifiers:

  • Brooks in Chat: UUIDs is really the only viable one, in my mind, before we get to query support.

  • Andrea: Patron expiration date
  • Problem of hanging requests
  • hold shelf expiration date or request expiration date
  • Molly in Chat: 

    I wonder if request UUID could be added to the CSV export from the Requests app to support the gathering of the IDs using the filters available in the Requests app. Otherwise, gathering of UUIDs would either be manual or via API right?

  • Brooks: 

    I definitely think we need to add a story to add the request UUID to the CSV export from requests search/filter.

  • Cheryl in Chat: 

    Your query to create list to be edited will need to include hold shelf expiration date to be updated as well as other criteria like service point

  • use case for a update the whole expiration date for the user with a specific expiration date?
    • To renew the date for a specific group of patrons
  • For the Query Work on Bulk edit: UXPROD-3785
• Request preview columns:
  • the item Barcode is nessecary
  • is queue position important?

    • Erin W. in Chat: Queue position is not important for msu

    • Brooks: no
    • Question in Chat: 

      Can we add the date/time a request was placed?

The Resource Access SIG works with developers to define essential circulation functions: checking out and discharging library materials. Defines patron types, loan types, fines and fees structures, recalls, holds. Defines essential reporting functions. Advises developers on the interactions needed between libraries and other parties necessary for successful sharing of resources, whether through shared consortial collections, interlibrary loan options, or other mechanisms.

Ths RA SIG works closely with the UM SIG, with members being present in both SIGs

all circulation components:

• Circulation log, Remote storage, Material Requests Title Level Requests, Delivery and transfer services
• Fees and fines, Lost Items, Patron Blocks, Claims returned
• circ log
• Loans, Check-in, Check-out, Loan information on Item Details
• Patron notices, Printing slips
• Courses: MOD-CR, UI-CR
• APIs: NCIP: Protocol for service requests/fulfillment, Z39.50 Support MVP, SIP2
• On the Fly Records / Fast Add
• RTAC: provides item availability information to discovery

A: What do you feel like your SIGs purpose is currently?

B: Has it changed over time?

A: our purpose hasn't change (support development relating to our area) but can't fullfil it because of the lack of POs and dev ressources

B: more focused on libraries that are live - more problem solving than developement of new features

direct feedback to POs working on the backlog

we are doing the work we can rather than the work we should do

Orient new people joining the project to RA issues, provide training and question time for those institutions, share best practices and workarounds. 

It has changed over time as we have been developing fewer features and/or moving feature development into breakout groups (like was done with title level requesting.)

A: Do you have product owners who regularly work with the SIG?

B: Do you feel that your requirements are being successfully developed into FOLIO?

A: Yes

B: Sort of: No: 3-Part Item status, Workflow engine, Courses, German Reminder fees

Yes.

We have basic requirements and could function if we went live now, but there are major things we would really like to have, like a fix to the faculty delivery workflows, the ability to freeze a patron record, and the three part item status.

A: What are some of the challenges facing your SIG/subgroup?

B: Are there ways in which you feel the SIG has been unable to accomplish it's mission?

A: Missing POs

B:

A: What has been successful with the SIG?

B: What things contributed to that success?

A:

B:

Is that Google spreadsheet being actively reviewed or is the intention to do it yearly?

I don't really feel like it represents RA work well since most/all of our stuff is marked as "in the future."

A: How can we improve our communications with the SIG?

B: Does the current monthly reporting work?

C: Would have a dedicated PC meeting for your SIG be helpful?

A:

B:

C:

A: What functions should the PC be accomplishing?

B: And how would the SIGs like to have those need met?

A:

B: