2020-07-28 Meeting notes

Jason: Self hosting at A&M - spending a lot of time on upgrade testing, being able to have a persistent release. Have to reload everything every time right now.  Jason has been submitting JIRAs every release.  A&M loads all of types of data (bib, users, orgs, etc) and runs into issues that DevOps doesn't see.  Yesterday 27 million records loaded in 6.5 hours.   The persistence seems to be getting closer.  An additional challenge for A&M is that we have two separate instances of Voyager (Evans & Medical Sciences Library) that have to be merged when we go on FOLIO.

John- shared A&M's FOLIO plan - have tested Edelweiss & Fameflower - For Edelweiss had an April 2 hands-on session planned for ~35 people Goals - familiarize staff with FOLIO, validate settings, identify workarounds - fell through because of COVID.  Switched to a 2-week online testing environment.  Had a feedback form that fed into a spreadsheet with problems with apps/workflow.

For Fameflower - people were more experienced - this time asked people to comment on all test cases, even the successful ones.  This was part of the official bugfest.  Had fewer people see functionality problems, more cases where we need more training for folks.  Had a lot of issues with calendars, for example.  Have identified that we have internal problems with training and people understanding the settings.

Will start Goldenrod testing in the first two weeks of Sept - dealing with vacations, Sept 1 fiscal year, staff just starting to come back onsite, etc.

Patty - for the issues people can't understand, can you feed that back into bugfest?  That would be helpful information.  AMB - it is being fed back to the project.

Karen - why using PowerPoint to run the test?  John - originally wanted to people run the tests individually and most people understood how to use it.  It was the easiest way to set things up.  AMB - there is a learning curve for TestRails and limited seats

John - have post-test meetings with the functional leads - lots more positive reaction from the testers.  A&M tests a release behind so can get some feedback about known problems.  Still find problems that were missed in bugfest.  Another helpful features of A&M testers is that multiple people will work on a case, highlighting consistent problems (5 people had the same problem with test case x).

Karen - how did you get people to do this?  John- a mix of volunteers and supervisor direction.  Have to remind people that we're not rebuilding Voyager.  Starting to see that some parts of FOLIO are better.

John will share his slides and spreadsheet - attendees were grateful.  You can contact him at jballestro@library.tamu.edu

Kelly, Anya, Beth - support SIG members present today - Support SIG Charge - Support dashboard for issues being experienced by implemented libraries - https://folio-org.atlassian.net/secure/Dashboard.jspa.  P1 - system broken and the institution is working on it - SIG tries to handle P2 & P3 issues and try to get them into the hotfixes.  Have instructions for Production Libraries - How to Report Bugs .  Kelly went through the Bug Reporting Flow Chart.  The notes and discussions will be kept in the JIRA tickets.

AMB - Lehigh reported some data import bugs, did they report it in the right place?