Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Discussion items

Review JIRA tickets OKAPI-570,UX-PROD-331 and UX-PROD-332

-what additional design considerations do we need to consider for the Data Lake?

-what additional design considerations do we need to consider for the Data River?

ItemWhoNotesReview Data Lake JIRA Tickets
Data Structure for SQL Reporting

Data analysts expect to be able to use tools such as Tableau and BIRT to access data in the Data Lake using SQL

-What steps need to be taken to ensure SQL access

Data Integrity

Data analysts expect the data structure in the Data Lake to have referential integrity

-What steps need to be taken to ensure referential

- Review, discuss, and detail JIRA tickets supporting Data Lake development and document additional considerations

-Establish expectations for data lake reporting (i.e., what types of reports do we expect the data lake to support or not support?)

-Document important features for data lake/warehouse design. Establish timeframe for standing up a Data Lake test environment

-Outline and document dependencies for meeting this target

-Approach for comprehensive report repository, report templates."WolfCon Updates and Impressions
WolfCon Attendees

"Criticality of Reporting for All SIGs/Domains" Presentation

Data Lake session

Data Confidence session

Other sessions?

Data ElementsAll

Reporting data elements gap analysis due by June 11

-data elements to be included in FOLIO V1

-steps to complete this work

-connections with Inventory app, MM SIG, and Data Migration Subgroup





Action items

  •