2024-07-11 Resource Access Meeting Notes

5Min

Administrivia

@Cornelia Awenius @Jana Freytag 

• Calendar entries: Let Jana know if you want to be included in the Calendar invites

• You'll find the invites here as well: Resource Access (right menu under Meetings)

• All our WOLFCon submissions were accepted

  • 2 Working meetings; Calendar Workshop

  • Early bird registration end end of July: https://openlibraryfoundation.org/about/wolfcon/upcoming/

•  List of Integrations Survey

• PC-Update:

  • Introduction of new Members: Product Council

  • The role of Developer Advocate was introduced: will help developers in whatever ways developers can best be helped. Developer Advocate Vision, Guidelines, And Proposed Goals

  • Acquisitions prioritization pilot:

    • Based on the Implementers topics List: Acquisitions/Resource Management implementers

    • Votes on Jira tickets

    • Prioritizing Acq SIG Topics

Note Taker:

@Jana Freytag

20Min

WolfCon session planning: WOLFCon24 topics

Ideas for the Working Meeting:

• Take a look at our processes: Gap list vs. implementers list; best ways to get desired features completed.

• What about looking at old items in backlogs - bugs, tasks, etc., and deciding if they’re still valid issues
  Steph: Closer to the date, I can create a filter or dashboard for aged backlog tickets

• outcome should be a process on how to structure our backlog, implementers topics and tasks for the future

• another topic could be the prioritization process

Ideas for the RA general Meeting:

• Cornelia will present flowchart on aged-to-lost process and its interaction with claimed returned – go through flowchart, and solicit suggestions for improvement.

• Other suggestions welcomed over the next few weeks.

Calendar Session: Christine and Erin will give hands-on type session, demonstrating how to use calendars – "Calendar 101". Meeting will be recorded and uploaded to RA folder.

Reading Room Meeting: Can discuss ideas for this during the reading room working group meeting on the 8th.

20Min

Open discussion round

• Following up on the slack discussion: https://folio-project.slack.com/archives/C3G05TF3R/p1720704594004129

• Amelia in Chat: I remember seeing a page on the wiki somewhere describing which Item statuses can be set from each other status, I will see if I can find it

  • Circulation Interactions Allowed By Item Status

• UIREQ-581: Allow requests for items that have item status as RestrictedClosedPreview

• What is the restricted item status? We should have a dedicated meeting on the restricted item status.

• Mark in Chat: UXPROD-3860 says "A library implements Controlled Digital Lending and decides to use the built-in item status of Restricted to represent when the digital copy of the item is circulating. They change the behavior of the Restricted item status such that they are not able to circulate the physical copy while the digital copy is on loan."

• This ticket references a spreadsheet that describes the functionality associated with Item statuses https://folio-org.atlassian.net/browse/UXPROD-3469
  https://docs.google.com/spreadsheets/d/19_aA7bhRIxhcC6Gz-rK_LrfOtz8F5VaOmOcsFsdGU8I/edit?gid=745971866#gid=745971866

• Cornelia verified that in Nolana it was possible to put a Hold request on a restricted item status, whereas in Poppy and Quesnelia requests on restricted item status items are no longer possible.

• outcome: we will schedule a discussion on the restricted item status (who uses it for what?) is it still necessary?

Other possible topic for future discussion is whether In transit items should be delete-able in the Inventory UI.

Related: Lack of warning when checking out/in Order closed items (UXPROD-3863 and UXPROD-3864)