2018-05-14 Reporting SIG Notes

Date

08 May 2018

Name	Organization	Name	Organization
Sharon Beltaine	Cornell University	Peter Murray	Index Data
Elizabeth Berney	Duke University	Erin Nettifee	Duke University
Joyce Chapman	Duke University	Karen Newbery	Duke University
Elizabeth Edwards	University of Chicago	Tod Olson	University of Chicago
Claudius Herkt-Januschek	SUB Hamburg	Scott Perry	University of Chicago
Doreen Herold	Lehigh University	Robert Sass	Qulto
Anne L. Highsmith	Texas A&M	Simona Tabacaru	Texas A&M
Vince Bareau	EBSCO	Mark Veksler	EBSCO
Harry Kaplanian	EBSCO	Kevin Walker	The University of Alabama
Ingolf Kuss	hbz	Charlotte Whitt	Index Data
Lina Lakhia	SOAS	Michael Winkler	OLE
Joanne Leary	Cornell University	Christine Wise	SOAS
Michael Patrick	The University of Alabama	Holly Mistlebauer	Cornell University
Emma Boettcher	University of Chicago	Andrea Loigman	Duke
Uschi Klute	GBV	Lynn Whittenberger

Item	Who	Notes
Review Data Lake JIRA Tickets		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?
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."