2019-11-15 Resource Management Meeting Notes

Announcements/Updates

• Product Council Notes
• House-keeping: No meeting Nov. 29

• You can view the slides to get details about the LDP.

WOLFCon ideas;

RM SIG spreadsheet

MM SIG Spreadsheet

Joint RM/RA/MM SIG meeting around "item states"

Some parameters:

• We could have the potential of a pre-conference, depending on space availability at Texas A&M and who is there on Tuesday
• There are 2.5 days we can fill, but there will be some plenary sessions, not sure how long they will be
• There are six concurrent rooms for FOLIO sessions
• We can request Zoom for remote access

Registration is now open. There is also a Slack channel for answering WOLFCon questions (#folio-wolfcon2020).

Suggested topics:

• A long session (several hours) to walk through workflows.
• It is also suggested that the SIGs have whiteboards where we can note places where apps interact so that stakeholders can discuss in more detail at the end of the conference.
• It is suggested that we have a session on the UI/UX experience now that people have begun spending more time with the system.
• A discussion of the functional scope of the OA Expenditures (APC) app.
• A cross-app session examining the Inventory app
• A session on consortial use
• A discussion on what people are doing/planning to do to migrate
• The interaction between ERM and Acquisitions apps (possibly a pre-conference topic) - this may be combined with the workflows.
• Cornell plans to have ERM implemented and will discuss their experience

Acquisition/access status type = a way to support necessary changes to holdings; informed decisions; streamlined management of current state of holdings (e.g. "subscribed", purchased with perpetual access; trial; post cancellation access). They are created in the settings and selected under package settings. Users will be able to filter package results by access type. It will not be a required field.

How are people currently tracking access status? What are the key workflows to consider? Chicago has an Access database where they track it and mainly use it for reporting. TAMU and UMASS use an acquisition type in CORAL - it does affect some workflows.

What are the expectations for this to interact with other apps? It would be good to track DDA holdings between apps. Open access also.

Should there be a set list or should users be able to create custom ones? It was suggested that there be an initial list with the ability to add new ones. If functionality is being driven by the type, having custom values makes things much more complicated. For the Agreements app, Owen has been cautious about having custom values for this reason. Why not use tags? Chalmers is currently using tags for access types but it's not the optimal solution.