2018-09-17 Reporting SIG notes

Duke University

Update on report prototype work to build a data model for the data warehouse environment

Meeting Notes

Joanne provides an overview of current report prototyping activities.

• A sample circulation report has been run, which includes all data elements one would expect in relation to a loan transaction. These data elements were then matched up to the two report prototypes currently in development (Reporting SIG Report Prototyping Sub-group).
  • • So far everything is looking good. Questions remain about the exact meaning of some of the data fields (e.g., "loan status" vs. "action")

This work is not yet complete and will continue.

• Joanne will continue to work with Nassib to flesh out the first two report prototypes
• Nassib notes that many of data elements are not yet fully documented. To assist with this, Sharon recommends that the Reporting SIG invest effort in helping to complete the FOLIO data dictionary

*Note: wishlist tab removed

Holly Mistlebauer will walk us through the upload of our data warehouse report information into the FOLIO JIRA system and the group will discuss JIRA workflow.

Reports from the Reporting SIG Master Spreadsheet (tabs 2-8) have been loaded into the FOLIO Reporting JIRA project as issues.

What you need to know...

• The "Report" column from the Reporting SIG Master Spreadsheet is the "Summary" field in JIRA.  Some "Report" cells were too lengthy–see REP-110 as example.
• If you update the "Report" column in the spreadsheet or the "Summary" field in JIRA, remember to update the other–this is the only place where redundant data exists.
• The "FOLIO JIRA Link(s)" column in the spreadsheet links to the JIRA issue–Holly has updated the import and export tab.  Need help updating other tabs–mapping of report ID to JIRA issue is attached.
  
• Do not change the report ID number.
• Consortia reports have not yet been added–will be this week.
  
• Filters are available for you to view the reporting issues.
• Please follow these instructions for adding a new report.
  
  

*** The links below are for Holly's use during the meeting–you will not have access except for the very last link (Working with workflows) ***

Notifications when issues added, modified, commented on, etc.

• Group created called reporting-notifications

• Customized Notification Scheme created called Reporting Notifications

Let's talk about the workflow (Issues can follow processes that mirror your team's practices. A workflow defines the sequence of steps that an issue will follow, e.g. "In Progress", "Resolved".)

• Could have one workflow for reports and another for other types of work (based on Issue Type--which can be customized too)
• Workflows already available in FOLIO's JIRA (but we can make a new one)
  
• Working with workflows (documentation from vendor)
  

Meeting Notes

Holly details her efforts to submit JIRA tickets for reports found in the Reporting SIG master spreadsheet.

Sharon notes that a review of the workflows associated with report prototyping/testing should be reviewed as Joanne and Nassib move forward to complete their report prototype test cases.

• Workflows in JIRA can be updated, or new workflows created
• Workflows define how JIRA ticket is brought to resolution (i.e., who is involved, and in what order)
• JIRA ticket "reporter" is the person who enters the ticket, while the "assignee" is the developer tasked with creating the underlying report functionality.
  

Sharon goes back through the master spreadsheet, noting the syntax for ID numbers. Asks that SIG members go back through and add their institution's name to the reports they would find useful.

Review and update Topics for Future Reporting SIG Meetings