2024-10-23 Status Meeting

Google Analytics

• Analytics code added to library admin setting. Marmot needs to check if it needs to be put into the config.ini file.

Website updates

• There are a lot of links throughout the pages that currently direct out to the old catalog and bibs therein

  • Explore Kits

  • Book Club Kits

  • Teens page is using the New Items widget – not sure if this is correct or not

• Newly updated search targets are limiting to the storage location because of IP settings

  • Maybe we should remove the IP address for the storage location, since there aren’t OPAC machines that patrons use to browse the catalog?

Email lists

• Discovery committee

• Discovery partners admins

Using the Help Desk

• All service requests for Clearview regarding Pika issues should be entered under the Pika heading

  • Get IT help, etc. are for other services.

• Individuals can be added as participants on service request so more staff get updates

  • We can set some automation where certain individuals are added as participants on all requests submitted by the library

    • This can’t be too complicated as far as a rule goes

  • Beth, Trevor, Brad as participants on all new tickets

• Nearly all incoming communication should be submitted in the help desk

  • We cannot initiate communication out of the help desk, so we may email from time to time

Regular Deployment Cycle

• 4x a year the evening of the Discovery Committee

• Next committee meeting Dec 3rd

Admin permissions

• Having lower level permissions and higher level permissions assigned to the same account causes issues

• Recommendation of having generic Pika accounts that are used by all appropriate staff for certain needs

  • Various List accounts for the given departments e.g. Teens, Adults, etc. with lower level permissions

    • If patron facing lists live with individuals' accounts, other staff users can’t always find them or edit things when they need to.

  • One Pika admin account that’s used by Marmot staff and Clearview staff

Browse category and widget review

• Browse categories are independent of widgets

  • Widget integration is different than assigning browse categories

Browse category bug

• Regardless of permission, browse categories are being assigned to the location with a known network that the user is coming in from

  • User with opacAdmin permission coming in from admin branch assigns the browse category to the admin branch’s location instead of the library system

Safari browser issue

• MHD-6005 and MHD-6008

OverDrive records in Polaris

• Will they be suppressed or deleted?

  • Up for discussion at Clearview collection development meeting

  • Will likely be removed from ILS, but will be a training piece

• Automatically suppressed for Pika with current export

• Overdrive collection makes up a large part of current export which does eat up some processing time

API feature/bug requests for III

• PIN/Password reset

  • The API needs to offer a process by which a patron who has forgotten their password can trigger a reset.

• Retrieve Username

  • The patron set username is not information that is retrieved from the API

• Bib level suppression

  • Bib changed calls should report bibs that have changed the status of IsDisplayInPAC = false, so that 3rd party discovery can suppress records from display.

• For exported MARC and the API

  • Inclusion of item’s creation date.  This would be used to calculate a more meaningful date Added to the index.  (when an item is created is more useful for patrons as the date added field) 

• Patron Authentication

  • When authenticating patrons against the AuthenticatePatron endpoint the AuthExpDate is returned as null. This information would be very helpful for determining the time patron access token can be cached and dramatically decrease the calls being made to the API server.

Scheduling training for Materials Requests

• Likely will go live with this in the new year after discussion with collection development