2018-04-30 Reporting SIG notes

Previous Notetaker: Joanne Leary

Today's Notetaker:Claudius Herkt

Thanks to Tod Olson for convening the April 23 Reporting SIG Meeting!

WolfCon Update: At this point, the Monday 5/7/18 9am Reporting SIG meeting will still take place because WolfCon sessions for SMEs don't start until the afternoon of that day.

Reporting SIG members should be able to attend the WolfCon conference remotely via Zoom links for sessions. Stay tuned for more information on this soon.

Christie Thomas, Charlotte Whitt

Christie Thomas and Charlotte Whitt from Metadata Management will join us for a discussion of Inventory and MARC data required for reporting. Here are some topics/questions to consider:

• (from Sharon) What is the current plan for MARC data in Folio? Will we be able to report on all local and standard MARC data? (from Christie) It is important that everyone understand the difference between the Folio instance record and the source MARC record. The Folio instance record may have data that is native to the Folio data model or may be derived from a source record. The difference is important in this context because it may be that data that has historically been sourced from MARC may be better drawn from the Inventory record, especially once Folio supports source bibliographic metadata formats other than MARC. (If the data is pulled from the Inventory it will already be somewhat normalized and reports will not need to be created for individual formats such as MARC and BibFrame.) Note: If you are attending WolfCon, see "How MARC cataloging app and inventory fit together (MM)" session on Tuesday at 2pm.
• (from Christie) How will we include data elements for holdings and item data?
• (Christie) Discussion about UChicago's local audit of their reports that rely on bibliographic / MARC, holdings, and item metadata (see link from Christie below)
• (from Sharon) What is the most efficient and effective process for the Reporting SIG to use to verify the inclusion of data elements needed for reporting in Folio?
• (from Sharon) Have the MM SIG and/or Inventory developers discussed ways we can ensure referential integrity across Folio apps to support reporting functionality?
• (from Sharon) What are the most important design considerations from an Inventory and MM perspective for building a data lake/warehouse environment for Folio?
• Other questions/topics?

Related Links:

(from Christie) At Chicago we have started to select some representative reports and ad hoc queries and systematically identify the data that is required. You can see how we are doing this here: https://docs.google.com/spreadsheets/d/1dVAejtiqzc1E5nFLW85XZvHHrUER58EHrlwCK2ZrhTI/edit?usp=sharing

Reporting SIG Master Spreadsheet

https://docs.google.com/spreadsheets/d/1svUM74Dkg4KvTXLzKZK_2k_SxeukX-87NnYf8CaTrYQ/edit?usp=sharing

Data Migration Subgroup Google Drive folder

https://docs.google.com/spreadsheets/d/15khBvG7hsUbIIofh6ZyrH_-sl2kngXdcQ24sBswAe_k/edit?usp=sharing

MM SIG Working Groups - Inventory Metadata Elements

https://docs.google.com/spreadsheets/d/1kdYx63J0KoqR3-LUHuPAzERgj8WE0OQ08rzuCaJaHWs/edit#gid=952741439

Review current plans for WolfCon and brainstorm ways Reporting SIG can make best use of the conference time and resources.

Important WolfCon Scheduling question: Reporting session on Data Confidence currently scheduled for Thursday morning, when some attendees may be catching flights back home. Shall we make a request to schedule this session for another time? If so, when is the best time? Wednesday morning?

KN:Open in Google sheets to view the entire schedule.

WolfCon Topic Proposals: https://docs.google.com/spreadsheets/d/17JmVl-XUaALDYtyqEzPGGYyHAbH8JQM63XPdl9ZxKFU/edit?usp=sharing
Current WolfCon Schedule (View Only): https://docs.google.com/spreadsheets/d/1jmjRAKBXJN2i1qPLOjdbeqi5xndTPyKzrDKuB8MeeBQ/edit?usp=sharing

WolfCon organizers are working to make the May 7-10 conference sessions available by ZOOM so all project participants may join WolfCon sessions remotely. More details on this coming soon.

Strong interest in the Data Lake:

The cases for this were the following:
- the data in the Lake "gets old". The concern, that data in the lake that are several years old can not anymore be interpreted.
- the data in the Lake miss metadata
- suggestion: the Lake will be used for short-term and mid-term reports
- the need for the Lake is to get FOLIO going. If it is running, it is wiser to import the data into a (more formal, more structured) data warehouse.
- another concern questioned with the Lake was referential integrity

(In case this is needed to revisit or for reference.)

We will discuss strategies for translating reporting requirements into reporting deliverables

KN: See Reporting SIG master spreadsheet: https://docs.google.com/spreadsheets/d/1svUM74Dkg4KvTXLzKZK_2k_SxeukX-87NnYf8CaTrYQ/edit#gid=312878932

-thank you for adding names to each report (just a few missing at this point)

-review updated Column E ("Legacy System Data Element Sources") and new Column F ("Folio Data Element Sources Notes")

-Reporting SIG members and new Reporting PO to work with other POs and SIGs to identify data elements needed for each report

-Reporting SIG members and new Reporting PO to work with other POs and SIGs to identify candidates for "in app" reports

-please continue to add your Report Requirements Contacts in Reporting SIG Master Spreadsheet

-report contacts need to be reachable, if not part of Folio project, please add person's email address

Review and update Topics for Future Reporting SIG Meetings