Versions Compared

Old Version 5

changes.mady.by.user Sharon Markus

Saved on

compared with

New Version Current

changes.mady.by.user Sharon Markus

Saved on

Key

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

Date

Attendees

Present?NameOrganizationPresent?NameOrganization
XSharon BeltaineCornell University
Peter MurrayIndex Data

Elizabeth BerneyDuke University
Erin NettifeeDuke University

Joyce ChapmanDuke University
Karen NewberyDuke University

Elizabeth EdwardsUniversity of ChicagoXTod OlsonUniversity of Chicago
XClaudius Herkt-JanuschekSUB HamburgXScott PerryUniversity of Chicago
XDoreen HeroldLehigh University
Robert SassQulto

Anne L. HighsmithTexas A&MXSimona TabacaruTexas A&M

Vince BareauEBSCO
Mark VekslerEBSCO

Harry KaplanianEBSCOXKevin WalkerThe University of Alabama

Ingolf Kusshbz
Charlotte WhittIndex Data

Lina LakhiaSOAS

Michael Winkler

OLE
XJoanne LearyCornell University
Christine WiseSOAS
XMichael PatrickThe University of Alabama
Holly MistlebauerCornell University

Emma BoettcherUniversity of Chicago
Andrea LoigmanDuke

Uschi KluteGBV
Lynn Whittenberger

Discussion items

ItemWhoNotes
Assign Notetaker, Take Attendance, Review
Data Lake JIRA TicketsReview 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."
agenda

Today's notetaker: Doreen Herold

Last week's notetaker: Claudius Herkt


WolfCon Updates and ImpressionsWolfCon Attendees

"Criticality of Reporting for All SIGs/Domains" Presentation

Data Lake session - Framing Questions, Notes, Action Items

  • feel free to use this presentation on your campuses to provide explanations, increase awareness
  • attendance exceeded expectations; targeted towards developers but audience had a great mix (people are interested)

Data Confidence session - Framing Questions, Notes, Action Items

Link to Notes for All WolfCon Sessions

Data Elements for Reports due June 11

Other sessions?

Other conference impressions, thoughts, ideas?

  • need to distinguish, and make clear, what is a working meeting vs. informative meeting (attendance included those not involved in Reporting SIG and required time to inform, taking time away from covering agenda); wonderful there is interest and will need to ensure that, in future, there are sessions to inform non-Reporting SIG members with a status update
  • approval of PO
  • need to get approval of testing environment
  • Okapi, message queue
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

  • data elements in our current systems to be mapped into FOLIO
    • Christie Thomas (Chicago; MM SIG) and Anne Highsmith (TAMU; migration) have been working on this already
    • we'll join their efforts
    • review your local reports to identify what data elements you currently use that you would like to see used in FOLIO
    • critically important for first implementers but also significant for those implementing later to ensure that the needs are being addressed as early as possible; please meet with your institution's colleagues to cover all functional areas
    • look at meeting notes from April 30
    • make a list of needs for reporting and bring to our next meetings
    • we still have much work to do re: increasing awareness about data store, support from mgt/project; contact
Topics for Future MeetingsAll

Review and update Topics for Future Reporting SIG Meetings

Action items

  •