Meeting Minutes for 03/05/2019

Discovery Committee Meeting
March 5, 2019
Minutes

• Software Development (SD) Process 
  • Categorization of tickets
  • Four Categories
    • Priority
    • Potential 
    • Perhaps 
    • Pasture 
• Pika Stable Build Priorities
  • Searching
  • Sierra API
  • Record Grouping
  • eContent Improvements
  • Admin User Improvements
  • Programming Languages Updates on Server
  • Future Version Improvements
    • These improvements are not essential to the Pika Core, but will be nice to have in the next  iteration of the Pika build.
    • Containers: Docker and Kubernetes - will help the SD team to do rapid deployment and singular maintenance.
• Pika Road Map
  • Items the team is currently working on now, and for future releases.
  • The timeline in the future is more vague, because you cannot predict that far into the future. 
  • On the Pika Stable Build Priorities document is a graph under Visualizations that shows a breakdown of the tickets. 
    • Priority - Contributes to the Core of Pika’s function or stability, and is beneficial to the group as a whole
    • Potential - Would be worked on for different versions
    • Perhaps - Good ideas that may not be feasible 
    • Pasture - Requests that are not possible or will not benefit more than one library
    • Moved to done - Finished tickets
    • Won’t Fix - Technically specifications changed, or was not feasible or possible
    • Obsolete - Non-issue to do software upgrades 
    • No Change/Active - It is actively being worked or on in the upcoming road map
  • The road map is the Software Development (SD) team’s effort to stay on track
  • Projects get update in real time
  • SD would like everyone’s input on long term roadmap
    • Want to make sure they are staying on target
    • Satisfying everyone’s wants and needs

• Call for feedback
  • Tickets by Priority spreadsheet with category tabs 
    • Category definitions
  • Please email [email protected] with collected feedback on the Tickets by Priority spreadsheet
  • Week of March 12th, the team will respond to feedback emails
  • Early fall 2019, Software Development hopes to send out a survey to the Discovery Committee to start crafting their road map for the future

• Q: What's Marmot's intention for Discovery Partners into 2020? 
• A: Marmot will maintain full commitment to ongoing support for Discovery Partners into 2020.   The focus on the backlog tickets has been to identify core needs that affect everyone. This is not a Marmot Members vs Discovery Partners and then trying to prioritize a balance between the two. These are items that benefit everyone that makes use of Pika. Marmot spent a good deal of money on the server room specifically for the growth and advancement of Pika. Marmot is still on pause for accepting any new Discovery Partners.

• Q: What commitments has Marmot made to the Software Development (formerly R&D) staff beyond 2019?
• A: Marmot still has one vacant position left after personnel departures. This position has been initially held as vacate, so as they go through the strategic planning process they can determine where that position would best be suited, and have the most impact within Marmot. As part of the strategic planning process they will put together some scenario based planning activities, and some of those would be identifying trigger points for when Marmot might think of adding other staff member.

• Q: If Nashville (or any other Discovery Partner) manages to complete features (e.g., RBdigital API integration) on our own, is there any commitment from Marmot to evaluate/merge the code?
• A:  Software Development needs to work out the details to find a way to make this happen.

• Q: Is there a commitment to update the full stack? 
• A: Yes, only the PHP was mentioned but there is a need for Mariadb and Solr. The reason PHP and the jQuery were mentioned  is because with PHP they are still back porting security patches, so these are the critical ones Marmot wants to do first.

• Q: Could you explain the card for onboarding a new team member?
• A: That card was meant for Chris to get him familiar with the Pika code.  Chris was given certain tasks as part of the project to help him explore the Pika software.  The onboarding a new team member project ticket is obsolete, but the tickets within the project are not obsolete, they have been recategorized.

• Release Notes

• Sideloads can now handle .csv files for record deletions
  • Special notes 
    • The record number ID field (whatever field it lives in) MUST be a field in the .csv file used for deletion
      • This is not the group work view
    • When you look at a specific bib view in the URL you see your site name, the sideload name, the last piece is the record number ID
      • Example - https://cmc.marmot.org/DocuseekCMC/doc00000502
    • Another way to find the record number ID is under the Staff View.  It is usually listed under the 001.

​

• The Record number IDs needs  to be saved in a .csv file (comma separated values)
  • Make sure each record number ID is on a single line

• AspenCat Migration
  • Complete
• Sacramento Discovery Partner Implementation
  • On going issues 
• New Team Member Onboard
  • Complete
• Bemis Library Marmot Implementation
  • Complete

• Aurora Implementation
  • The team started implementation 
• Integrate Hoopla API
  • Work on the indexing part that was not finished 
• Planning on working towards the full integration by the next release