2017-08-17 Meeting Notes

Owned by Autumn Sunshine (Unlicensed)
Last updated: Aug 17, 2017Version comment
2 min read

Date

17 August 2017

Attendees

 

 

Ground Rules:

  • honor time limits (starting and ending)
  • no interrupting /interject at appropriate times
  • listen and be considerate of all opinions
  • be present (limit device distraction)
  • no disruptive side conversations
  • shared responsibility for LEAD goals/outcomes

Desired Outcome

  • Set a direction for development of the kiosk app, get the primary features up and running

Discussion Items

TimeItemWhoNotes
15min

General application features

  • UI and Accessibility
  • Adding additional kiosks
    • Client end adding of kiosks (looks like core functionality is added but kind of dead ends)
    • Floor specific slideshow functionality (duplicating the main touch kiosk so we can have a kiosk with the same functionality but a different slideshow)
    • Ability to set collection of slides to run on multiple kiosks (kind of extremely helpful for floor specific content, don't have to manually duplicate slideshow schedule on multiple kiosks)
  • "recurrence" feature for slides e.g. display a slide for 1 week every 6 weeks starting on August 17th 2017 (Autumn's personal usability enhancement request (smile))
  • Scale-able to portrait mode?
  • app knows there's more than one kiosk but no front
  • would be lots of work to duplicate
10min?

PC requirements

    • Browser clear cookies every couple minutes?
    • Auto update
    • routine restarts
    • limited patron access
    • no browser history (issue with kiosk root left logged in!)
    • Out of memory (no)
    • Software keyboards!
    • accessability (screen reader/high contrast/zoom
  
25min +

Primary features for this project's goals

  • LibNav map
    • ETS progress update
    • Timetable for getting client end data entry (room 'blobs') up and getting the map up live
  • Primo integration
    • How to get it in the kiosk app
    • Maintaining patron privacy
      • Browser clear cookies every couple minutes?
    • That pesky keyboard question
      • Patron access physical keyboard
      • in web app
      • on pc hardware (can we find a restricted software keyboard? It looks like the windows 10 keyboard is already pretty limited with no function keys if we don't allow users to access system settings and turn them on)
      • ease of use (Android style swipe, iOS style autocomplete, voice recognition?)
      • Accessibility
    • Zooming
    • We can make a stripped down version of primo that only searches OSU
  • Interoperability of LibNav and Primo
    • Linking of Primo into Libnav map
      • Can we just allow LibNav to popup in the Primo iframe?
  • ILL?
  • on hold while working on scholors archive
  • still need fix for time and date issue
  • lump everything together
  • need a firm timeline
  • create tickets in osu libraries (for ETS)
  • Email library tech
  • Autumn will email bugs and feature requests
  • Primo top priority
  • Patron logon not practical
  • Keyboard
    • kiosk pc software keyboard a possibility
  • still have to think about patron logon for room reservations, was done/can be done with authentication and no login
  • LibNav is a good foundation, very breakable
  • not fair to cs students to start them on bug fixes not real project
  • bug fixes/ time and date, memory
  • set priorities not the kitchen sink
  • libnav sandbox info can be imported into live version
    • try it out
    • are we ok with putting software out with bugs
  • libnav for fall: should we just play with it for now?
  • how do we want to alot developer time after august?
  • libnav separate from kiosks
  • projects to libtech support, will show up in github or sauna

 

 

 
10min

Secondary features (if we have time in this meeting)

  • Room reservations: ETS update
  • Campus resources map
  • Paging or Librarian chat
  

Action Items

  •