2019-04-08 RPWG Meeting notes

Review RPWG Project List

NOTES

-is "filtering" to build out the data elements just for reporting the most efficient way to develop?

-will we develop all 250 reports?

-what scaling can we do at our institutions to support report development

Review FOLIO attributes in the Circ Item Detail Report Prototype

-rename as ID401 Collections Use?

NOTES:

Please take a look at the documentation for API data elements from the eUsage app development team.

eUsage API data elements documentation: 
https://docs.google.com/spreadsheets/d/1CViG0LzMPpN2IVm1EM6vSEzVWnZvUJ0C61YbNP5vexA/edit?usp=sharing

• the "counter-reports" worksheet shows the metadata for the harvested reports.
• for eUsage, we do not actually save the single data fields of each report, but the monthly reports as a whole, with metadata to identify them

eUsage UI presentation:
The eUsage UI design includes a statistics previews backend that queries specific reports (identified by provider, date range, metric type etc.) and then processes the full report

Here is a presentation explaining this design with an example: https://docs.google.com/presentation/d/1r9KWetrYpQFd79j9uDRZkKEbigGp4mOqkh-a3nXJkq0/edit?usp=sharing

Next Topics:

-custom fields?

-how many of the reports do we develop?

-next priority reports?

Next meeting of the Report Prototype WG is scheduled for Monday, April 15 at 10:00am EST