Page Comparison

We will be looking at the data model for the Orders module to see whether anyone has been able to map their existing data elements, and to see what kinds of problem they may have encountered. If no one has been able to do anything yet, we may have a short meeting.

Spreadsheet for Orders: https://docs.google.com/spreadsheets/d/1Ll9eWACkmUVrZvOXC7CaOYQBjEWrBR9aHstqR7P-FWY/edit#gid=902905968

The meeting began with a discussion of the Composite_to_folio_orders sheet that Martina and Uschi has done some work on. There was some uncertainty abput the definition of some of the field names in the FOLIO schema;.

Ann-Marie Breaux came on the call and explained that in FOLIO, the order type code is a combination - 3 fields combine to cause specific order action.

• One time or ongoing
• Physical or electronic
• Create an inventory - container, instance, nothing.

Depending on what you are choose, you will be presented with different workflows and different actions will be triggered.

The order starts with enough bib data to create an instance or container or holdings and items.

Finishing the order updates the inventory record.

You can start with a bib record and not re-type.

Or order on a vendor site and import, either with API or load EDI. Will create the order and inventory records.

If a Marc record is associated with the order it will end up in the MARCstore.

There will be a way to get between the order and the inventory instances

FOLIO will have the order record with relevant data accessible with order record storage.

A large dev team is working on this so the schema should be finalized soon.

The Container piece is new, for example.

the PO# in FOLIO will be generated sequentially; 12 characters in PO#. Libraries may choose to migrate existing PO#s to that field.

999 lines within any PO

PO Line numbers: ABC123-1, ABC123-2, ABC123-3 etc

line # will be the match point for searches.

Single line POs will add -1 to the PO number

PO line - 16 characters. (Voyager allows 25)

PO line is child to the PO.

Martina observed that sometimes they need two of their fields to make one in FOLIO

Might make the most sense to not migrate open orders and do the switch at the fiscal year.

Makes sense to migrate subscriptions but maybe not open orders.

Dale mentioned that even if a lot of the Acq app has to be set up manually, it would be good if it could accept scripted input. Implementers don't want to populate funds manually everytime.

Ann-Marie said you can create orders now with API and JSON documents.

NEXT MEETING - discussion of loading users. Anne pointed out she had developed a log for loading data that she hoped others would use: https://docs.google.com/spreadsheets/d/1Q3TtDtOaYYYdoH3JyzQasmVyvMmHZ9CbcW5-0UIX9Pk/edit#gid=1572006106