2024-01-11 Product Council Meeting Agenda and Notes

Owned by Alexis Manheim
Last updated: Jan 11, 2024 by Tim Auger
8 min read

Date

Attendees

Discussion items

TimeItemWhoNotesDecisions and Actions
5 minAnnouncementsall

WOLFCon FOLIO volunteer needed to represent the project on the overall planning group – first meeting at the end of January

  • No one volunteered in the meeting
  • Everyone is welcome to raise interest

20 minPresentation on mod-batch-print functionality
Charlotte Whitt 

For evaluation of new functionality prior to Tech Council review:
TCR-33: mod-batch-print is an Okapi service that can generate pdf files as a nightly job and store them. The files will be accessible from a dedicated settings page.

Link to slide deck

starting min. :07

  • backend module only - it is not a new app
  • very simple and lean and dedicated backend module to generate pdf print jobs on a nightly basis
  • module is optional
  • basic UI permissions needed
  • the TC review is to come after the presentation in PC
  • Jenn Colt and Tod Olson will do the review
  • development is done by Index Data in a project with hebis (German library network)
  • hebis and Index Data work on German reminder fees
  • Team = Odin
  • Worked on reminder fees since April 2023
  • 2 features for Quesnelia (to be released in April) - in JIRA
  • Printed letters to patrons with the final notification about reminder fees are a legal requirement for e.g. Hebis network
  • file is printed out as a nightly job - sent as a regular letter
  • Charlotte demoes the new development min :14 - demo in development environment
  • Settings - Circulation - Patron notices - Patron notice print jobs
    • created print jobs can be deleted with the relevant permissions
  • mod-batch print is an Okapi service that generates pdf files as a nightly job and stores them in a database
  • pdf files are accessible from settings page: settings > circulation > patron notice print jobs
  • settings can be ignored if not needed
  • built into the regular flow for patron notifications
  • not interfering with mod-email 
  • it is a separate module because it is not needed by all institutions (not all institutions need to send printed letters)
  • TCR-33 is already submitted
  • asking for approval by PC 
  • next step: review by TC
  • Marc Johnson comments in chat: There is no way to define optional extensions to flower releases in the current way we define the contents of a flower release
  • Charlotte: the intention is to have the pick & choose option - as it is not relevant for all libraries - it does not interfere and all extra permissions can be submitted
  • Owen in chat: What does “optional” mean in this context then?
    My guess is that it means “you don’t have to use it if you don’t want to”, rather than “you don’t have to install the module”?
  • Charlotte agrees
  • Harry: APIs seem reasonable to me
    • output files are typically managed in the apps
    • why is it different here?
  • Charlotte demoes again :28: all reminder fee policies are defined in circulation settings - that is the place users are working when involved 
  • deletion happens in settings as well
  • at the moment it is set up only for reminder fees
  • where the information is displayed has nothing to do with the backend module
    • raised during discussion: display in export manager
  • there is more interest and raised hands - due to time constraints we need to postpone further discussions
  • we can continue discussion in Slack before we have a vote
  • if needed we can come back to this topic in 2 weeks

(warning) No decision made

Continue discussion and voting either via Slack or in 2 weeks

20 minPresentation on new Direct Consortia Borrowing/DCB Integration 

 Steve Ellis Tim Auger 

For evaluation of functionality in three new modules prior to Tech Council review:
TCR-35, TCR-36, and TCR-37

Tim presents on DCB starting :40

  • What is OpenRS?
  • it is a portfolio of resource sharing products
    • direct consortial borrowing
    • document delivery
    • mediated supply (ILL)
  • it is an open source OLF project
  • it is a coalition of consortia dedicated to develeiopment of open-source resource sharing software
  • MOBIUS is the consortium that is contract partner together with K-Int
  • Highlights of the system
    • platform agnostic Resource Sharing system
      • harvesting APIs
      • Patron requests via DCB hub
      • tenant to tenant communication always goes through DCB
    • seamless integration with circulation
      • 3 primary roles: lensing, borrowing, pickup (if there are multiple locations or lending libraries involved)
      • all platforms support all 3 roles
  • FOLIO Enhanced Consortia Support (ECS)
    • tenant to tenant communication via DCB to process information
    • only necessary personally identifiable information is shared
    • all fees, fines, patron notifications etc. managed by borrowing library - using circulation config and convention
    • Temporary bib, items and patrons

Questions will be collected in Slack

Further Q&A is postponed to Slack or next PC meeting

5 minFuture topicsall

Chat

15:59:59 Von Alexis Manheim an Alle:
    yes
16:00:11 Von Alexis Manheim an Alle:
    I avoided traffic
16:02:08 Von Jennifer Eustis an Alle:
    Happy New Year
16:02:24 Von Kristin Martin an Alle:
    https://folio-org.atlassian.net/wiki/display/PC/2024-01-11+Product+Council+Meeting+Agenda+and+Notes
16:03:39 Von Kristin Martin an Alle:
    https://folio-org.atlassian.net/wiki/display/PC/2024-01-11+Product+Council+Meeting+Agenda+and+Notes
16:21:56 Von Marc Johnson an Alle:
    There is no way to define optional extensions to flower releases in the current way we define the contents of a flower release
16:25:42 Von Owen Stephens an Alle:
    What does “optional” mean in this context then?
16:26:17 Von Owen Stephens an Alle:
    My guess is that it means “you don’t have to use it if you don’t want to”, rather than “you don’t have to install the module”?
16:27:21 Von Tim Auger an Alle:
    My apologies for being late…I had the wrong time in my calendar.
16:27:31 Von Tim Auger an Alle:
    Quick comfort break…brb
