Questions
-is there an example of this report somewhere?
(Link to REPORT EXAMPLE)
Report Description
The application that captures eUsage statistics for an institution varies. Some may use the eUsage app, others may use another application.
Description Detail
- This report is modeled on (Cluster), a cluster of ERM reports currently consisting of (REP-XXX, etc.). The purpose of this cluster of reports is to ...
- Have I already paid for serial/journal x?
- How much did serial/journal x cost me in YYYY?
- How much did I pay for my agreements?
Data Attributes
- (high-level list of data fields)
- Data Attributes will come from the following application areas: Orders, Invoices, and Agreements
Report Criteria
- (describe report cluster parameters, criteria, filters, etc.)
Information Resources for Data Attributes
FOLIO Attribute Definition Sources
-See ERM Statistics summary for report descriptions and priority.
Report Criteria
- cost per view of given title
- cost per download of given title
- invoice amount / number of titles = cost per title
- cost per use = cost per title/use of title
FOLIO Attribute Definition Sources
-API reference documentation for all modules located at: https://dev.folio.org/reference/api/
eUsage data attributes???
https://docs.google.com/document/d/1jeFPHIUmRPCAPFpKkciIOBidQbXGBEE-8Fez0vKszrk/edit
-See eUsage: requirements/fields
-See the Finance Data Model
Jira Legacy
See mod-erm-usage in API documentation for FOLIO Attributes
Agreements App- manages packages and titles within packages with connection to Order and Invoice in the Finance App; for ongoing agreements and orders, there will be many invoices, so you may need to look at particular time periods
eUsage app - harvesting counter statistics through SUSHI of downloads and views of given titles; harvest downloads and views from one vendor- Calculate Statistics: Costs Per Download
| Folio Attribute (Module/Path:Object) | Folio Data Element Description | Parameters/Query |
|---|---|---|
...