2024-01-30 Acquisitions Meeting notes: Serial Binding and Claiming UAT results

Housekeeping 

Dung-Lan

• Housekeeping

  • Next scheduled meeting, Friday, Feb. 2nd, at 9 am Eastern

  • In the process of planning a demo/Q&A with Bjorn Muschall re: custom fields functionality and how it's implemented (related to Implementers' Topics #113)

  • FYI - Oleksii Petrenko Poppy R2 2023 Release Digest is available - Poppy (R2 2023)#FOLIO-PoppyR22023Releasedigest 

 :06

 Serial Binding

 Joe

 Review forthcoming approach to serial binding (@Joseph Reimers )

• Binding will start in the receiving app. 

• Select a title, click the pieces you want to bind, then click form to bind. 

• If you need to rebind, or bind a single piece, you will be able to manually set the status that it is at binding. 

• Open

  

• That will bring up an additional screen where you will select what issues need to be bound. 

• Open

  

• Adding a ''bound' check box. 

• Open

  

• Once you have selected the pieces to be bound, a bound item will appear. 

• Will be adding a 'bindery active' toggle to the purchase order line which will allow you to keep track of materials to be bound. Boundary active will do some pre-configuration that ensures all inventory interactions work correctly. By default will have to have independent ordering and receiving quantities because we need to associate that. 

• Kristin Martin asked for clarification on how the item is created when you click the 4 you want to bind. 

  • When you click the 4 pieces you want to bind, you are saying to merge into one. You will have one item record that will link to those four pieces. The pieces remain independent in the receiving history, but the receiving history at the bottom 

• Molly Driscoll 12:18 PM
  If the original items are deleted, is there a dependency check to look for open loans, requests, and fees/fiens prior to deletion?

  • That is not built in yet and is one of the reasons I wanted to talk about this. We will need to do the normal due diligence. The item will be decoupled from the receiving history and this was a good catch by Molly. 

• If no other questions Joe will keep working on this. 

• Right now, we are hoping to have this in the Ramsons version. 

• Molly Driscoll 12:23 PM
  Is this the correct Jira to "watch"? UXPROD-4093: Support for physical materials to be boundClosedPreview

  • Yes - that is the feature. 

:24

Summary of claiming

Dennis

• Summary of findings and feedback from recent UAT around claiming. 

  • Testers: 15

  • Unique Institutions: 8

  • Time to complete - ~ 1 hour

    • Susanne Gill (BVB) 12:27 PM
      I didn't need an hour. It was like 5-10 Minutes

    •  

      Dung-Lan Chen 12:28 PM
      It didn't take long time for me … went back to it the second day … total less than an hour.

• Positive feedback 

  • Claiming functionality added made the serials claims workflow more effective. 

  • Export worked well. 

  • I was able to create an order line with claiming active right away. 

• No showstoppers defects identified. 

  • The users that participated were able to complete the test. Nothing critical was identified that would give reason not to release this functionality with Quesnelia. 

• Bugs Identified: 

  • Could not use 'un receivable'  with my created user (permission issue)

  • Unable to edit certain fields in piece record (working to reproduce. Need more prominent alert for required fields that are not filled or have validation errors. Cursor should move to that box after save attempt. 

• Suggested enhancements: 

  • Changing expected receipt date should impact the status of the piece, ie, from late to expected the other way. 

    • Will add a story to manage this logic.

  • Export only the pieces matching the search criteria rather than all the pieces for the returned title. 

    • Would be nice, but right now filter for receipt status, late. 

  • Being able to filter by ISSN would help when managing materials in Cyrillic alphabet and other challenging languages. 

  • Adding an automated send claim function via email would be helpful. 

    • This has been talked about in the past. now that we have a piece status we can possibly add details about how pieces of a certain status should be handled. I think we have a feature for that. 

  • Use AI to generate the predictive pattern for serials claiming in the future. 

  • UAT explanation could have included screenshots to help remove guesswork from the test. 

• Next steps: 

  • Prioritize enhancements, update functionality and begin performance testing. 

• Retrospective discussion: 

  • Reminders about UAT timing have been helpful

  • Having a sequence of actions for each test has been helpful

  • really appreciate the ability to work through UATs in our own time. 

  • Could be helpful to have someone taking the group through testing. Having a functional expert guiding the session would be helpful. 

  • Could coordinate with LCAP (Library of Congress project) PO's more closely to facilitate UAT's. 

  • Susanne Gill (BVB) 12:42 PM
    It would have been great to know that you needed 3 days...Some of the People didn't realized it and couldn't finish

• Susanne Gill (BVB) 12:46 PM
  Is it just for Serials or one-time orders as well?

  • Dennis: I don't think there is a restriction. Any order line can be related to a pattern. 

  • Martina: That is correct. You can link a serial record to any po line. Serial app can create expected pieces for you in receiving even if it's a one time order or standing order. 

  • Dennis: You can claim any piece, no matter the format. 

• Julie Stauffer 12:49 PM
  As you know, we are not using Receiving for serials, but I am curious if the new Serials app will be coordinated with the new binding functionality, e.g., default bound/unbound settings; binding instruction notes, etc

  • Dennis: Right now it's all being developed in parallel. But its all part of the receiving application. In theory, the serials app is communicating with receiving and it might just be a matter of adding additional functionality to connect. 

  • Martina: That is correct. At the moment, we are not planning it in the serials app since it is being developed in the receiving app.