16:28:06 Von Marc Johnson an Alle:
    I took Charlotte’s use to refer to the technical mechanism 
    
    My point is that if this approved then the module will be included in the flower releases by default and system operators will need to remove it
16:29:40 Von Tim Auger an Alle:
    back
16:31:06 Von Jana Freytag | VZG an Alle:
    This makes sense from a librarian standpoint, I'd say. Since this Kind of Output has no specific app.
16:31:14 Von FOLIO Team an Alle:
    I also took that meaning; I presume that it's optional in that it's designed to not be a dependency for anything else.  This makes it nicely future-compatible with our intent to have a more streamlined 'core' release and separated Apps
16:31:45 Von Jennifer Eustis an Alle:
    In our consortia, we shy away from giving people permissions to settings.
16:32:03 Von Martina Schildt | VZG an Alle:
    Reacted to "This makes sense fro..." with 💯
16:32:10 Von Kirstin Kemner-Heek an Alle:
    Replying to "I also took that mea..."
    
    +1
16:32:17 Von Jenn Colt an Alle:
    I could see where this might have landed in export manager.
16:32:27 Von Jennifer Eustis an Alle:
    Reacted to "I could see where th..." with 👍🏻
16:32:54 Von Jennifer Eustis an Alle:
    Replying to "I could see where th..."
    
    Isn't this where other circ reports are?
16:33:30 Von Marc Johnson an Alle:
    Replying to "I also took that mea…"
    Possibly. A highly generalised module that contains highly specific behaviour doesn’t necessarily fit into the app decomposition model 
    
    As the highly general part belongs in the fundamentals and the specific better fits with the app responsible for the specific use case and that separation isn’t possible if the code for both is in the same module
16:33:44 Von Jenn Colt an Alle:
    Replying to "I could see where th..."
    
    Users seems to have circ and export manager has money stuff
16:34:38 Von Brooks Travis an Alle:
    I also like the export manager idea
16:37:01 Von Owen Stephens an Alle:
    What’s the next step for this discussion - do we have a PC vote to approve module?
16:37:29 Von Tim Auger an Alle:
    If we are in the flow of this topic, I can return next week.
16:37:42 Von Tim Auger an Alle:
    ?
16:38:07 Von Martina Schildt | VZG an Alle:
    Having this in settings makes sense to me. In our network many libraries give system users (not only admins) permissions for settings - so it would fit into our workflows for us.
16:38:19 Von Jana Freytag | VZG an Alle:
    Reacted to "Having this in setti..." with 💯
16:38:19 Von Tod Olson an Alle:
    Replying to "If we are in the flo..."
    
    Next week is the Tri-council meeting, would have to be in two weeks.
16:38:24 Von Martina Tumulla an Alle:
    Reacted to "Having this in setti..." with 💯
16:38:27 Von Kirstin Kemner-Heek an Alle:
    Reacted to "Having this in setti..." with 💯
16:38:43 Von Niels Erik an Alle:
    Reacted to "Having this in set..." with 💯
16:38:44 Von Niels Erik an Alle:
    Removed a 💯 from "Having this in set..."
16:38:50 Von Tim Auger an Alle:
    🙂
16:40:52 Von Kirstin Kemner-Heek an Alle:
    I would like to add, that I like this module very much. It will be used in GBV and I see a lot of other usage options for other modules as well, e.g. in acquisition one day.
16:43:37 Von Martina Tumulla an Alle:
    Thank you Charlotte - we need this print option as well
16:46:04 Von Jana Freytag | VZG an Alle:
    Reacted to "I would like to add,..." with 💯
16:49:54 Von Charlotte Whitt an Alle:
    Reacted to "Thank you Charlotte ..." with 🌸
16:49:59 Von Charlotte Whitt an Alle:
    Reacted to "I would like to add,..." with 🌸
16:51:55 Von Martina Schildt | VZG an Alle:
    Reacted to "I would like to add,..." with 💯
16:54:08 Von Harry an Alle:
    Reacted to "I could see where th..." with 👍🏻
16:54:59 Von Niels Erik an Alle:
    I would like to add that the discussion about where or how to display the generated print jobs in the UI are largely irrelevant to the assessment of the relevance of and utility of the new back-end module. I noticed that several domain experts said it's currently displayed in a place that feels natural for the workflow but it could be put somewhere else UI wise. The main question under consideration, though, is whether the module is needed and useful.
16:55:45 Von Charlotte Whitt an Alle:
    Reacted to "I would like to add ..." with 🌸
16:56:50 Von Kirstin Kemner-Heek an Alle:
    Reacted to "I would like to add ..." with 👍
16:56:56 Von Jana Freytag | VZG an Alle:
    Reacted to "I would like to add ..." with 👍
16:59:25 Von Jennifer Eustis an Alle:
    Reacted to "I would like to add ..." with 🌸
16:59:43 Von Tod Olson an Alle:
    Is the use of temporary bibs and items consistent with how NCIP uses them?
17:00:38 Von Brooks Travis an Alle:
    Replying to "I would like to add ..."
    
    Not sure I agree. It’s PCs job to consider how this functionality fits with the overall “product” of FOLIO
17:00:51 Von Brooks Travis an Alle:
    Replying to "I would like to add ..."
    
    The UI/UX is a big part of that
17:01:24 Von Martina Tumulla an Alle:
    Reacted to "I would like to add ..." with 👍
17:02:17 Von Florian Ruckelshausen an Alle:
    Reacted to "I would like to add ..." with 👍
17:03:02 Von Alexis Manheim an Alle:
    Nope
17:03:10 Von Martina Schildt | VZG an Alle:
    Reacted to "I would like to add ..." with 👍

Action items

  •