2016-04-20 Meeting notes - Self-Check Task Force

Owned by Suzanna Conrad (Unlicensed)
Last updated: May 03, 2016
1 min read

Date

Attendees

Goals

  • Establishing goals and scope of the project
  • Finding a regular meeting date
  • Determining best deadlines for deliverables

Discussion items

TimeItemWhoNotes
10minImplementation Survey ResultsSuzanna
  • 13 campuses are not using self-check; San Bernardino is interested in exploring self-check options once live. San Marcos and Sacramento are not using self-check.
  • 3M: 8 including Fresno, Long Beach, Los Angeles, Pomona, San Diego, San Jose (currently), San Francisco, San Luis Obispo
  • TechLogic: 2 including Channel Islands and Monterey Bay
  • Libramation: 1 including Fullerton
    • Special circumstances: San Jose will be moving to Biblioteca in the next 12-18 months; Pomona uses Lyngsoe on an AMH system for check-in
5minFresno's experiences with self-checkRenaldo
  • Setup appears to be vendor agnostic
  • They have to go through stunnel to do the configuration; everything uses SIP2
10minGoals & scope of the projectSuzanna
  • Discussed goals and scope to be posted to Atlassian. Discussed groups with whome we will need to collaborate and discuss (RFID and Access Services Working Group)
5minSurveySuzanna
  • Determined that a survey was appropriate to find out how campuses are using self-check. Suzanna will draft a survey that can be distributed in May.
5minDeadlines for deliverablesSuzanna
  • Discussed deadlines for deliverables.
  • The biggest challenge is testing the configurations at various campuses without knowing when we will have access to our systems – likely we will be able to get certified and test over the summer, then provide documentation by the end of the summer or beginning of the fall.

     

     

Action items