I was speaking of transactions as a technical term from the perspective that all interaction between the browser (or an outside system) and FOLIO is an HTTP transaction. Those transactions provide the hooks on which we can hang processes such as streaming out data to tables on a SQL server. So an update to a bibliographic record is itself a form of a transaction.

One other note: the way FOLIO is designed means that there is not direct access to the underlying data storage mechanisms, so updates are handled by constructing a HTTP request to the server. This can quickly get pretty technical -- describing the mechanisms for using the HTTP API -- so I think I'll stop here. If at some point the reporting SIG would like a demonstration of the API for writing data, I'd be happy to show that.

Peter

On May 12, 2017, 5:58 PM -0400, Joanne Elisa Leary <jl41@cornell.edu>, wrote:

Peter,

Just to clarify: what do you mean by 'transactions'? Our reporting work involves delving into lots of non-transactional data. Whatever system we get will have to allow us to deal with true transactions (like circ transactions, acquisitions transactions, etc.) but also a lot of data related to bibliographic records and more (for creating lists, troubleshooting, updating records, generating statistics, etc.).

Thanks - Joanne

Sent from my iPad

On May 12, 2017, at 5:15 PM, Peter Murray <peter@indexdata.com> wrote:
Hi Lydia,

This is a topic of some discussion among the developers. The current thought is that the FOLIO platform will provide a mechanism for apps to stream transactions out to a SQL database -- perhaps anonymizing and denormalizing the data along the way. It would be up to the module developers to use this mechanism to make transactions available to reporting utilities. Beyond that, the developers haven't specified any needs or requirements. There may be some discussion of refining the requirements and mechanisms at the developers meeting in Dublin next week.

Peter
On May 10, 2017, 11:13 AM -0400, Lydia R. Pettis <lp14@cornell.edu>, wrote:
While it may be premature for us to be looking at this, it would be helpful if an Index Data person could speak briefly to our SIG about reporting tools and this piece of the charge:

“The SIG should examine 3rd party reporting tools such as BIRT and other tools or dashboards that could be integrated into the platform.”

My sense is that we all use different methods of accessing and reporting our data, based largely on our LMS and the skill set of those creating reports. It would be helpful to get a sense of Folio’s vision on this topic.

If someone is available to address this in the next week or two, let me know and I will put you on the agenda.

****************************************************************
Lydia Pettis                                    607-255-9477
Applications Systems Analyst IV
Division for Library Information Technologies (DLIT)
218 Olin Library
Cornell University                       lp14@cornell.edu
Ithaca, NY 14853
****************************************************************
------------------------------------------------------

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> .
------------------------------------------------------

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> .
------------------------------------------------------
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> .

------------------------------------------------------ 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=VV3jVCCAGGO77tIcDTOYv2fPZCg1sAiG. 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> .