2024-06-25 Better Sample Data Meeting Notes

Owned by Charlotte Whitt
Jul 23, 2024
2 min read

 

 

  1. Welcome:

    1. Yogesh Kumar

    2. Kristin Martin

    3. Autumn Faulkner

    4. Charlotte Whitt

    5. Tod Olson - Regrets

  2. Intro / announcements

    1. Start defining the task this group’s work. See next bullet point.

  3. Scope and time frame?

    1. Timeline by Bugfest Ramsons

    2. Will work our planning backwards based on that.

    3. Environments:

      1. FOLIO Snapshot (where all code get merged into)

        1. Updated daily

      2. Rancher environments for each development team

        1. Has all new code

      3. Sprint test environment (full data)

        1. Updated each sprint every two weeks

      4. Bugfest (full flower FOLIO release after feature complete)

        1. Bugfest is also updated for each CSP - jira tickets has status Awaiting Release and Awaiting Deployment, and finally Bugfest Review

        2. Generally 2 Bugfest environments available at a given time (upcoming release and its preceding release)

  4. Presenting on some very initial work

    1. High-quality data in reference environments 2024

    2. Files in Bugfest Quesnelia: MARC Authority Records with links to instances with source MARC - DRAFT

  5. Planning of work

    1. Convener of the group - maybe shared? Charlotte and Yogesh

    2. Note taker (rotate)

    3. Regular meeting time? Kristin Martin will find a meeting time for next time. We will find a regular meeting time when we are all back from vacation

    4. When will we meet next time?

    5. Rotation agenda (on wiki of Google doc)? For transparency will provide a link to the Wiki 

    6. Create a wiki page on FOLIO Wiki under the PC? Kristin will do this + google drive in the PC domain

    7. Actions items (to dos) until we meet next time?

      1. Identify the different types of data used in each of the apps as well as data at the tenant level - move the table to spreadsheet 

        1. Reference data by app

          1. Loan types, fund codes, call number types, etc.

        2. Record types by app

          1. Orders, order lines, users, instance/holdings/items, etc.

        3. App settings

          1. Data Import job profiles, Inventory export targets, etc.

        4. Tenant-wide data & settings

          1. Libraries, location codes, service points

          2. Consortial partners & relationships

          3. Permission sets

      2. Create the spreadsheet (CW) 

      3. Insert links to GitHub repositories

      4. Identify the respective SIGs (CW)

      5. Creating a rubric - what types of data will be helpful - input to each SIGs (Autumn) 

        1. Will create on a spreadsheet in shared Google Drive with columns/categories of data for each app

        2. Also solicit data samples from respective libraries

    8. Longer term actions

      1. Get input!

        1. Involve PC liaisons & SMEs

        2. Info from frontline staff about what would be helpful

      2. Identify libraries where we can borrow data - uChicago, MSU

      3. Identify data we will create from scratch  

        1. Ask for contributions from SMEs here to ensure robust data, use of all possible features

      4. Get development teams to help us extract identified data as json

      5. To get data updated on GitHub, here the task needs to be assigned to the different development team

        1. Write up jira tickets to be assigned to development team