...
Question: do we really need to specific "bibliographic detail" in the report name? Is it reasonable to assume bibliographic data will be included?(extensive discussion
- when is something like that assumed to be in a report, and when does it need to be called out in the name?
- can we just make a general "Loans" report with all of the columns and let people discard columns they don't need later?
- end users would probably be happier with more specific subset reports already created for them; they will want to see both "Loans with Material Type" and "Loans with Service Point", even if at their core they are similar and we could hypothetically create a master "Loans" query with all necessary columns
- going forward, maybe that's how we organize our work on report clusters: create master queries will a large set of columns needed across several reports, then develop queries that build off that query to tailor the results for specific report requests (see workflow below)
Upper-level grouping options:
...
- Issue title should change to the new naming convention
- don't try to create new JIRA projects for the umbrella categories; all dwreport issues stay in REP
- to filter down to reporting umbrella categories, could create a new field ? or just add more tags? (. Solution TBD).
Special cases:
- external reports (e.g., ARL) - the "report" will be a collected set of queries required for external statistics; each of the queries, however, might be useful for other reports
- Question: how does that work with GitHub? If we update the query in one place, do we just have to remember to update it everywhere else it might be used?
...