2018-07-09 Reporting SIG notes

Sharon Beltaine

Cornell University

Peter Murray

Index Data

Elizabeth Berney

Duke University

Erin Nettifee

Duke University

Joyce Chapman

Duke University

Karen Newbery

Duke University

Elizabeth Edwards

University of Chicago

Tod Olson

University of Chicago

Claudius Herkt-Januschek

SUB Hamburg

Scott Perry

University of Chicago

Doreen Herold

Lehigh University

Robert Sass

Qulto

Anne L. Highsmith

Texas A&M

Simona Tabacaru

Texas A&M

Vince Bareau

EBSCO

Mark Veksler

EBSCO

Harry Kaplanian

EBSCO

Kevin Walker

The University of Alabama

Ingolf Kuss

hbz

Charlotte Whitt

Index Data

Lina Lakhia

SOAS

Michael Winkler

OLE

Joanne Leary

Cornell University

Uschi Klute

GBV

Michael Patrick

The University of Alabama

Holly Mistlebauer

Cornell University

Assign Notetaker, Take Attendance, Review agenda

Sharon

Today's notetakers: Sharon Beltaine and Holly Mistlebauer

Last week's notetaker: Ingolf Kuss

Gap Analysis

Holly

Holly will report on the results of the Gap Analysis work done last week

Status from weekly OLE Project Report distributed July 6th:

The evaluation of the gap analysis exercise (aka feature prioritization) is in full swing.  Mark Veksler has created a spreadsheet process that uses the responses from the exercise, along with date of implementation, to calculate a priority for each feature. The process then uses the available capacity of each development team to determine if the work required of that team will be able to get done in the period of time it needs to.  Right now we only have a draft version of the spreadsheet because we need to:

• Finish confirming feature prioritization answers from some of the institutions

• Finish addressing “missing” features that were identified by various institutions

• Confirm the capacity of each development team (e.g. how much time each developer is available per week)

After the three items above are taken care of, we will produce an updated version of Mark’s nifty spreadsheet for the product owners to review.  They will look for:

• Estimates that are incorrect (they become more obvious on this spreadsheet, as Holly learned today)

• Features that are planned out of order

When the product owners are done looking at the spreadsheet, it will be available for sharing.  We are already noticing places where we need more developers, so additional resources or shifting of current resources will be necessary.  Work for the Q3 2018 release officially started today, so we need to move quickly so that we are working on the correct features.

NOTES

-Holly to share final gap analysis results next meeting

-plan will be set up to allow for trying different scenarios for Go Live

-data warehouse named a Go Live priority for all institutions except Chalmers (which has a unique implementation)

-"verification that reporting tools work with data warehouse" issue added by Tod and named a Go Live priority by all institutions but Chalmers

Next Steps for External Reports

ALL

Holly will describe the next steps for the "external" (not "in app") reports we have documented in the Reporting SIG Master Spreadsheet. She is working on bringing these reports into the Folio Project JIRA.

• We now have a JIRA project called Reporting

• Holly has added 2 issues

• Plan is to batch reports from Reporting SIG Master Spreadsheet into JIRA

  • First we need to create custom fields in JIRA for unique fields in the spreadsheet

  • Will not batch load in-app reports because they are only in JIRA within the app JIRA project

  • Will try this in test mode first to make sure SIG approves of approach

  • Hopefully won't need spreadsheet anymore after everything is in JIRA–will keep spreadsheet as an archive

NOTES

-general reporting issues (e.g., data warehouse, external reports) will include the label "reporting" and the prefix "REP" in the FOLIO JIRA system

-in app report issues will have the label "appreports" in the FOLIO JIRA system

-to see JIRA reporting issues entered, search on Holly's name as owner

-Holly will enter external reports showing the contact person for each report; contacts will set themselves (or someone else at their institutions) as "Assignee" if they will be generating that report

-If you would like to be a member of the FOLIO Reporting JIRA group, which automatically sets you up to watch all reporting issues (notifications), please send your FOLIO JIRA username to Holly Mistlebauer at HLM7@cornell.edu. Please use "Reporting JIRA" as the subject line in your request.

FOLLOW-UP

Holly has created 6 shared filters (aka queries, reports) in JIRA:

• Reporting: All issues with key "Rep-"    

• Reporting: All issues with label "appreport"

• Reporting: All issues with label of "reporting"    

• Reporting: Open issues with key "Rep-"

• Reporting: Open issues with label "appreport"

• Reporting: Open issues with label "reporting"

To make these 6 shared filters readily accessible when you log into JIRA, please follow these steps:

1. Go to https://folio-org.atlassian.net (if you aren't already logged in to JIRA, use the same login that you use to login to this wiki)

2. Select Manage filters from Issues drop-down menu

3. Click on Search option in the left-hand column

4. Type "Reporting" in the Search box and press the Search button

5. The 6 filters listed above will appear

6. Click on the white star to the left of each filter name, turning the star gray

7. Now when you select the Issues drop-down menu you should see these 6 filters with the FILTERS section, making them easy to find and use

Data Elements for Inventory Application

Anne, Sharon

Review the work currently underway to build a data model for the Inventory application. First implementers are working together to map data elements from their current LMS environments to the new Folio data elements.

Link Your "Yes-In App" Reports

All

(Reminder)

Important Notes to Reporting SIG members:

• If your report is identified as a "Yes - In-App Report": Please drop a copy in the appropriate functional area folder in the Library Stats folder in the Reporting SIG Google Drive folder and link them to the "Link to Sample" column in the Reporting SIG Master Spreadsheet, if you haven' yet. It really helps Product Owners to have a report to view to understand what is needed for a given in app report.

• Please keep track of all the reports you added to the spreadsheet as Product Owners may add questions and remarks to the spreadsheet.

• If you do not agree with a certain report being identified as "No In-App report" please turn to Holly.

Other Topics?

All

Any other topics to discuss today?

Topics for Future Meetings

All

Next week's meeting focus: Reporting Data Element Verification for Inventory Application

Review and update Topics for Future Reporting SIG Meetings