Welcome to the "Config Examples" logbook. This database contains elogd.cfg 
examples from various users, showing how ELOG can be configured for various 
purposes. Feel free to use these configuration files as a starting point 
for your own logbook.

To enter a new configuration example, you have to register an account on 
the "Forum" logbook, then you can log in with the same username and 
password to this database.

Then you are supposed to upload your "elogd.cfg", but I suggest to first 
rename it locally to "elogd.txt" and then upload it. This way it gets 
automatically displayed below the message body, so people can see the 
message body and the contents of the configuration file at the same time.

If you want to revise your entry at a later time, hit 'edit', delete your 
old attachment, and submit your new 'elogd.txt' file.

• it uses the same password file as the 'forum' logbook
  
• it has a guest menu so that people without an account can read it
  
• the author and email are automatically taken from the password file
  
• a 'last revision' gets updated on each edit
  
• entries can only changed by the origial author ('restrict edit = 1')
  
• no email notification is sent
  

This is the configuration of the 'Demo' logbook coming in the distribution, 
it contains only the most basic options.

This is the configuration of the discussion forum on this server. Special 
things are:

- a guest menu so people without an account can read it
- an entry can only be edited by the original author ('restrict edit = 1')
- the author and email attributes are taken from the password file and
  cannot be changed by the author, thus to make sure who wrote a specific
  entry
- the email notification is sent to all people who registered for it, but
  their email address is not contained in the "To:" field 
  (Omit Email to = 1) so that they don't see each other's email address
  (for security reasons). For the 'from' field in the email, my address
  is used to that people can hit 'reply' on automatic notifications and
  they will reach me.
- The option "Format <attribute>" is used for a compact page display

This is the configuration of the demo database on this server. It is also 
very basic, with a few exceptions:

- no message text is used (show text = 0)
- no attachments are used (enable attachments = 0)
- in the message listing page, only certain attributes are displayed 
  (display search = ...)

This database like implementations work a bit like an Excel worksheet. 
Attributes are displayed in grid table, and one can click on the column 
titles to sort that column.

I made a new CSS file, which simulated 3D cells using different border 
colors for the four sides of each cell. I plan to put this as the new 
default into the distribution. There is also a new ELOG icon. If anyone 
has a better one, please post it here!

The attached test.html (elog:/3) show the different classes in the CSS 
file, thanks to Etienne Van Caille <etienne.vancaillie@mba.be>.

Hier noch eine schön einfache CSS-Datei mit deutschen Kommentaren zur 
Funktion der Objekte. Kann immerhin helfen, um zu verstehen, wo man etwas 
einstellen muss.

sample of standard elog css and class name
http://public.mba.be/demo/elog/elog_test_css.htm

This configuration example shows a few of the newly developed advanced 
options. We use it at our institute as a visitor registration database. 
Before someone from our collaboration visits the institute, she/he has to 
register on this public logbook.

Following advanced functionality is used:

- The arrival and departure dates are attributes of type "date". This way 
a visitor can select the date from the date picker. In addition, the 
entries can be sorted according to the arrival date. Using a quick filter 
on arrival date, one can show the new arrivals for the next week, next 
month and so on. By adding a bookmark to the browser in the form

http://server.domain/Visitor%20Registration/?Arrival+date=7

one can click on that bookmark to see who will come in the upcoming week. 
Using the find page, one can query the database for arbitrary arrival and 
departure dates, like "who was here last year between May and July?".

- The "visitor" and "email" attributes are preset with the name and email 
of the current user. Of course every user has to register on that logbook 
(enabled with "self register = 2")

- The attribute "Home Institute" can be chosen from a list of preset 
institutes. Using the home institute as a conditional attribute, the elogd 
server fills in automatically the fax number of the institute (see the 
list {1},{2}, ...) after it has been selected.

- Email notifications are set up such that on each new registration, an 
email is sent to stefan.ritt@psi.ch, and an email is sent to 
radiation@psi.ch if the check box "Radiation badge" is checked. Please 
change the smtp server host name to make email notifications work.

elog:/1 shows an example entry screen.

The attached simple elogd.cfg implements a personal address book. Since 
version 2.5.2, data can be incorporated into ELOG via the CSV format. This 
way I moved my address data from MS Outlook to ELOG.

The address book is sorted according to the attribute "LastName", and the 
EmailAddress field is converted into a "" link which can be clicked 
to start your email frontend directly. Using the CSV or XML export 
functionality, the address book contents can easily be exported to other 
programs through the "find" page.

This is a typical shift logbook, in this case for an accelerator. It
contains following features:

- public read access
- write access only for registered users
- typical attributes for shift logbook
- author and author email get automatically filled in
- no email notification

This will let you use <site>/elog/ as your URL.

    location /elog/ {
        proxy_pass http://127.0.0.1:8080/;
        proxy_pass_header Set-Cookie;
        proxy_redirect off;
        proxy_set_header Host $host;
    }