Meeting Minutes for 12/09/2020

Discovery Committee Meeting
December 9, 2020
Minutes

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

• Release Notes

Other discussion topics 

• Priority Value Survey(Minute 1:01)
  • Pika Enhancement Value Survey (closed)
  • Description of enhancements and user stories 
  • Clarifications needed
  • Pika staff will be more mindful when writing user stories to be more explicit and explain things better
  • Added in the Last’ Facet Should Work As Designed for All Content
    • The value for some eContent does not have a good value to know when it was added to the catalog for the given added in the last option
  • The user story is trying to explain that the added in the last facet doesn’t always capture values for eContent holdings
    • User lists should be easier to distinguish in search results
    • SD is thinking of having an image or images from the cover art of the first few items in a list so it makes things more explicit so they look like a list
  • When facets have values that mean “no data” in the results they should be combined
    • There are several facets that will have a note “no information is given” or “undefined” or “no data” 
    • This is an attempt to combine any of those values into one entry
  • Create a date facet for the digital archive
    • Currently, we do not have a way to limit by date range in the digital archive for Marmot folks
    • This feature will give people the ability to limit by specific date ranges
  • Make the distinction between abridged and unabridged audiobooks in search results
    • Pascal mentioned that they may add an unabridged facet
  • Implement browse category ownership and sharing options
    • Currently, the way it is set up for widgets is that you only see widgets created for your library or those that are designated for ‘all libraries’
    • With browse categories, you can see, edit, and touch the ones made by all the libraries 
    • Anyone could go in and edit any of the browse categories even though it is not for your library
    • Ashley would like to have them limited to your library much as they do for the widgets where they belong to a library
    • The  “all libraries” could be used by any library
  • Cloud Library API
    • Several discovery partners use Cloud Library so it would be nice to have an API that works like the OverDrive and Hoopla API
  • Create handling for ILS bibs that direct out to external systems
    • Sacramento if a good example of a library that has an external bookings system
    • We want to make sure links that produce buttons in Pika get directed out to the external site
• Discussion of development priorities for the next release (Minute 1:08:52)
  • Road Map (Note: the roadmap has been updated since the meeting)
  • The road map is a more graphical representation of what we have outlined for the three quarters 
  • Marmot wants to make the items they are working on and expectations more accessible to everyone involved
  • The Q4 for 2020, and Q1 - Q3 for 2021 roadmap were discussed
  • Q2 of the previous roadmap and now Q3 of the new roadmap shows a sub-bullet point that will include 3 prioritize user stories 
  • User stories are the outcome of the previous value survey 
• Pika Governance Document is now live (Minute 1:10:34)
  • The document makes sure that feature requests do not get overwhelming so the Pika team can be very responsive to requests  
  • Marmot has stayed true to their member-driven vision and mission by turning those around back to the discovery committee for feedback on the value they have for you 
  • This is why it is so important to fill out the Pika enhancement value survey 
  • This is your voice in the governance of Pika 
  • The governance document was reviewed
• RBdigital to OverDrive process (Minute 1:16:24)
  • Confirm when any RBdigital collections will be moved to OverDrive Advantage accounts
    • eBook/eAudio, Magazines/Zinio, Comics
  • These new additions will affect the size of the catalog that the Pika team is referencing  and automatic processes
  • Contact pika@marmot.org so they can turn off any corresponding RBdigital sideloads 
• Hoopla 2.0 (Minute 1:19:14)
  • Have libraries heard from Hoopla/Midwest about changes to Hoopla?
  • Migrating other collections to Hoopla (e.g. cloud library)
  • Seems like Hoopla might be acting as an aggregator role for lots of eContent 
  • If you have Hoopla or are considering Hoopla the Pika team is curious to know what is being presented to you from Midwest
  • The Pika team will attempt to have a meeting in the new year with some of their developers but in the meantime, the team is in the dark about what is happening with Hoopla
  • Pascal explained that part of the situation is that the way Hoopla works in the Pika catalogs now is that there is a standard collection for everyone with suppression rules
  • The discussion now is about importing titles that would be unique for one library, so Pika would need to work out how to get those special records that are not part of the standard collection into the catalog 
  • Pascal is not sure if their API supports integration for those special records
• Welcoming Delta County Libraries to Marmot (Minute 57:29)
  • Newest Marmot member, go live on Dec. 15th

The next meeting is Tuesday, March 2, 2021