| 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
| |
)