| Actions items (to dos) until we meet next time? 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 Reference data by app Loan types, fund codes, call number types, etc.
Record types by app Orders, order lines, users, instance/holdings/items, etc.
App settings Data Import job profiles, Inventory export targets, etc.
Tenant-wide data & settings Libraries, location codes, service points Consortial partners & relationships Permission sets
Create the spreadsheet (CW) Insert links to GitHub repositories Identify the respective SIGs (CW) Creating a rubric - what types of data will be helpful - input to each SIGs (Autumn) Will create on a spreadsheet in shared Google Drive with columns/categories of data for each app Also solicit data samples from respective libraries
| | How did Chicago share data? Exported out. Inventory data is relatively safe for sharing How did we officially share the data? Can we share bigger sets of data for BugFest, and then create a smaller set for Snapshot? Chicago data was originally scoped to Inventory, and did not contain connections to other records. How do we deal with different institutions' data? What does the environment that we are putting the data into need to look like? What should the FOLIO BugFest actually be managed Maybe we need to carefully curate the reference data in advance of getting the data Libraries should be testing the logical portion of features, and not full workflows We’ll want to iteratively update BugFest dataset across different areas What’s in BugFest right now? Verify different types of data and what is working for people?
Do we need a consortial data set? Consortial BugFest: so far only Mobius Start with non-consortial first, then go with consortial Hold off on consortial issue for now
Action items: Populate spreadsheet of reference data (AF) Develop a Google Form for SIG responses (AF). This will tell us which types of reference data we need to create ourselves and which types we can source Check about effort needed to get a fresh export from Chicago and documentation on the process (TO) Set up next meeting (YK)
|