/
2025-03-18 Acquisitions Meeting notes

2025-03-18 Acquisitions Meeting notes

 Date

Mar 18, 2025

 Participants

Aaron Neslin

Jean Pajerek

Okay Okonkwo

Aaron Neslin

Jean Pajerek

Okay Okonkwo

Alissa Hafele

Joe Reimers

Peter Breternitz

Ann Crowley

John Banionis

Peter Sbrzesny

Anne

Kathleen Norton

Rhonda Fuhrmann

Daniel Huang

Kimberly Pamplin

Sabrina Bayer

Daniel Welch

Kimberly Wiljanen

Sara Colglazier

Dennis Bridges

Kristin Martin

Scott Perry

Dung-Lan Chen

Lisa Maybury

Stephanie Larrison

Dwayne Swigert

Lisa Smith

Susanna Skowronek

Heather McMillan

Martina Schildt

Susanne Gill

Heiko Schorde

Masayo Uchiyama

Sven Thomsen

Jackie Magagnosc

Michael Hobson

Sylvia Hamann

Jason Moore

Molly Driscoll

Vanessa French

 Agenda

  • Joe will review Batch allocation

  • WOLFcon 2025 - Acquisitions topics? Proposals need to be in by April 11. 

    • WOLFcon 2025 will take place from September 23–25 at The Westin Kansas City at Crown Center in Kansas City, Missouri, USA.

    • Pre-conference workshops are scheduled for Monday, September 22.

    • Past Topics: 

      • 2024

        • Discussed FOLIO Financial tracking

        • Consortia Support

        • Acquisitions automation review

        • AI workflows with FOLIO (Jeremy Nelson)

        • Serials and Binding

      • 2023

        • Orders and Invoices

        • Fiscal Year rollover

        • Serials development and progress

        • Several ERM sessions

  • Implementers Topics 169

 Discussion topics

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes

 

WOLFcon 2025

Heather McMillan

  • WOLFcon 2025 - Acquisitions topics? Proposals need to be in by April 11. 

    • WOLFcon 2025 will take place from September 23–25 at The Westin Kansas City at Crown Center in Kansas City, Missouri, USA.

  • Kristin Martin 12:02 PM
    BTW, The deadline for submissions is April 25, 2025 now.

  • Owen, Joe, and Martina planning for another serials, binding, claiming, receiving topic.

  • Kristin - series of show and tell demos with different libraries about loading and managing orders. Would love to do something like that again. Maybe Chicago and some others.

    • On integration side would be great to look at APIs for orders.

  • :08 - Dennis - Workflow efficiency in FOLIO. Presentations where folks are talking about how they use FOLIO are valuable and interesting. For POs there is interest in how you use the systems. Sometimes a lot easier to have those conversations in person.

  • Same kind of support for online this year?

    • Yes, with fee to support technology involved

  • Vanessa French 12:10 PM
    The proposal submission form says "All sessions must have at least one presenter or moderator in person."

:12

Batch Allocations

Joe Reimers

  • Overview of UAT responses

  • 6 responses in total, was not expecting a large number

  • Do the question types work for you or do you hate them? Creates a nice visual for how people feel about things.

    • Comments in chat that this works

  • One response requesting two additional columns “Unavailable” and “available” with the amount of the budget. Would help to see if there is enough money.

  • Is there a use case when doing allocation/deallocation where you would need to know funds on hand vs actual?

  • Most people tested via CSV upload. A little choppier. Anytime dealing with CSV upload vs direct within app, greater opportunity for confusion or bad data to sneak in. Biggest issue, how to resolve errors that come up.

  • Opportunities to improve on error resolution.

  • Do the allocation logs contain information needed for audit?

    • Issue in b/w writing requirements and implementation where location of logs changed. Batch allocation logs moved to different Actions menu.

    • Why was it moved to the other actions menu? Not intuitive to people.

      • Allocations are ledger specific. Logs are not. Logs are the logs and you see all of them.

      • Open to feedback as to where they should reside.

  • Working on correcting error notifications; more feedback absolutely welcome.

  • All in snapshot, can test there

  • Coming up on BugFest in a few weeks.

    • Would encourage anyone who is interested to test in BugFest. While past point of making major changes, can still take feedback on ways to improve.

  • Which release is this in?

    • Sunflower

