/
2025-01-17 Acquisitions Meeting notes

2025-01-17 Acquisitions Meeting notes

 Date

Jan 17, 2025

 Participants

Alissa Hafele

Kathleen Norton

Masayo Uchiyama

Dung-Lan Chen

Kimberly Pamplin

Owen Stephens

Dwayne Swigert

Kimberly Wiljanen

Peter Breternitz

Jackie Magagnosc

Kristin Martin

Sara Colglazier

Jean Pajerek

Linh Chang

Scott Perry

Joe Reimers

Lisa Maybury

Susanne Gill

John Banionis

Lisa Smith

Tim

 Agenda

Housekeeping -

  • FYI - planned for Tuesday, Jan. 21st, workflow demo & more discussions re: Implementers Topic #152 (Martina Schildt)

  • FYI - planned for Friday, Feb. 14th, OA SIG demo requirements re: needing to be able to add a final expenditure amount to FOLIO after invoices have been approved and paid (Martina Schildt and colleagues)

PC Update (Kristin Martin) -

  • Happy New Year from the PC!

  • Be on the lookout for a Save the Date for WOLFCon 2025: week of September 22 in Kansas City

  • Note that there is a release date for Ramsons: February 3rd

  • 2025-01-09 Product Council Agenda & Meeting Notes

    • Looking to adjust the review process for new functionality for FOLIO, to better mirror the TC process

    • Received input from the POs and want to make process more useful and transparent

    • Looking to track via Jira, where documentation can be attached, make it feel less duplicative of work already occurring within the SIGs

  • 2025-01-16 Product Council Agenda & Meeting Notes

    • Discussion of Eureka timeline: Report on the timeline for adoption of the Eureka platform

    • SIG work will be around the application formalization (Dennis mentioned UXPROD-4997 - Package acquisitions modules into applications based on Eureka platform format. In Refinement )

    • Early adopters and hosting providers are testing to make sure Eureka will work for their customers

    • early reports have indicated that changes in permissions require some work

Business -

 Discussion topics

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes

:01

Housekeeping

Dung Lan

Housekeeping -

  • FYI - planned for Tuesday, Jan. 21st, workflow demo & more discussions re: Implementers Topic #152 (Martina Schildt)

  • FYI - planned for Friday, Feb. 14th, OA SIG demo requirements re: needing to be able to add a final expenditure amount to FOLIO after invoices have been approved and paid (Martina Schildt and colleagues)

  • Co-convener still needed for FOLIO Acq meetings if you would like to volunteer or know anyone who would be interested.

:07

PC Update

Kristin Martin

  • Be on the lookout for a Save the Date for WOLFCon 2025: week of September 22 in Kansas City

    • Work on 2026 also getting set up, no announcements that can be made as of yet.

  • Note that there is a release date for Ramsons: February 3rd

  • Can anticipate that original release date for Sunflower will be pushed as well.

  • 2025-01-09 Product Council Agenda & Meeting Notes

    • Looking to adjust the review process for new functionality for FOLIO, to better mirror the TC process

    • Received input from the POs and want to make process more useful and transparent

    • Looking to track via Jira, where documentation can be attached, make it feel less duplicative of work already occurring within the SIGs

    • Pilot with new functionality from resource access; hearing about a new module coming down the pipe related to ILL

  • 2025-01-16 Product Council Agenda & Meeting Notes

    • Discussion of Eureka timeline: Report on the timeline for adoption of the Eureka platform

      • In Sunflower EBSCO will shift support from Okapi to Eureka

    • SIG work will be around the application formalization (Dennis mentioned UXPROD-4997 - Package acquisitions modules into applications based on Eureka platform format. In Refinement )

    • Early adopters and hosting providers are testing to make sure Eureka will work for their customers

    • early reports have indicated that changes in permissions require some work

:20

Questions?

Dung-Lan Chen

  • Question from Kimberly:

    • Customization - Talked about quite frequently, is there any work on this and is it happening through a particular group?

    • Joe: It is being looked at by POs - handled at Stripes level (?)

    • Khalilah taking the lead

:22

Claiming UAT

Joe Reimers

  • Claiming UAT starting next week, starting on Tuesday

  • ~:24: Claiming app demo in Snapshot - Setup

  • Add integration in Organizations. If you are claiming, must have integration.

image-20250117-142550.png
  • ~:26: Create order/order line

  • “Claiming active” should be checked in POL

  • Need to open order to create receiving piece

  • :28 - Receiving - piece shows up as expected because it is just created

  • Added “Mark late” for manual status change

    image-20250117-142840.png
  • Claiming - What has claim active true? What has receiving status of late?

  • Claiming app really useful for finding pieces of all statuses (via filters)

  • By default see claiming active and late

  • After choosing line:

  • Have ability to Send claim, Delay claim, mark unreceivable for all pieces in list

  • Can limit to particular vendor/order types, etc.

  • Can search on:

  • Send claim

  • Determine claim expiry date

  • Now will show up under “Claim sent” status

  • :31 - Export Manager

  • Click Job ID and will download CSV file

  • This is Sunflower functionality

  • “Expected” - ordered, not yet received, not late

  • Kristin - When you have a one-time order, basically “on order” and then received goes to “in process.” One-time orders with no expected date would they stay in on order?

  • No new status. In receiving a piece will be Expected, Late, Claim Delayed, Claim Sent, Received, or Unreceivable.

  • Item status is on order, but receiving piece status is expected.

  • Is this set per vendor or per purchase order line? - Per purchase order line - tick claim active and set a receipt date - These will tell FOLIO it needs to be claimed and when it’s expected to arrive.

  • Susanne Gill (BVB) 8:36 AM
     Will there be Dates in the CSV? Like the expected date for an issue

    • Not in there, but can take that feedback if it is necessary

  • POL: Receipt date = Expected Date

  • Works quite nicely with Serials app

  • Claiming interval = Claim delay. Claim is late, what is the expected delivery time? What is your buffer for when you expect it? In days. Will be modified in the near future where claiming interval will be replaced with claim cycles.

  • Claiming interval of 1 = 1 day after expected date, will become late.

  • Configurable at the Organization level - default claim interval for vendor. Can also be set up in PO/POL template.

  • Can you set different claim intervals for same organization?

    • Not at this time.

  • Susanne - Talked with Bjorn and Andre from Leipzig. - On agenda being able to do this separately. (one-time/ongoing)

  • Will announce UAT in the Slack channel

 Action items

 Decisions

Related pages