Date
Attendees
- E Pennington
- Former user (Deleted)
- Kevin Walker
- Angela Zoss (Old)
- Matthew Harrington
- Roman Ruiz-Esparza
- Nassib Nassar
- lm15@cornell.edu
- Vandana Shah
- Michael Patrick
NOTES
-Establish Naming Conventions for reports and queries
-modularizing queries
-core query to generate 1st stage table
-organization should be simple, clear, and logical
-include date
-use short description focusing on function eg Count Loans for Locations
-information should come from API structure, FOLIO elements
-report: how queries used
-query describes what the query does
-show app name in the report code? eg RA, RM, etc.
-circulation usually refers physical items, and usage usually refers to electronic
Example Circulation Detail Report
Requirements ID: ID401
JIRA Ticket: (REP-103)
Name of Report:
- Circulation Transaction Detail
- Circulation Transactions
- Loans by Material Type
- Circulation Transactions with Bibliographic Detail
- Loans by Material Type with Bibliographic Detail
- Loans with Item Detail
The 5 most used apps of FOLIO that reports will be generated for:
- users
- circulation
- inventory
- finance and orders
- resource management
Upper-level grouping:
- Circulation (use API structure; users, circulation, inventory, finance and orders, resource management)
- maybe this is most readable for non-expert analysts
- Resource Access (stick with current functional areas)
- useful for report development, but maybe not useful for UX; could potentially just include tags on GitHub
-just use functional area to organize reports, not to name them
-use tagging (e.g., in GitHub?) to help organize reports
Report Naming Construct
-
-by = filter or focus
-with = what the report includes, details
Name of Quer(ies):
Short name(s) for queries:
Circulation Detail Report
-counts, aggregation
-detail about function
-cluster report topics; elements in common could be factored into smaller queries
Discussion items
| Item | Notes |
|---|---|
| Attendance | Update Attendee List |
| Action Items | Review and update Action Items |
| Missing and Lost Items | -any updates on this new model from Vandana? |
| Shelf List Location | Eric and Sharon met with Charlotte Whitt about overlaps between REP-189 and UXPROD-892 and UXPROD-880. Charlotte will propose replacing UXPRD-892 and UXPROD-880 with REP-189 to the MM SIG. There are also some follow-up questions for this group on how to deal with Repeating Fields. We need to determine how to address repeating fields in the data model. For example:
Answer: For Repeating Fields the star schema will do a full join for all areas where there are multiple fields; Angela recommends that Eric just note that there will be multiple fields; select based on Item ID |
| Loan and Renewal Count Report Prototype | Kevin will walk us through this new report prototype |
| RPWG Projects | Review RPWG Project List -next priority reports? |
| Circ Item Detail Report Prototype | -Nassib and Roman implementing this data model in the shared LDP data warehouse -latest update on progress from Nassib? |
| DC Meeting Plans | -duplicate report checking -still meet with Reporting SIG -try to meet with POs -Marc in the data warehouse -MM Convener joins to discuss MM reporting |
| For our next meeting... | Next Topics:
Next meeting of the Report Prototype WG is scheduled for Monday, June 10 at 10:00am EST |
Action items
- Angela Zoss (Old) to follow up with Marc Johnson about why dates are stored as strings; dates are not being validated for Service Point Usage data model
- Sharon Markus to set up meeting on data elements for renewal dates