Versions Compared

Old Version 7

changes.mady.by.user Jana Freytag

Saved on

compared with

New Version Current

changes.mady.by.user Andy Horbal

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

...

TimeItemWhoDescriptionGoals/Info
2minAdministrivia

Jana Freytag


40MinTitle level requests

Kelly Drake

Continued Discussion and reveiew of final summary


___________________________________________________________________________

Presentation & Live-Demo by Marie Widigsonfrom Chalmers → Slides

Gathering requirements and accessing interest for title level requesting

Title Level Requests - Technical information


Timeline:  We would like to have requirements gathered by March 15, 2021

Name:  "Title level requests" vs. "Instance level " requests

  • The request is not actually on the title - different editions or formats of a title may be available but will not be included in the request queue that we are envisioning
  • "Instance' is folio-speak and non-native folio speakers may not understand what we mean


Slides:

Widget Connector
urlhttps://docs.google.com/presentation/d/1xAN3dLAaF6d13XglToECGHdSUkWlDfcat6tDYjIihSg/edit?usp=sharing




15Min

Check-out App

Feature discussion

(OLD ACCOUNT) Erin Nettifee

Check-Out App: Allow Custom Fields as Patron Identifiers for Check-Out

UXPROD-2936


Meeting Outcomes

Functional Area

Product Owner

Planned Release (if known)

Decision Reached

Reasoning

Link to supporting materials

Comments

e.g. loans, fees/finesNamee.g. Q4 2018, Q1 2019Clearly stated decision
  • Because...
  • Because...
e.g. mock-up, JIRA issue




























Notes

Title-level requests - Kelly Drake

Summary of discussion to date:

  • FOLIO Item level request functionality is very good, well appreciated and must continue
  • Title Level Requesting and is an absolute requirement for some FOLIO libraries and would be a welcome additional option for others.
  • Item level requests will need to placed even when there are multiple items

Additional info is included on Kelly’s slides.

Multi-volume sets, or periodicals with more than one item per issue = out of scope (still need to determine how to identify). These will still be handled as item-level requests. Additional permissions also = out of scope, and current (and in development) circ rules will be able to handle this.

Discussion of what identifiers institutions using title-level requesting employ now, including what EDS systems do.

Consensus that this is a hard technical problem to solve!

API changes/additions will include information regarding a patron’s place in the instance/title queue, and maybe item vs title request.

Need a new setting to enable title-level requests.

Timeline + next steps are included on Kelly’s slides.


Check-out app - Erin Nettifee

Erin here to get input on UXPROD-2936, which Duke is going to pay to develop. Four configurable (in SettingsàCirculationàGeneral) identifiers that you can use when checking an item out to a patron: barcode, external system ID, FOLIO record number, and username. UM SIG has been batting around idea of adding additional identifiers to record for awhile. Cons: it’s already pretty “busy” and includes a lot of fields. Answer = use custom fields! Proposal is to make changes to FOLIO to allow this. Biggest change that people will see in UI is in Settings, where a fifth option for “Custom Fields” with a drop-down menu would now appear. If your library doesn’t want to use this feature, you can just leave the box unchecked, meaning it shouldn’t impact you at all. Should be no impact on performance of system.

Consensus that this sounds fine to everyone!