2018-10-08 Reporting SIG notes

Duke University

Sharon is currently representing reporting in the Data Migration Subgroup and needs to step back from this role. Is anyone else from the Reporting SIG able to take on this role? If so, please send an email to Sharon Beltaine.

-          The Data Migration Subgroup meetings are held on Mondays at 11:00 am Eastern U.S. time

-          The main activities are to take the data elements from your institution and do data mapping between the FOLIO data elements and your institution’s ILS

-          It helps with understanding FOLIO

-          Interconnection with data warehouse

In order to determine the order in which we will prototype our reports for the development of data models for the data warehouse, we need to prioritize them within each functional area (e.g., RM, RA, etc.). Please see the Prioritizing Reports page in the wiki for detailed instructions.

-As we start building prototypes, it is critical to prioritize our reports

-Reporting SIG representatives  should meet with the reporting groups at their institutions and review each set of reports in order to prioritize them as P1 (for go live), P2 (first quarter after go live), P3 (second quarter after go live), P4 (third quarter after go live) and P5 (fourth quarter after go live).

-Follow the guidelines provided in the “Prioritizing Reports” document.

-Look at data warehouse reports only

-On the Master spreadsheet add your priority in the “Institution Priority” column. Also add your institution symbol, for ex. “P1 – CU” (CU=Cornell University)

-Look at the “In-App Report” column to tell if it’s an in-app report or not. No – means not in-app report, so focus on those

- Prioritize reports within functional areas

We need a target date for completing this project

Initial date suggested was December 3^rd.

-Monday November 12, 2018 is our target completion date

-Reporting SIG members will aim to prioritize the reports within each functional area for their institution by the proposed deadline: November 12, 2018

-On November 12^th we’ll start to look at patterns

- Prioritize the reports listed for your institution and only data warehouse reports

Holly will walk us through the process of assigning ourselves to our reports in the FOLIO JIRA System. Instructions are provided on this wiki page, which will also contain other JIRA info:  Working on a JIRA Issue

-Holly showed the page about “Working on a JIRA Issue”

-It’s only an issue inside of a project

-The page gives an example of what you need to do in order to assign an issue to yourself

-Go to the Reporting Issue project or from using the filters, go to Open Issues. Look for Reporting SIG and put the ID in.

-You can also go to an issue from the Reporting SIG Master spreadsheet. Each report has an ID and a contact person responsible for generating the report for their institution. In the “Folio JIRA Issue(s)” column, there is a link that will take you to the JIRA issue. You can assign the report to you (click on “Assign to me”) or you can enter the name of a person and it gets assigned to them. Hit the check mark.

-You can edit the issue – Click the “Edit” button at the top of the page (you also have the “assign to me” option)

- You can look at the history – what happened to the issue over time

-The assignee can’t close the issue, but can mark it as “in review”. Only the Reporter can close the issue. Sharon and Holy have permission to do anything (back each other up).

Holly has updated the instructions for Reporting JIRA Project Permissions to include the steps for adding the JIRA issue for a new report.  For those of you who are comfortable with JIRA, feel free to add the issue yourself.  Otherwise feel free to contact me and I will add the JIRA issue. 

-First you need to check if there is a report similar to the one you want. If not, go to the bottom of the page, add a new ID number, fill the information, and then in the column “Link to Sample” enter “wishlist”.

- Holly gave us permissions to create JIRA issues. Follow the “strict guidelines”.

Holly created a special JIRA Permission Scheme for our project so that we can adjust the permissions as we see fit.  If you notice any strange behavior, please let Holly know ASAP.  Thanks!

-The assignee will be testing the report. The assignee may or may not be generating the report in the data warehouse. The assignee is responsible for that report. The Reporter will also review the report. Anyone on the Reporting SIG can be assigned as Reporter.

- If more than one institution is listed for the report, the institutions will discuss it among themselves (who tests and takes responsibility for the report).

-Please remember: it's important to update the status of an open issue

-Monday November 12, 2018 is our target completion date

Topics for Future Meetings

Review and update Topics for Future Reporting SIG Meetings