**Use case list from Janice Nelson**

**25 May 2006**

I have regularly used the SLAC version of the JLAB ELOG for \~2.5 years
now. When I went to make my list of how I use (and would like to use) an
elog, I found that my list is very elog dependent. Basically I use all
of the features available for our elog.

Worried that I was too biased, I made a list of **how I used the old
paper log**:

-   make entry with timestamp (no need for initials because everyone\'s
    handwriting was known)

-   tape in printouts of graphics, tables of info, shift summaries, etc

-   write on the printouts (e.g. an arrow with a note)

-   reference previous entrys by date/time or page number

-   put in start-of-shift sticker and enter information (who was on
    shift, what the plan was, what\'s the current state of the machine,
    etc)

-   draw in little words/pictures that conveyed an emotion or urgency
    associated with an entry (draw a box and some exclamation marks
    around an entry, sad faces, devil faces, frustrated faces, big eye
    for look at this, etc)

Making this list I realized I miss getting to write on printouts and
drawing faces for my entries since the move to elog. Obviously I could
grab the graphics I want to attach, put them in some other program,
write on it, then send the enhanced graphics to the elog. What a pain
though! Perhaps this isn\'t bad as it makes my entries more bland &
professional.

Here\'s the list of **things I do/want to be able to do in an elog**
(this is the list that seems elog-dependent)

-   basic text entry, desireable: fewest mouse clicks and scrolling to
    get the info in

-   text + printout, file or graphic

-   display previous entries. I use the following display options: a
    list of just titles that link to full entry (best for skimming), the
    \"scrollable\" version that is all of the full entries, and the
    individual full entry. Here easy skimming and non-distracting
    formatting is a plus

-   search: date/time, type of entry (by a program or a person), which
    logbook the entry is in . I don\'t search by text often, but if I
    still worked in main control I think I would.

-   auto entries: main control has 3 programs now that do this. I wrote
    my own in matlab a couple years back that everyone in the group
    (myself included) loved.

-   link a new entry to a previous one (like follow-up or re:)

-   supercede - this is my favorite feature -- it doesn\'t delete the
    original entry but lets you write a new entry that the displays will
    show instead of the first if that option is selected. A way to
    delete without deleting (a SLAC-only feature conceived by main
    control ops)

-   event time vs log time - my 2nd favorite feature - enter the time
    the occurrence actually happened in addition to the time the entry
    was made. Then the displays can sort by event time or log time.
    (another SLAC-only feature from the operators)

-   associate an entry with multiple logbooks - easy way to communicate
    info to other groups

-   a web-interface is key. An op also wrote a tk interface that I use
    about 1/3 of the time. I actually like the compactness, ease of use,
    & display on the tk interface more.

**wish list**

-   I\'m tired of having to click the logbook choice box for the 95% of
    the time that it\'s the same one. Maybe a default logbook associated
    with a user? I have this for the Tk interface but not the web
    interface.

-   I would LOVE to be able to send an email and have it automatically
    entered in the elog. Finding the webpage, having to log in and enter
    the info in the right boxes, and clicking the desired logbook seems
    like too much work sometimes (Yes, I\'m pathetically lazy.)

-   more default choices for the displays

Looking at this list now, I think I could do the 2^nd^ and 3^rd^
relatively easily (\<1 wk of work) The first would require a bit more
digging, i.e. it\'s not obvious to me how to start.