2025-01-29 Better Sample Data Meeting notes

General:

1. Letter to Risk Office at Michigan State University Libraries

2. Eureka platform to be rolled out with the Sunflower release (4/28/2025)

FOLIO Snapshot:

3. Environment is ready

4. Stanford is working on sample authority data to be ready soon for the snapshot environment.

Anonymization of data in Bugfest environments:

Golden Copy:

@Autumn Faulkner did send the finalized letter to the dean for the MSU early December.

The letter was sent to the risk management group, no response yet.

Document written up by the TC: https://folio-org.atlassian.net/wiki/spaces/TC/pages/676855870

Does this cause any changes to what this working group is working on? The expectation is data will work as is.

Is there any update from the Tri-Council meeting on the decision on when to roll out Eureka?

TC approved it. PC is voting on it. CC is still planning to vote on it.

Any new updates on FOLIO Snapshot?

Last Update:

• Finally the Quesnelia environment https://folio-quesnelia.dev.folio.org/ is up and running. The Wiki landing page is updated.

  • Charlotte will work on Inventory data.

    • Update existing 36 FOLIO Source

    • Add 100 MARC records - MM-SIG eyes on the 100 bibs What to ensure that these records has the right mix of misc. types, to cover the basic; incl. bound-with.

    • Instances to have holdings, or holdings/item. Also example on items with No barcode, On order, and regular item barcodes.

  • Shelley to add Authority data. Try to overlap with inventory records both source FOLIO? and source MARC - added 100 authority records via data import.

  • Shelley will provide the job profile used in the institution.

  • Autumn has provided sample data for music records and serials records with multiple holds and multiple items. Holdings statements to be added. - These will be loaded shortly into the env.

    These records are loaded to this groups shared drive.

  • Autumn:

    • Create a job profile to match records from Shelley

    • Setup locations

    • Load sample set of 100 records, bound with relationship and stats codes.

    • MSU Documentation: https://msults.atlassian.net/wiki/spaces/TSdoc/pages/129597445/Importing+overlaying+bib+records+in+FOLIO

  • Order/Order lines data. Kristin will provide screen shots in Edit mode to Autumn. Autumn will create two job profiles, one for open orders and one for pending status.

  • ERM-SIG to help with providing data and review the entered data and data to be added. Kristin to reach out.

• Decide to do a wiki page where we document how the FOLIO Snapshot data is build, and other relevant information for test users.

No updates - working on updating Stanford's env. to Q release.

Does anonymizing matter for Inventory records

• E.g. notes (drop administrative notes, and all notes with private information - this need to be spec’ed out in our documentation),

• local tags, digital book plate information, donor information (can be dropped)

  • This working group should provide the guidelines for this. Shelley asks - where the tool need to be flexible.

• donor or bookplate data in MARC tags? Or other inventory record fields?

  • yes

• any donor info at all?

Will come back to the following topics at next meeting:

• are circulation rules supposed to be anonymized? We will come back to that topic next time.

  • In FOLIO Snapshot the circ rules should be minimal

• FOLIO Snapshot is being build every 24 hours. So the sample data must adhere to that, when adding talking about loan patterns, how do we ensure that open loans adhere to the circ rules for testing things like bills, notices, aging to lost, etc.?

Lee’s group will be tied up in Ramsons and Sunflower work.

Lee suggests to focus on one area; e.g. Patron and usergroups data. Can use a tool to fake data (names, phone numbers, addresses - all PII data).

Shelley is working on this in Phython. Shelley has put together a wiki page to gather requirements for anonymization - https://folio-org.atlassian.net/wiki/x/BQA4K . Shelley has pulled out all reference data. Tod mentioned that maybe Chicago could contribute with a Phyton developer too. Will come back to this in the new year.

Shelley would need to have the technical requirements written up. Will start with the document provided by Lee and his project on the POC.

Done - cleaned existing data to use until a new solution from the data anonymization project is available.

Review timeline document

• Draft - timeline document - Now work can get started.

Other topics

Any items to discuss?