Meeting Minutes for 06/04/2019

Discovery Committee Meeting
June 4, 2019
Minutes

Marmot Users Group (MUG) presentation needs

• Google Analytics by Chris Froese was a suggestion for a MUG presentation.
• Beth and Jesse from Nashville offered to present Material Request handling.
• Last call for Marmot Voting Member presentations, otherwise  Council decided the time will be used for other presentations.
• It was decided that members would prefer to hear about Google Analytics at the Marmot User Group (MUG) conference.

Marmot Council Meeting Recap

• Findings from 360 Evaluation report regarding Pika
  • Marmot did a very through 360 evaluation that was used for evaluating Marmot’s current and past statuses. The data collection for the study was comprised of three intensive data sources:  the library director focus groups; the survey sent to librarians/library staff at Marmot Voting Member libraries; and a very deep examination of historical use, operational, and financial data to identify trends.
    • The 360 evaluation has a lengthy set of findings about the direction for Pika and the concept of Discovery Partners.
    • The study has been concluded, and now have some direction  by Council for Marmot to continue very thoughtful, moderate growth in Discovery Partners.
    • Marmot is reaffirming their commitment to  the development of Pika
    • The deep dive into the tickets to solicit feedback and input on setting priorities for active development of Pika.
    • Marmot will be developing some data elements to find Discovery Partners that are a good fit for the  resources that are available at Marmot.
    • Marmot is excited to bring on a few more Discovery Partners over time.
      • There was a question about how the focus group information was captured, and how that information about the contribution from Discovery Partners evolves into an excitement about   obtaining new Discovery Partners.
        • This was an opportunity to renew the perspective of the voting members around the fact that Discovery Partners bring a lot of good ideas to the Pika community.
        • These good ideas can benefit all libraries that use Pika.
        • The Discovery Partner ideas have reinvigorated the excitement for that level of contribution among the members.
        • The very nature of Pika is that it is an open source system taking the wisdom from all the different libraries who use PIka to continue to improve it.
    • There was a question asked what steps they need to take to insure the feeling that participation is valued by all participants.
      • Marmot will be working on a governance structure for Pika  that helps clarify exactly how future directions for Pika are to be decided.
      • Just a reminder that Marmot at its core is a consortium that serves Colorado libraries, and their voting members are their core constituencies.
      • There was a push on selling Pika outside of Colorado that resulted in more time being spent on implementing new Discovery Partners, than was being spent on tickets, addressing bugs, and feature requests.
      • Marmot is very actively recalibrating that with everyone participating in the Deep Dive.
      • The Deep Dive will make everything more formal by documenting it.
      • Marmot is going to reassert that its primary purpose is to serve the voting members.

Code Contribution guidelines

• Marmot is in the process of figuring out how they can take advantage of the fact the Pika is open source software that resides in GitHub.
• Marmot wanted to open up the possibilities for members of the Pika community to submit code addressing some of the features that they would like to see within Pika.
• Marmot has identified the Pika core functionality priorities that Marmot staff are working on currently.
• Highly desired features that libraries would like to see added to Pika have also been identified.
• if there are certain features that libraries would like to see added earlier than scheduled on the Pika Roadmap, they have the option to be able to develop code for themselves for that functionality.
• This code can be submitted for review by the Software Development team,  for the possibility of it being included in the code base for all libraries.
• The team has developed the guidelines for code submission.
• The code contribution guidelines are a working draft that Marmot would like to open up for feedback to make sure they make sense.
• The guidelines will be revisited at the Discovery Committee meeting in July.
• Any code submission that only benefits one or a few libraries will be not be reviewed or added to the code on a rapid basis.
• Marmot will be focusing on the priorities that have been identified by the team,  members, and the Discovery Partner input.

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

• Release Notes

Discussion of development priorities for the next release

• Road Map

Current Release

• DPLA Feed Improvements
  • Collection of the new analytics data for archive objects
  • By the Spring of 2020 the analytics will have valuable data on the use of the Digital Archives
• Integrate Hoopla API
  • Project is paused due to  issues in this project that need to be addressed
  • The more critical issue is the control of eContent manifestation display
• Aurora Implementation
  • Complete

Next Release

• Sierra API Patron Integration
  • Chris will continue to work on this integration   
  • Use API calls to Sierra for patron transactions
• Sierra API Extract
  • Process where using the extract or MARC data from Sierra and index that data, so you get all near real-time bibliographic data throughout the day
  • The full export every night would no longer be needed
  • LION has been beta testing this for more than a year now
• Horizon ROA Driver
  • Chris will finish up with this project for the self registration and reading history

Next Quarter

• Programming Language Updates
  • Need to work on updating to a new version of PHP for speed and quality
• Control of Econtent Manifestation Display in Search Results and Grouped Work Views
  • The current display is confusing because the primary button is for OverDrive, but there could be other eContent titles that are not showing until the “Show Editions” button is used.
  • The team would like to give Pika Admin the ability to control which eContent collection gets displayed first, and which one has the primary hold button.

Short Term

• Record Grouping Adjustments
  • Will make a change to the grouping formula
• Clean Up Search Bugs
  • These are broken out into the Long Term section
  • Long Term
    • Stability Version - Search: Advanced Search
    • Stability Version - Search: Language
    • Stability Version - Search: Display and Interface
    • Stability Version - Search: Format Determination
    • Stability Version - Record Grouping: Language
    • Stability Version - Record Grouping: Improved handling for grouping category: Movie
    • Stability Version - Record Grouping: New grouping category: Graphic Novel
    • Stability Version - Search: Combo Handling

Other discussion topics

What happening on June 3rd to cause problems for Pika.

• Once a month the Pika team updates Lexile data.
• When the team updated the data to get it ready for deployment, it contained corrupt data that Pascal is trying to learn the specifics of the root issue.
• This corrupt data affected the full indexing for most items on all the sites.
• The Pika team removed the corrupt file and restored the indexes.
• The team is working on making sure this issue never happens again.
• The interim solution is to exclude the Lexile data in the indexing until a solution is found.

Reports from libraries on special projects

• James from Nashville has created a very specific school report for handing out overdue slips
• He will get in touch with Shelly from Mesa County Valley Schools to show her this report

Next Meeting is Tuesday, July 2nd