:28

Implementer’s topic # 169



  • When on order level and click close, can choose from a long list of reasons for why you are closing the order. All the reasons should also be at the POL level.

    • Have encountered this more often at ongoing level, but also applicable to one-time orders.

    • Frustrating that your only options are that it stays ongoing or cancelled. May not be cancelled, may be complete, ceased, etc.

    • Or maybe it would automatically populate over. -- Only problem here is if you have an order with multiple POLs, might not apply to every POL. (e.g. one title ceases).

  • Dennis - Are there situations where the status needs to be different?

    • Is the real difference that some might be cancelled and some might be closed?

  • In multiple POLs could be variation.

  • Options have nothing to do with the order level, has always been at the wrong place so to speak.

  • Is this unique to electronic material?

    • No

    • Print might cease or split into multiple titles.

  • What if we move reason for closure from the PO to the POL?

    • Agreement in chat

  • Could also have two options at POL closed / cancel, but PO would only have closed status then.

  • Heather McMillan (TAMU) 12:38 PM
    example, we have a membership that includes four print titles, and we put them all on one po with four pol's.  One of the titles ceased, the other three continued.

  • If POL had status of cancelled would you have different reasons for cancellation?

    • Yes

  • If we still allow the POL to be cancelled - options are closed or cancelled, but in both of those cases would apply a reason for closure/cancellation. Both would essentially be “Resolved.”

  • Status possibilities at POL would be closed or cancelled and in either case would be asked to specify a reason and add a note.

  • Does it still make sense to have note?

    • Yes, would be excellent if that were always editable. Cannot currently edit at PO level.

    • Does not need to be mandatorily filled in.

  • Martina Schildt | VZG 12:43 PM
    Being able to edit would be very helpful

  • Vanessa French 12:43 PM
    and if the note went in as a closure note type on the POL in the notes field

  • Would it be problematic to migrate reason for closure from PO to POLs?

    • No way to know what reason each POL should have.

  • One-time? - Fully received/Fully paid when workflow status is closed and reason for closure is complete.

    • Can vary, receipt not required

  • For ongoing orders would not be problematic. Only two options are ongoing/cancelled.

  • Would be better to migrate reason from PO to POLs than to let that data disappear or better to not have reason for closure?

  • In theory could have PO with many POLs with many journal titles - vendor EBSCO, ongoing, subscription - 100 POLs with all journal titles. Over time, manage individual POLs as they happen. Wouldn’t be closing the PO, would be needing to manage the individual POLs.

  • Daniel Huang 12:50 PM
    the more specificity the better

  • Reasons should be at the title level.

    • Daniel Huang 12:51 PM
      exactly, the change in vendor/title and that would be PO line level

  • There is necessarily a different handling of one-time/ongoing orders.

  • Kimberly Smith (MTSU) 12:52 PM
    I agree the One-Time versus Ongoing are different

  • Problem for one-time orders is related to business logic. Receipt status changed to fully received. Paid invoice, changed to fully paid. Once both done, completes the order.

  • Joe Reimers (EBSCO) 12:54 PM
    In broader strokes, I think there's an opportunity to examine, essentially, Serials Acquisitions vs. Monographic Acquisitions, and how can we best accommodate both

  • Daniel Huang 12:54 PM
    I'd argue we do a single PO per one-time just to make sure there is nothing janky with multiple POLs that we regret later

  • Daniel Huang 12:54 PM
    like let's not even talk about returns of physical material lol

  • Kimberly Wiljanen 12:55 PM
    At MSU, we do a single PO for firm orders, but multiple POLs for our approvals

  • If you unopen an order, might not want to lose that information.

  • Will need to explore how to manage this when you are closing orders from the PO level. From POL pretty straightforward.

  • Does also get reflected in inventory. (e.g. shows that something is cancelled, when actually ceased).

 Action items

 Decisions

Related content