User Tools

Site Tools


evergreen-reports:meetings:2021-05-27

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Last revisionBoth sides next revision
evergreen-reports:meetings:2021-05-27 [2021/05/27 10:42] jventuroevergreen-reports:meetings:2021-05-27 [2021/08/09 11:20] – Add meeting notes jventuro
Line 7: Line 7:
   - Introduction to the Reports Interest Group    - Introduction to the Reports Interest Group 
   - Discussion about Naming of Reports   - Discussion about Naming of Reports
 +    - Bibliomation practices: 
 +      - All templates under one admin user account with a generic name.
 +      - Templates grouped by type in shared holds
 +      - List report templates start with "List of", count report templates start with "Count of"
 +      - Alphanumeric code at end of name - three letters signify the folder it came from (ex. ITC for "Item Count"), number is just a unique number (usually the order that it was added to the folder). Version number follows main number. Example: ITC 004.1
   - Seeing if we can come up with a list of suggestions and best practices when naming reports.   - Seeing if we can come up with a list of suggestions and best practices when naming reports.
-  - Sharing of Reports+      - All consortia/libraries are a little different with their needs, so may not be possible. 
 +  - Sharing of Report Templates 
 +    -  Some templates in breadcrumb format on the wiki
   - Patron privacy and reports   - Patron privacy and reports
-  - Next Meeting date and time.+      - Be careful with what accounts get report access - know that they get access to ALL data 
 +      - Don't email reports with patron data as attachments if you can help it 
 +  - Next Meeting date and time. (TBD) 
 +  - New wishlist items: 
 +      - "Report admin" permission, that would enable direct access to the templates/reports/output of other users (within their scope, etc) 
 +      - A report that puts machine-readable output (json? csv if you must) at a place that another script can harvest 
 +      - Permission to restrict what type of reports a staff member can view and create
  
  
evergreen-reports/meetings/2021-05-27.txt · Last modified: 2022/02/10 13:34 by 127.0.0.1

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.