2023-06-09 Acquisitions Meeting notes



  • Heather McMillan, Dung-Lan Chen, Owen Stephens, Ann Crowley, Emily Robertson. Jackie Magagnosc, Jean Pajerek, Kristin Martin, Lucinda Williams, Martina Schildt, Okay Okonkwo, Kimberly Pamplin, rmerrell, Scott Perry, Sven Thomsen, Victoria Anderson, wiljanen


  • Current: Friday, June 9, 2023

    Housekeeping -

    • WOLFcon 2023 session proposal submission deadline extended thru Monday, June 19 - proposal form link here
    • Early Bird registration deadline - June 18 (more info about WOLFcon 2023 check out this page here)

    PC update (Kristin Martin ) -

    Business -

    • Continue discussions/conversations regarding FYRO

Discussion items

PC UpdateKristin Martin
  • PC update (Kristin Martin ) -

    • Meeting 2023-06-01
      • Special meeting devoted to discussion of improvements to data import
      • Delay of Poppy until November 20 (previous release deadline for Quesnelia)
    • Meeting 2023-06-08
      • Introduction and demo of new Lists App, for cross-app query solution
      • SIG updates
 :10 FYRO Discussion

Scott Perry - They did FYRO on test server and it failed. Not sure why yet. (In Nolana)

Lucinda Williams - has also had failed rollovers, but unchecked boxes about encumbrances and then had a successful rollover. 

Scott Perry (UChicago) 8:15 AM
Of the three check boxes, we only checked close previous fiscal year budgets.

rmerrell 8:16 AM
Our fiscal year ends June 30, and this will be our first time to roll over in FOLIO.  All these problems make it seem kind of scary!

Scott Perry (UChicago) 8:20 AM
We have one ledger and only rollover encumbrances on one-time pols (with the remaining amount).  We do not create allocations as part of the rollover process.

Owen Stephens 8:26 AM
I don’t know if this was covered at the last meeting (if so please don’t repeat) but I’m interested in what the process of investigating what’s gone wrong looks like when FYRO fails. Would it be useful to collect some message definitions in the wiki somewhere (in lieu of more useful messages being added into the system)

Owen Stephens 8:33 AM
Just a suggestion. I guess it just seemed like there might be some common errors that you might be able to check easily - like the additional ledger, or duplicate id etc. etc.

Dung-Lan - Lets start capturing some of the messages and collecting them in a central location with potential solutions when possible. 

Scott Perry (UChicago) 8:37 AM
Duplicate transaction key
This is being shared with the PO for further development

General discussion on different experiences in FYRO.  

Action items