Starting ELogbook
Always be sure that the Electronic Logbook is up and running when you come on shift. If it isn't running on one of the desktops, you can bring it up by double clicking on the ELogbook icon on the desktop.
The first GUI that comes up asks you for details about connection to the server that holds the ELogbook database. The defaults are normally appropriate. The LAT-BTserver computer serves the MySQL database for the ELogbook. As it turns out, LAT-BTserver is also the machine with the screens, keyboard and mouse, so the ELogbook client can connect to the 'localhost'.
Accessing the Shift Log
Once the connection between client and server is made, another GUI pops up that shows the various kinds of logbooks that can be accessed. For the beam test, the one that will be used most often is the shift logbook. There is a button in the upper right hand corner labeled "Access Shift" that allows you to go to the shift of your choice. By default it goes to the current shift in progress. You can also peruse existing shifts or create future shifts (e.g. to populate the Summary/plan section). After clicking on this button, you can hide the logbook selector GUI.
The Summary/Plan window
The Access Shift button brings up another GUI containing the shift log interface. The Shift Summary/Plan window is used to describe the general shift instructions, goal and plan. It can be modified as many times as necessary. If the goal/plan changes during the course of the shift, this section should be updated.
Making an entry
The Shift Activies section allows you to enter your activities as you go along with taking data, etc. There is a selector that lets you choose in which kind of log book you want to enter your activities. By default, it comes up with Main logbook. For the beam test, the convention is to enter all shift notes into the Main logbook.
Each logbook has three tabs that are labeled Activities, Problems and Other. Most entries should be entered in the Activities tab. If you want to call out special attention to a problem or other issue, you can use the other two tabs. Note that the tab is easily inadvertantly left in the wrong state, thus causing activies you might want to appear in the log in time order to appear in another section. So always be sure that the Activities tab is selected before you start entering an activity.
Sometimes the ELogbook will complain that you're trying to enter an activity in what it considers the wrong shift. You are given the option to either stay with your initial shift or to go to the current shift. Your response will depend on your situation.
ELogbook entries can be modified up to the point that they're exported to the SLAC Oracle database. However, it's best not to modify entries but to correct them with another entry instead. Modifying entries risks dropped information and lost history.
Authentication
Each entry into the Activities, Problems and Other sections is required to be authenticated. After you make an entry, click save. This will bring up the authentication GUI. If you have not yet authenticated, or someone added an entry just before yours, the GUI will not be initialized with your user name. Enter your user name and password (since you'll do this often, I suggest making your password simple). The act of authentication will put your initials near the entry in both the stand alone and the web version of the e-log, so there is no need to do that in the entry as well.
If you don't have a username/password, or your username/password is failing, ask one of the Online people to add one or update it for you. It is better if you don't masquerade as someone else, but acknowledged that it is sometimes unavoidable.
What to enter
During LAT I&T, we found that it is beneficial to make a log entry every time a run is started and another one every time a run completes. Note the run number in both cases and any peculiarities that may have shown up during the run. Also note any other activities like the trigger logic being changed in the NIM bins, that a computer rebooted, that you reset the VME crate, accesses to the cave, beam conditions, communications from (S)PS controls, unusual, or outside of your experience, behaviour (both hardware and software) of any part of the system, etc., etc. When in doubt, log it.