To me a data warehouse means star schemas and column stores, and we probably won’t have very much of that at least in the first implementation, for various reasons.  So to avoid confusion, I’ve been referring to it as a reporting database.

There also is some disruption happening in analytics which may require different kinds of database and query models, and I think we should try to keep this implementation fairly lightweight.


On Dec 18, 2018, at 11:20 AM, Sharon Marcus Beltaine <slm5@cornell.edu> wrote:

Ingolf,

Yes, the Library Reporting Database is part of the Library Data Platform that Nassib presented in response to the Reporting SIG's requirements for a data warehouse. According to Nassib, the architecture for our reporting environment is not exactly a data warehouse. We are using the term "Library Reporting Database" to provide an easy way to reference the environment. 


Nassib may want to weigh in on this topic with more explanation...


Yes, the goal is for eUsage statistics reports to be generated from the Library Reporting Database being developed by the Reporting SIG.


Okay, glad to hear a second vote of support for the Reporting Prototype subgroup moving forward with the eUsage project. 


Thank you!


All the best,

Sharon



Sharon Beltaine

Applications Systems Analyst III

Cornell University Library

FOLIO Reporting SIG Convener

FOLIO Data Migration Subgroup member

slm5@cornell.edu

+1 607-255-9477

Make an appointment: https://calendly.com/slm5




From: reporting-sig@ole-lists.openlibraryfoundation.org <reporting-sig@ole-lists.openlibraryfoundation.org> on behalf of Ingolf Kuss <KUSS@hbz-nrw.de>
Sent: Tuesday, December 18, 2018 9:54 AM
To: reporting-sig@ole-lists.openlibraryfoundation.org
Subject: Antw: prototype eUsage next?
 
Hi Sharon and group,

*  I missed the definition of the term Library Reporting Database. Is this part of the Library Data Platform (LDP) and the work / concept which Nassib presented ?

* I understood that we principally agreed that eUsage statistics reports will be generated from the central reporting solution (the LDP with the data warehouse) which the Reporting SIG develops / supervises. Correct ?

If the answer to both of my questions is "yes", the work on the data model for eUsage is certainly a good direction to take right now, in my opinion.

Best,
Ingolf



>>> Sharon Marcus Beltaine <slm5@cornell.edu> 17.12.2018 22:38 >>>
Reporting SIG,
In the Reporting Prototype subgroup, we have been working on some initial circulation reports and testing out various reporting applications against the Library Reporting Database. During our meeting today, Annika Schroer provided us with a demonstration of the eUsage app and we discussed setting up a data model to support reporting on data associated with this ERM-related app in Folio. 

During the Report Prototype subgroup meeting just now, we discussed the idea of working on a data model for the eUsage app, and agreed this would be a good project to work on next. As it turns out, some of the pieces we need for the circulation report data model are not quite ready yet, so we have gotten about as far as we can go with this area for now. 

The Report Prototype subgroup would like to go ahead and start working with Annika and Bjorn on a data model and reports in the area of eUsage statistics for the Library Reporting Database. 

The priorities for our work are set by the Reporting SIG, so I want to be sure you agree this is a good direction for us to take with our work right now. Please share your thoughts on this when you have a chance.

All the best,
Sharon



Sharon Beltaine
Applications Systems Analyst III
Cornell University Library
FOLIO Reporting SIG Convener
FOLIO Data Migration Subgroup member
+1 607-255-9477
Make an appointment: https://calendly.com/slm5

------------------------------------------------------
You received this message because you are subscribed to OLE Mailing List
"reporting-sig".
To unsubscribe from this list and stop receiving emails from it, follow
this link: http://archives.simplelists.com.
To post to this group, send email to
reporting-sig@ole-lists.openlibraryfoundation.org
<mailto:reporting-sig@ole-lists.openlibraryfoundation.org>.
Visit this group at
https://ole-lists.openlibraryfoundation.org<https://ole-lists.openlibraryfoundation.org>
.
lists.openlibraryfoundation.org>
.

------------------------------------------------------
You received this message because you are subscribed to OLE Mailing List
"reporting-sig".
To unsubscribe from this list and stop receiving emails from it, follow
this link: http://archives.simplelists.com.
To post to this group, send email to
reporting-sig@ole-lists.openlibraryfoundation.org
<mailto:reporting-sig@ole-lists.openlibraryfoundation.org>.
Visit this group at
https://ole-lists.openlibraryfoundation.org<https://ole-lists.openlibraryfoundation.org>
.
lists.openlibraryfoundation.org>
.

------------------------------------------------------
You received this message because you are subscribed to OLE Mailing List
"reporting-sig".
To unsubscribe from this list and stop receiving emails from it, follow
this link: http://www.simplelists.com/confirm.php?u=H3YKJudWvPZRngEDnRqXjVGnBE2zUdD4.
To post to this group, send email to
reporting-sig@ole-lists.openlibraryfoundation.org
<mailto:reporting-sig@ole-lists.openlibraryfoundation.org>.
Visit this group at
https://ole-lists.openlibraryfoundation.org<https://ole-lists.openlibraryfoundation.org>
.
lists.openlibraryfoundation.org>
.