2017-09-25 - Reporting SIG Notes

Owned by Ingolf Kuss
Last updated: Sep 25, 2017

Date

Attendees

Goals

Discussion items

TimeItemWhoNotes
5WelcomeIngolf 
5IntroductionsIngolf

Welcome to new member John McDonald

John is the new EBSCO Director of Product Management, Analytics & Assessment

20Summary on Developers' MeetingPeter Murray

Peter reports from developers' meeting in Montreal Sept 18-20 (Slides)

Organization of Development:

Recap of operational goals:

  • UX process to capture and distill library requirements

  • Implement V1; core library functionality

  • Construct an extensible platform that 3rd parties can use
  1. Rough-In (phase 1)
  2. Refinement Phase

FOLIO-UX-Update (Filip): CSS Layers (skeletal styling - host scheme - end user scheme), Preferences (tenant preferences, end user preferences)

  • User Experience Documentation
  • Resource Management (see slides)

  • Dev Ops - next steps

  • Define preliminary test infrastructure

  • Document initial performance goals/expectations

  • Define data migration requirements

  • Create toolkits for library profiling, data migration

  • Load real library user data

  • Define external integration requirements
    ==> Looking for more participants in the Dev Ops & Management SIG, Systems Operations and Management SIG Home , People from OLE institutions.
20RDBS Database model for reportingIngolf

I presented my first sketch of an RDBS database model. The model is designed using MySQL Workbench. It is desirable to have a more social software tool to be able to design the database model in an agile way. I tried with https://www.genmymodel.com/, but the free version is to small (doesn't capture enough data).

The model consists of a set of database tables. The tables are related to each other by 1:N - relationships or 1:1-relationships. These relationships can be mandatory or optional. Each database table consists of a set of datafields. The datafields at least have a name and a data type.

My target was to inlucde any data field which appears in the Reporting SIG Master Spreadsheet (https://drive.google.com/open?id=1svUM74Dkg4KvTXLzKZK_2k_SxeukX-87NnYf8CaTrYQ) in this model - and of course the model must be enlarged to include ANY field which we will ever need in reporting!

I put comments from the Master Spreadsheet to this model. The comments can appear at the table level and at the field level. I also put the IDs of the reports that use this field for some fields (where the usage of the field is not clear).

The outcome reminds me of the relational database model used in Kuali OLE - not surprisingly.

I haven't finished with the model yet, i.e. didn't go through the whole Master Spreadsheet, I will do so.

I will put the model - exported as PDF files - into the Reporting SIG Google Drive folder.

Comments from the group:

  • (Peter) : presenting bibliographic records as MARC records is too restricted, this must be generalized and be replaced by Codex objects.
  • there should be more emphasize on electronic resources, which should manifest itself in the design of the model
  • there is not yet a Product Owner for Reporting

 

 

Action items

  •