Page Comparison

Continue discussion on Finance. Funds, budgets, ledgers, and fiscal years. Sharon Beltaine has kindly generated a gap analysis spreadsheet for Finance on which to document our needs. It can be found here. It is based on the Acquisitions Interface Fields spreadsheet found here.

Sharon Beltaine, who created the spreadsheet, pointed out some issues on how it had been laid out; she asked whether her addition of the record name under the record type header was useful; after some discussion it was decided to delete the rows containing the record name.

Uschi asked about the subtransaction data element and whether the statement, "to-many; all the tags associated to the budget" was a cut-and-paste error. This led to a long discussion of the purpose of the subtransaction record and finally consensus that it was unlikely to be used for migration, as it is used internally in FOLIO typically for fund-to-fund adjustments. During the discussion Scott Perry mentioned that he had tried to model a financial structure in one of the FOLIO test systems, but had had problems doing so due to system instability. Dennis Bridges responded that much of the instability was due to system issues, e.g. the deployment of a new Stripes module, rather than bugginess in the acquisitions code. The discussion branched off into whether it was possible to do modelling of the financial records at this point and how likely it was that financial structure would be migrated at all. The upshot was that modelling of the financials will be deferred and the group will switch to working on purchase orders, which Dennis Bridges said should be quite stable. Dennis will post the location of the latest version of the purchase orders and related json to the Data Migration Subgroup list and the Data Migration slack channel. Tod Olson will work at deriving a basic list of the data elements and descriptions, if any, from that json and will forward to Sharon Beltaine for final setup.

Next meeting Dennis Bridges will do a short demo of order functionality to help members understand how data elements are used; this should assist subgroup members in modelling data migration for purchase orders.