Meeting Minutes for 10/01/2019

Discovery Committee Meeting
October 1, 2019
Minutes

Demo of new features, bug fixes, and documentation for the upcoming release

• Release Notes

Discussion of development priorities for the next release 

• Road Map

Current Release

• Sierra API Extract
  • Still doing a little cleanup
  • This project is ready to be done
• Google Analytics Upgrade and Enhancements
  • Work is done on this project 
  • Ready for Chris to present at MUG
• Sierra API Patron Integration
  • This is still a work in progress
  • Chris will continue to work on this project
• Montrose - New Marmot Member Implementation
  • After MUG the team will finish the Pika pieces to bring Montrose into Marmot
• Record Grouping Adjustments
  • Specifically working on the language and new grouping  categories first
  • Next, working on other tickets in the grouping project 
  • This project will go to at least the end of the year
• Stability Version - Record Grouping: New grouping categories
• Stability Version - Record Grouping: Language
  • Everything the SD team is working on is based upon getting to the stable build
  • These will not go into Production until SD wrapped up all the changes, because this affects the group work data 
• Virtualize Flatirons Pika server
  • This will be started in October
  • They are virtualizing their ILS at the same time

Next Quarter

• PHP Language Update and PHP 3rd Party Library
  • JB wants to focus on getting the software on the server updated
  • This will take the rest of the year

Other discussion topics

• Lynda.com/LinkedIn Learning
  • Lynda.com was delivering MARC records sets with a simple API to Marmot’s FTP Server
  • New process for libraries continuing this subscription
    • If you are going to continue the service, your Lynda.com records will be set up like a normal sideload 
    • You will have to reach out to them and get records sets
    • You will have to download the records from the vendor and follow the normal sideload procedures
  • According to Nashville, Lynda.com/LinkedIn Learning has apparently put a pause on the transition process for libraries 
    • Addison, Aurora, Flatirons, Arlington received the same message about pausing
    • No other library received the message 
  • Several libraries dropping
    • Flatirons, Sacramento (already dropped), Anne Arundel (already dropped), all Marmot libraries 
  • Action Item: Ashley can reach out to her LinkedIn Learning contact to see if they will continue to deliver the recordsets
• MUG session
  • Earlier in September, a notice was sent out to the Discovery Committee about the PIka Development Priorities survey 
    • The survey was open from September 12 - September 26
    • The individual representatives for each library on the Discovery Committee had a personal link into the survey
    • 43 people received the survey, and there were 33 responses
    • The survey asked about the type of library (public, academic, school), and what type of membership (voting or associate)
    • For each of the functional areas that people were asked to prioritize, they  were sorted by type and membership, and Marmot looked at the average priority rating for each ticket
    • Taking into account all information, Marmot was able to find items that were of high priority for everyone
  • The session at MUG is going to be a further narrowing of the prioritizations ​
    • Out of the 200 backlogged tickets that were put in the potential category, the team narrowed it down to 60 viable ones
    • Based on the survey results, items that had an average priority (for either a voting member or a discovery partner) of either 2 or 3 were considered for prioritization for the Pika Roadmap Prioritization session at MUG
    •  During the MUG session, there will be an activity where participants can determine their investment amount for the items that were in the middle range
    • Marmot will summarize the findings from the MUG session and present it to the committee at the November Discovery Committee meeting
    • The point of this process is to supplement what is stated for the stable release 
    • The Software Development team will attempt to build some of these items into their Sprint planning process throughout the development of the stable build
    • Those that they cannot fit in will have to take priority after the stable build is complete
    • Marmot is targeting Q4 of 2020 for the completion of the stable build
• Record grouping improvement project
  • Pascal is working on record grouping for at least the next three months
  • He does not want to put it into production until they are done with the improvements
  • He will be working on a different branch of code for that period, so they can continue development on other things that can go into the release on the monthly cycle
  • The Marmot test server has been cloned to work on the record grouping changes
  • The new test server will be used to demo the progress they have made on the record grouping and get feedback on those changes
  • They only cloned the Marmot test server and not all the other discovery partners sites, because the algorithms work for everybody, and Marmot has examples of potentially everything they need to fix
  • A month before the release, the changes will be put on all the test sites and let it go into effect at that time
  • Pascal will ask the UCC Dedupe Subcommittee to review the record grouping changes
• Reports from libraries on special projects
  • The Flatirons consortium is virtualizing their servers
  • Liz from Pine River added a widget slider to their homepage
  • Ashley will be doing some Marmot Pika Admin 101 sessions on October 24 and November 7

Next Meeting is Tuesday, November 5th