This user guide is for the Tracer Eyes project. Tracer Eyes is a component of the distributed project code named 'Tracer'. The overall purpose of project Tracer is keep track of ingress and egress of patrons and staff from the library to facilitate the generation of usage reports and if necessary contact tracing lists of everyone ho could have come in contact with individuals infected with the novel corona virus disease 19 (COVID-19).
Tracer Eyes is intended to help staff tasked with greeting/managing the flow of patrons. Its primary role is to provide a quick and seamless system for such staff to log ingress/egress records for all patrons and other staff. The following sections of this guide will be concerned with the Workstation (powering on, logging in, rebooting, etc.), the Application (how to start the Eyes app, basic functionality, how to restart if there are issues), and Failures (which provides further details about handling errors and information about contacting Guy Gastineau).
Welcome to the Workstation
Its real name is 'tracer-eyes', but it is not very particular about what you call it ;)
Most use will only require logging in as the user 'eyes' if the screen locks due to inactivity, but this guide also explains how to power the computer on, how to power it off, and also how to log in.
Access Services Staff
You probably only need the following information for logging back in when the screen locks from inactivity. But you may need to turn it on in the morning or log back in if technical staff needs to reboot it remotely.
User : eyes
Passphrase : tracer eyes
General Information about Workstation
The following provides an extended view into the basic functionality of Workstation
Our robot friend tracer-eyes has the desktop environment KDE Plasma 5 installed.
It gives us a pretty environment and helps us manage graphical applications.
Power Off / Reboot
The EKU Libraries Department of Technology automatically syncs with the workstation after 11:00 PM every night. After syncing tracer-eyes is rebooted. You should never need to turn the workstation off (or on for that matter) during normal circumstances.
Access Services Staff
Once access services staff have logged into the Workstation they can begin using the Eyes application.
Once Eyes is running you will see a white screen with text and sections drawn on it. The sections' format will change as data is written to the screen. Do not be alarmed when the areas resize themselves and affect the layout. The following section outlines the layout.
In summary incoming and outgoing transactions are logged to the top sections of the application. They will expand as they fill with information. If they grow too much you will need the scroll bar to access the 901# entries in the bottom of the app. To avoid cluttering the screen you should use the clear buttons in the lower left quadrant of the application frequently.
Incoming Transactions (top left)
Outgoing Transactions (top right)
Clear Buttons (bottom left)
Patrons by Banner ID (bottom right)
Scrolling (right side)
After the accumulation of many transaction logs in the first row of the window, the scrollbar on the right is likely to become useful. If you find the application in this state, please be nice and clear the transaction boxes with the clear buttons. It will be easier for you and the Workstation to work together in harmony. Currently, there is no functionality to scroll with the center mouse wheel. Guy gives you his deepest apologies for this. It is unlikely to be possible with the current software, but a click-and-drag scrolling feature is on the way.
Here are some more screenshots of the Eyes application in use in my development environment. Expect some more detailed and annotated screenshots in the future.
The components of Tracer Eyes are intended to be a collection of inter-working parts that provide a robust system to help staff log all the ingress/egress of the main library. Sometimes these parts will cease to function as expected. In such cases we can follow some general protocols.