mirror of
https://gitea.psi.ch/ELOG/elog.git
synced 2026-09-29 04:04:29 +00:00
Removed option for donations
This commit is contained in:
Stefan Ritt
parent
3813dc6605
commit
57a5ea606e
433
doc/index.html
433
doc/index.html
@ -1,228 +1,205 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<HEAD>
|
<HEAD>
|
||||||
<TITLE>The ELOG Home Page</TITLE>
|
<TITLE>The ELOG Home Page</TITLE>
|
||||||
<LINK REV="made" HREF="mailto:fredp@mygale.org">
|
<LINK REV="made" HREF="mailto:fredp@mygale.org">
|
||||||
<META NAME="generator" CONTENT="NoteTab Light 4.86c">
|
<META NAME="generator" CONTENT="NoteTab Light 4.86c">
|
||||||
<META NAME="author" CONTENT="Fred Pacquier">
|
<META NAME="author" CONTENT="Fred Pacquier">
|
||||||
<META NAME="description" CONTENT="Home of the Electronic Logbook (ELOG) package">
|
<META NAME="description" CONTENT="Home of the Electronic Logbook (ELOG) package">
|
||||||
<META NAME="keywords" CONTENT="ELOG MIDAS PSI RITT">
|
<META NAME="keywords" CONTENT="ELOG MIDAS PSI RITT">
|
||||||
<LINK REL="stylesheet" TYPE="text/css" HREF="elog.css">
|
<LINK REL="stylesheet" TYPE="text/css" HREF="elog.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY BGCOLOR="#ffffff" TEXT="#000000" LINK="#0000ff" VLINK="#800080" ALINK="#ff0000">
|
<BODY BGCOLOR="#ffffff" TEXT="#000000" LINK="#0000ff" VLINK="#800080" ALINK="#ff0000">
|
||||||
<div class="title"> The ELOG Home Page </div>
|
<div class="title"> The ELOG Home Page </div>
|
||||||
<p>
|
<p>
|
||||||
<div class="menu"> Site map : [Home]
|
<div class="menu"> Site map : [Home]
|
||||||
[<a class="nav" href="userguide.html">User's Guide</a>]
|
[<a class="nav" href="userguide.html">User's Guide</a>]
|
||||||
[<a class="nav" href="adminguide.html">Administrator's Guide</a>]
|
[<a class="nav" href="adminguide.html">Administrator's Guide</a>]
|
||||||
[<a class="nav" href="faq.html">FAQ</a>]
|
[<a class="nav" href="faq.html">FAQ</a>]
|
||||||
[<a class="nav" href="http://midas.psi.ch/elogs/Forum">Forum</a>]
|
[<a class="nav" href="http://midas.psi.ch/elogs/Forum">Forum</a>]
|
||||||
[<a class="nav" href="wishlist.html">Wishlist</a>]
|
[<a class="nav" href="wishlist.html">Wishlist</a>]
|
||||||
[<a class="nav" href="contrib.html">Contributions</a>]
|
[<a class="nav" href="contrib.html">Contributions</a>]
|
||||||
[<a class="nav" href="http://midas.psi.ch/elogs/Linux%20Demo/">DEMO</a>]
|
[<a class="nav" href="http://midas.psi.ch/elogs/Linux%20Demo/">DEMO</a>]
|
||||||
[<a class="nav" href="download.html">Download</a>]
|
[<a class="nav" href="download.html">Download</a>]
|
||||||
</div>
|
</div>
|
||||||
<p>
|
<p>
|
||||||
<div class="menu"> * this section : [<a class="nav" href="#whatis">What
|
<div class="menu"> * this section : [<a class="nav" href="#whatis">What
|
||||||
is ELOG ?</a>] [<a class="nav" href="#screenshots">Screen shots</a>]
|
is ELOG ?</a>] [<a class="nav" href="#screenshots">Screen shots</a>]
|
||||||
[<a class="nav" href="#usecases">Use cases</a>] [<a class="nav" href="#license">License</a>]
|
[<a class="nav" href="#usecases">Use cases</a>] [<a class="nav" href="#license">License</a>]
|
||||||
[<a class="nav" href="#links">Links</a>] * </div>
|
[<a class="nav" href="#links">Links</a>] * </div>
|
||||||
<P class="Sub">Home of the <i>Electronic Logbook</i> package by <a href="mailto:Stefan.Ritt@psi.ch">
|
<P class="Sub">Home of the <i>Electronic Logbook</i> package by <a href="mailto:Stefan.Ritt@psi.ch">
|
||||||
Stefan Ritt</a></P>
|
Stefan Ritt</a></P>
|
||||||
<div class="version">Current version is : 3.0.0</div>
|
<div class="version">Current version is : 3.0.0</div>
|
||||||
|
|
||||||
<form action="https://www.paypal.com/cgi-bin/webscr" method="post">
|
<hr>
|
||||||
<input type="hidden" name="cmd" value="_donations">
|
<a name="whatis">
|
||||||
<input type="hidden" name="business" value="stefan.ritt@psi.ch">
|
<div class="section"> What is ELOG ? </div>
|
||||||
<input type="hidden" name="item_name" value="ELOG Donation">
|
<p>
|
||||||
<input type="hidden" name="no_shipping" value="1">
|
<b>ELOG</b> is part of a family of applications known as <i><i>weblog</i>s</i>
|
||||||
<input type="hidden" name="no_note" value="1">
|
. Their general purpose is :
|
||||||
<input type="hidden" name="return" value="http://midas.psi.ch/elog/index.html">
|
<p>
|
||||||
<input type="hidden" name="tax" value="0">
|
<ol>
|
||||||
<input type="hidden" name="currency_code" value="EUR">
|
<li>
|
||||||
<input type="hidden" name="lc" value="US">
|
to make it easy for people to put information online in a chronological
|
||||||
<input type="hidden" name="bn" value="PP-DonationsBF">
|
fashion, in the form of short, time-stamped text messages ("entries") with
|
||||||
<input type="image" src="paypalcard.png" border="0" name="submit" alt="Make payments with PayPal - it's fast, free and secure!">
|
optional HTML markup for presentation, and optional file attachments (images,
|
||||||
<img alt="" border="0" src="https://www.paypal.com/en_US/i/scr/pixel.gif width="1" height="1">
|
archives, etc.)
|
||||||
</form>
|
<p></p>
|
||||||
</center>
|
<li>
|
||||||
|
to make it easy for other people to access this information through a Web
|
||||||
<!--
|
interface, browse entries, search, download files, and optionally add, update,
|
||||||
https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=stefan%2eritt%40psi%2ech&item_name=ELOG%20Donation&no_shipping=0&no_note=1&tax=0¤cy_code=EUR&lc=US&bn=PP%2dDonationsBF&charset=UTF%2d8
|
delete or comment on entries.</li>
|
||||||
-->
|
</ol>
|
||||||
<hr>
|
<p>
|
||||||
<a name="whatis">
|
<b>ELOG</b> is a remarkable implementation of a <i>weblog</i>
|
||||||
<div class="section"> What is ELOG ? </div>
|
in at least two respects :
|
||||||
<p>
|
<p>
|
||||||
<b>ELOG</b> is part of a family of applications known as <i><i>weblog</i>s</i>
|
<ul>
|
||||||
. Their general purpose is :
|
<li>
|
||||||
<p>
|
its simplicity of use : you don't need to be a seasoned server operator and/or
|
||||||
<ol>
|
an experimented database administrator to run <b>ELOG</b> ; one executable file
|
||||||
<li>
|
(under Unix or Windows), a simple configuration text file, and it works. No Web
|
||||||
to make it easy for people to put information online in a chronological
|
server or relational database required. It is also easy to translate the
|
||||||
fashion, in the form of short, time-stamped text messages ("entries") with
|
interface to the appropriate language for your users.
|
||||||
optional HTML markup for presentation, and optional file attachments (images,
|
<p></p>
|
||||||
archives, etc.)
|
<li>
|
||||||
<p></p>
|
its versatility : through its single configuration file, <b>ELOG</b> can be
|
||||||
<li>
|
made to display an infinity of variants of the <i>weblog</i> concept. There are
|
||||||
to make it easy for other people to access this information through a Web
|
options for what to display, how to display it, what commands are available and
|
||||||
interface, browse entries, search, download files, and optionally add, update,
|
to whom, access control, etc. Moreover, a single server can host several <i><i>weblog</i>s</i>,
|
||||||
delete or comment on entries.</li>
|
and each <i>weblog</i> can be totally different from the rest.</li>
|
||||||
</ol>
|
</ul>
|
||||||
<p>
|
<p>
|
||||||
<b>ELOG</b> is a remarkable implementation of a <i>weblog</i>
|
<hr>
|
||||||
in at least two respects :
|
<a name="screenshots">
|
||||||
<p>
|
<div class="section"> Screen shots </div>
|
||||||
<ul>
|
<p>
|
||||||
<li>
|
<table border="0" cellpadding="5">
|
||||||
its simplicity of use : you don't need to be a seasoned server operator and/or
|
<tr>
|
||||||
an experimented database administrator to run <b>ELOG</b> ; one executable file
|
<td>
|
||||||
(under Unix or Windows), a simple configuration text file, and it works. No Web
|
<a href="elog.gif"><img border="0" align="top" src="elog_thumb.gif" alt="elog.gif"></a>
|
||||||
server or relational database required. It is also easy to translate the
|
</td>
|
||||||
interface to the appropriate language for your users.
|
<td valign="top">
|
||||||
<p></p>
|
On the left upper panel is a typical logbook page displayed by Netscape
|
||||||
<li>
|
Navigator. Each logbook page can contain attachments in a similar way to
|
||||||
its versatility : through its single configuration file, <b>ELOG</b> can be
|
emails. This makes it possible to store images or text files and retrieve them
|
||||||
made to display an infinity of variants of the <i>weblog</i> concept. There are
|
easily. You could for example attach a sample configuration file which can
|
||||||
options for what to display, how to display it, what commands are available and
|
later be copied to the local machine with the "<I>Save As...</I>" function of
|
||||||
to whom, access control, etc. Moreover, a single server can host several <i><i>weblog</i>s</i>,
|
the Web browser.
|
||||||
and each <i>weblog</i> can be totally different from the rest.</li>
|
<p>
|
||||||
</ul>
|
Several logbooks can be served though a single <b>ELOG</b> server. Each logbook
|
||||||
<p>
|
can use different attributes for its entries. The logbook can then be searched
|
||||||
<hr>
|
using these attributes. The right pane on the left image shows a search for all
|
||||||
<a name="screenshots">
|
entries with attribute "<I>Type</I>" equal to "<I>Configuration</I>
|
||||||
<div class="section"> Screen shots </div>
|
", and the lower pane shows the search result. It is also possible to use
|
||||||
<p>
|
full-text search in attributes and the entry body.
|
||||||
<table border="0" cellpadding="5">
|
<p>
|
||||||
<tr>
|
While logbook entries are usually displayed one entry per page, they can also
|
||||||
<td>
|
be listed consecutively which makes it easy to produce a paper printout of a
|
||||||
<a href="elog.gif"><img border="0" align="top" src="elog_thumb.gif" alt="elog.gif"></a>
|
logbook.
|
||||||
</td>
|
<p>
|
||||||
<td valign="top">
|
Logbook pages can be edited or deleted. This feature can be turned off in the
|
||||||
On the left upper panel is a typical logbook page displayed by Netscape
|
configuration file so that a logbook entries cannot be changed after being
|
||||||
Navigator. Each logbook page can contain attachments in a similar way to
|
submitted.
|
||||||
emails. This makes it possible to store images or text files and retrieve them
|
<p>
|
||||||
easily. You could for example attach a sample configuration file which can
|
An additional feature is the automatic generation of a notification email
|
||||||
later be copied to the local machine with the "<I>Save As...</I>" function of
|
messages based on a certain type or category of a logbook entry.
|
||||||
the Web browser.
|
<p>
|
||||||
<p>
|
Also try out the <b><a href="http://midas.psi.ch/elogs/Linux%20Demo/">online demo</a></b>
|
||||||
Several logbooks can be served though a single <b>ELOG</b> server. Each logbook
|
!</p>
|
||||||
can use different attributes for its entries. The logbook can then be searched
|
</td>
|
||||||
using these attributes. The right pane on the left image shows a search for all
|
</tr>
|
||||||
entries with attribute "<I>Type</I>" equal to "<I>Configuration</I>
|
</table>
|
||||||
", and the lower pane shows the search result. It is also possible to use
|
<p>
|
||||||
full-text search in attributes and the entry body.
|
<hr>
|
||||||
<p>
|
<a name="usecases">
|
||||||
While logbook entries are usually displayed one entry per page, they can also
|
<div class="section"> Use cases </div>
|
||||||
be listed consecutively which makes it easy to produce a paper printout of a
|
<p>
|
||||||
logbook.
|
The features of <b>ELOG</b> make it useful for several applications:
|
||||||
<p>
|
<ul>
|
||||||
Logbook pages can be edited or deleted. This feature can be turned off in the
|
<li>
|
||||||
configuration file so that a logbook entries cannot be changed after being
|
<b>Personal Logbooks</b>. Personal notes can be written into <b>ELOG</b> and
|
||||||
submitted.
|
can then be retrieved from anywhere with a Web browser. This makes it handy for
|
||||||
<p>
|
PC supporters who have to go around in companies or laboratories and don't want
|
||||||
An additional feature is the automatic generation of a notification email
|
to carry their paper logbook with them. The same holds true for people
|
||||||
messages based on a certain type or category of a logbook entry.
|
traveling around a lot. The logbook database consists of plain ASCII files
|
||||||
<p>
|
which can copied easily between different computers to have local access, for
|
||||||
Also try out the <b><a href="http://midas.psi.ch/elogs/Linux%20Demo/">online demo</a></b>
|
example on a notebook with no network connection.
|
||||||
!</p>
|
<p></p>
|
||||||
</td>
|
<li>
|
||||||
</tr>
|
<b>Shared Logbooks</b>. Logbooks can be shared by several people, for reading
|
||||||
</table>
|
and optionally for writing. This way workgroups can share and exchange
|
||||||
<p>
|
information like in a (simplified) news group. This is supported by the <i>Reply</i>
|
||||||
<hr>
|
command in <b>ELOG</b> which creates "<I>threads</I>" of entries. Users can be
|
||||||
<a name="usecases">
|
notified by email when new entries are added to the logbook. Compared to that
|
||||||
<div class="section"> Use cases </div>
|
of a news server, the installation of <b>ELOG</b> is much simpler.
|
||||||
<p>
|
<p></p>
|
||||||
The features of <b>ELOG</b> make it useful for several applications:
|
<li>
|
||||||
<ul>
|
<b>Small Databases</b>. Since arbitrary attributes can be defined for a
|
||||||
<li>
|
logbook, it can be used as a small database with search facilities.
|
||||||
<b>Personal Logbooks</b>. Personal notes can be written into <b>ELOG</b> and
|
<p></p>
|
||||||
can then be retrieved from anywhere with a Web browser. This makes it handy for
|
<li>
|
||||||
PC supporters who have to go around in companies or laboratories and don't want
|
<b>Problem collections</b>. A system can consist of two logbooks, in one of
|
||||||
to carry their paper logbook with them. The same holds true for people
|
which users enter bugs or problems. If someone adds a problem, an email is
|
||||||
traveling around a lot. The logbook database consists of plain ASCII files
|
automatically sent to the administrator, who can then copy the entry to the
|
||||||
which can copied easily between different computers to have local access, for
|
second logbook and add the solution to the problem. Users can then look up all
|
||||||
example on a notebook with no network connection.
|
fixed problems.
|
||||||
<p></p>
|
<p></p>
|
||||||
<li>
|
<li>
|
||||||
<b>Shared Logbooks</b>. Logbooks can be shared by several people, for reading
|
<b>Shift Logbooks</b>. If the <i>Allow delete</i> and <i>Allow edit</i> flags
|
||||||
and optionally for writing. This way workgroups can share and exchange
|
are off, an entry cannot be modified once it's been entered. This can be useful
|
||||||
information like in a (simplified) news group. This is supported by the <i>Reply</i>
|
for shift logbooks for example in accelerator control rooms where each entry
|
||||||
command in <b>ELOG</b> which creates "<I>threads</I>" of entries. Users can be
|
becomes a "<I>document</I>" with a time and author stamp. <b>ELOG</b> was
|
||||||
notified by email when new entries are added to the logbook. Compared to that
|
originally developed as a shift logbook for the <a href="http://pibeta.psi.ch">PiBeta</a>
|
||||||
of a news server, the installation of <b>ELOG</b> is much simpler.
|
and <a href="http://meg.psi.ch">Muegamma</a> particle experiments at <a href="http://www.psi.ch">
|
||||||
<p></p>
|
PSI</a>.
|
||||||
<li>
|
<p></p>
|
||||||
<b>Small Databases</b>. Since arbitrary attributes can be defined for a
|
<li>
|
||||||
logbook, it can be used as a small database with search facilities.
|
<b>File collections</b>. Since files can be attached to <b>ELOG</b> entries,
|
||||||
<p></p>
|
the system can be used to store and retrieve files. This can be used to store
|
||||||
<li>
|
configuration files, which need to be accessible by several people over the
|
||||||
<b>Problem collections</b>. A system can consist of two logbooks, in one of
|
web, or to store images. Since <b>ELOG</b> features an elaborate query
|
||||||
which users enter bugs or problems. If someone adds a problem, an email is
|
facility, entries can be searched for by specifying several categories.</li>
|
||||||
automatically sent to the administrator, who can then copy the entry to the
|
</ul>
|
||||||
second logbook and add the solution to the problem. Users can then look up all
|
<p>
|
||||||
fixed problems.
|
<hr>
|
||||||
<p></p>
|
<a name="license">
|
||||||
<li>
|
<div class="section"> License </div>
|
||||||
<b>Shift Logbooks</b>. If the <i>Allow delete</i> and <i>Allow edit</i> flags
|
<p>
|
||||||
are off, an entry cannot be modified once it's been entered. This can be useful
|
<b>ELOG</b> is released under the <a href="http://www.gnu.org/copyleft/gpl.html">GNU
|
||||||
for shift logbooks for example in accelerator control rooms where each entry
|
Public License</a>
|
||||||
becomes a "<I>document</I>" with a time and author stamp. <b>ELOG</b> was
|
.
|
||||||
originally developed as a shift logbook for the <a href="http://pibeta.psi.ch">PiBeta</a>
|
<p>
|
||||||
and <a href="http://meg.psi.ch">Muegamma</a> particle experiments at <a href="http://www.psi.ch">
|
<hr>
|
||||||
PSI</a>.
|
<a name="credits">
|
||||||
<p></p>
|
<div class="section"> Credits </div>
|
||||||
<li>
|
<p>
|
||||||
<b>File collections</b>. Since files can be attached to <b>ELOG</b> entries,
|
The author would like to give credits to following people:
|
||||||
the system can be used to store and retrieve files. This can be used to store
|
<UL>
|
||||||
configuration files, which need to be accessible by several people over the
|
<LI><a href="mailto:fredp@dial.oleane.com">Fred Pacquier</a> for
|
||||||
web, or to store images. Since <b>ELOG</b> features an elaborate query
|
this Web site and the French translation</LI>
|
||||||
facility, entries can be searched for by specifying several categories.</li>
|
<LI><a href="mailto:roktas@omu.edu.tr">Recai Oktas</a>
|
||||||
</ul>
|
for the Debian package
|
||||||
<p>
|
<LI><a href="mailto:djek@xs4all.nl">djek</a>
|
||||||
<hr>
|
for the Dutch translation
|
||||||
<a name="license">
|
<LI><a href="mailto:Heiko.Scheit@mpi-hd.mpg.de">Heiko Scheit</a>
|
||||||
<div class="section"> License </div>
|
for many bug fixes and fruitful discussions
|
||||||
<p>
|
<LI><a href="mailto:jhcalvo@arnet.com.ar">Julio Calvo</a> for the Spanish
|
||||||
<b>ELOG</b> is released under the <a href="http://www.gnu.org/copyleft/gpl.html">GNU
|
translation</LI>
|
||||||
Public License</a>
|
<LI><a href="mailto:AlberT@SuperAlberT.it">Emiliano 'AlberT' Gabrielli</a></LI> for
|
||||||
.
|
his idea of scaling attached images
|
||||||
<p>
|
</UL>
|
||||||
<hr>
|
<p>
|
||||||
<a name="credits">
|
<hr>
|
||||||
<div class="section"> Credits </div>
|
<a name="links">
|
||||||
<p>
|
<div class="section"> Links </div>
|
||||||
The author would like to give credits to following people:
|
<p>
|
||||||
<UL>
|
If your are reading this documentation from your local <b>ELOG</b> server,
|
||||||
<LI><a href="mailto:fredp@dial.oleane.com">Fred Pacquier</a> for
|
check for updates on the <a href="http://midas.psi.ch/elog/">ELOG Home Page</a>
|
||||||
this Web site and the French translation</LI>
|
.
|
||||||
<LI><a href="mailto:roktas@omu.edu.tr">Recai Oktas</a>
|
<p>
|
||||||
for the Debian package
|
<HR>
|
||||||
<LI><a href="mailto:djek@xs4all.nl">djek</a>
|
<div class="footer"> Content by <a class="nav" href="mailto:Stefan.Ritt@psi.ch">
|
||||||
for the Dutch translation
|
Stefan Ritt</a>, Web pages by <a class="nav" href="mailto:fredp@mygale.org">Fred
|
||||||
<LI><a href="mailto:Heiko.Scheit@mpi-hd.mpg.de">Heiko Scheit</a>
|
Pacquier</a> - last modified on 16/01/2002 </div>
|
||||||
for many bug fixes and fruitful discussions
|
</BODY>
|
||||||
<LI><a href="mailto:jhcalvo@arnet.com.ar">Julio Calvo</a> for the Spanish
|
</HTML>
|
||||||
translation</LI>
|
|
||||||
<LI><a href="mailto:AlberT@SuperAlberT.it">Emiliano 'AlberT' Gabrielli</a></LI> for
|
|
||||||
his idea of scaling attached images
|
|
||||||
</UL>
|
|
||||||
<p>
|
|
||||||
<hr>
|
|
||||||
<a name="links">
|
|
||||||
<div class="section"> Links </div>
|
|
||||||
<p>
|
|
||||||
If your are reading this documentation from your local <b>ELOG</b> server,
|
|
||||||
check for updates on the <a href="http://midas.psi.ch/elog/">ELOG Home Page</a>
|
|
||||||
.
|
|
||||||
<p>
|
|
||||||
See also the <b>ELOG</b> project pages on <a href="http://sourceforge.net/projects/elog">
|
|
||||||
<img align="middle" src="http://sourceforge.net/sflogo.php?group_id=40505&type=1"
|
|
||||||
width="88" height="31" border="0" alt="SourceForge"></a>
|
|
||||||
<p>
|
|
||||||
<HR>
|
|
||||||
<div class="footer"> Content by <a class="nav" href="mailto:Stefan.Ritt@psi.ch">
|
|
||||||
Stefan Ritt</a>, Web pages by <a class="nav" href="mailto:fredp@mygale.org">Fred
|
|
||||||
Pacquier</a> - last modified on 16/01/2002 </div>
|
|
||||||
</BODY>
|
|
||||||
</HTML>
|
|
||||||
|
|||||||
@ -1,209 +0,0 @@
|
|||||||
<HTML>
|
|
||||||
<HEAD>
|
|
||||||
<TITLE>The ELOG Home Page</TITLE>
|
|
||||||
<LINK REV="made" HREF="mailto:fredp@mygale.org">
|
|
||||||
<META NAME="generator" CONTENT="NoteTab Light 4.86c">
|
|
||||||
<META NAME="author" CONTENT="Fred Pacquier">
|
|
||||||
<META NAME="description" CONTENT="Home of the Electronic Logbook (ELOG) package">
|
|
||||||
<META NAME="keywords" CONTENT="ELOG MIDAS PSI RITT">
|
|
||||||
<LINK REL="stylesheet" TYPE="text/css" HREF="elog.css">
|
|
||||||
</HEAD>
|
|
||||||
<BODY BGCOLOR="#ffffff" TEXT="#000000" LINK="#0000ff" VLINK="#800080" ALINK="#ff0000">
|
|
||||||
<div class="title"> The ELOG Home Page </div>
|
|
||||||
<p>
|
|
||||||
<div class="menu"> Site map : [Home]
|
|
||||||
[<a class="nav" href="userguide.html">User's Guide</a>]
|
|
||||||
[<a class="nav" href="adminguide.html">Administrator's Guide</a>]
|
|
||||||
[<a class="nav" href="faq.html">FAQ</a>]
|
|
||||||
[<a class="nav" href="http://midas.psi.ch/elogs/Forum">Forum</a>]
|
|
||||||
[<a class="nav" href="wishlist.html">Wishlist</a>]
|
|
||||||
[<a class="nav" href="contrib.html">Contributions</a>]
|
|
||||||
[<a class="nav" href="http://midas.psi.ch/elogs/Linux%20Demo/">DEMO</a>]
|
|
||||||
[<a class="nav" href="download.html">Download</a>]
|
|
||||||
</div>
|
|
||||||
<p>
|
|
||||||
<div class="menu"> * this section : [<a class="nav" href="#whatis">What
|
|
||||||
is ELOG ?</a>] [<a class="nav" href="#screenshots">Screen shots</a>]
|
|
||||||
[<a class="nav" href="#usecases">Use cases</a>] [<a class="nav" href="#license">License</a>]
|
|
||||||
[<a class="nav" href="#links">Links</a>] * </div>
|
|
||||||
<P class="Sub">Home of the <i>Electronic Logbook</i> package by <a href="mailto:Stefan.Ritt@psi.ch">
|
|
||||||
Stefan Ritt</a></P>
|
|
||||||
<div class="version">Current version is : 3.0.0</div>
|
|
||||||
|
|
||||||
<hr>
|
|
||||||
<a name="whatis">
|
|
||||||
<div class="section"> What is ELOG ? </div>
|
|
||||||
<p>
|
|
||||||
<b>ELOG</b> is part of a family of applications known as <i><i>weblog</i>s</i>
|
|
||||||
. Their general purpose is :
|
|
||||||
<p>
|
|
||||||
<ol>
|
|
||||||
<li>
|
|
||||||
to make it easy for people to put information online in a chronological
|
|
||||||
fashion, in the form of short, time-stamped text messages ("entries") with
|
|
||||||
optional HTML markup for presentation, and optional file attachments (images,
|
|
||||||
archives, etc.)
|
|
||||||
<p></p>
|
|
||||||
<li>
|
|
||||||
to make it easy for other people to access this information through a Web
|
|
||||||
interface, browse entries, search, download files, and optionally add, update,
|
|
||||||
delete or comment on entries.</li>
|
|
||||||
</ol>
|
|
||||||
<p>
|
|
||||||
<b>ELOG</b> is a remarkable implementation of a <i>weblog</i>
|
|
||||||
in at least two respects :
|
|
||||||
<p>
|
|
||||||
<ul>
|
|
||||||
<li>
|
|
||||||
its simplicity of use : you don't need to be a seasoned server operator and/or
|
|
||||||
an experimented database administrator to run <b>ELOG</b> ; one executable file
|
|
||||||
(under Unix or Windows), a simple configuration text file, and it works. No Web
|
|
||||||
server or relational database required. It is also easy to translate the
|
|
||||||
interface to the appropriate language for your users.
|
|
||||||
<p></p>
|
|
||||||
<li>
|
|
||||||
its versatility : through its single configuration file, <b>ELOG</b> can be
|
|
||||||
made to display an infinity of variants of the <i>weblog</i> concept. There are
|
|
||||||
options for what to display, how to display it, what commands are available and
|
|
||||||
to whom, access control, etc. Moreover, a single server can host several <i><i>weblog</i>s</i>,
|
|
||||||
and each <i>weblog</i> can be totally different from the rest.</li>
|
|
||||||
</ul>
|
|
||||||
<p>
|
|
||||||
<hr>
|
|
||||||
<a name="screenshots">
|
|
||||||
<div class="section"> Screen shots </div>
|
|
||||||
<p>
|
|
||||||
<table border="0" cellpadding="5">
|
|
||||||
<tr>
|
|
||||||
<td>
|
|
||||||
<a href="elog.gif"><img border="0" align="top" src="elog_thumb.gif" alt="elog.gif"></a>
|
|
||||||
</td>
|
|
||||||
<td valign="top">
|
|
||||||
On the left upper panel is a typical logbook page displayed by Netscape
|
|
||||||
Navigator. Each logbook page can contain attachments in a similar way to
|
|
||||||
emails. This makes it possible to store images or text files and retrieve them
|
|
||||||
easily. You could for example attach a sample configuration file which can
|
|
||||||
later be copied to the local machine with the "<I>Save As...</I>" function of
|
|
||||||
the Web browser.
|
|
||||||
<p>
|
|
||||||
Several logbooks can be served though a single <b>ELOG</b> server. Each logbook
|
|
||||||
can use different attributes for its entries. The logbook can then be searched
|
|
||||||
using these attributes. The right pane on the left image shows a search for all
|
|
||||||
entries with attribute "<I>Type</I>" equal to "<I>Configuration</I>
|
|
||||||
", and the lower pane shows the search result. It is also possible to use
|
|
||||||
full-text search in attributes and the entry body.
|
|
||||||
<p>
|
|
||||||
While logbook entries are usually displayed one entry per page, they can also
|
|
||||||
be listed consecutively which makes it easy to produce a paper printout of a
|
|
||||||
logbook.
|
|
||||||
<p>
|
|
||||||
Logbook pages can be edited or deleted. This feature can be turned off in the
|
|
||||||
configuration file so that a logbook entries cannot be changed after being
|
|
||||||
submitted.
|
|
||||||
<p>
|
|
||||||
An additional feature is the automatic generation of a notification email
|
|
||||||
messages based on a certain type or category of a logbook entry.
|
|
||||||
<p>
|
|
||||||
Also try out the <b><a href="http://midas.psi.ch/elogs/Linux%20Demo/">online demo</a></b>
|
|
||||||
!</p>
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
</table>
|
|
||||||
<p>
|
|
||||||
<hr>
|
|
||||||
<a name="usecases">
|
|
||||||
<div class="section"> Use cases </div>
|
|
||||||
<p>
|
|
||||||
The features of <b>ELOG</b> make it useful for several applications:
|
|
||||||
<ul>
|
|
||||||
<li>
|
|
||||||
<b>Personal Logbooks</b>. Personal notes can be written into <b>ELOG</b> and
|
|
||||||
can then be retrieved from anywhere with a Web browser. This makes it handy for
|
|
||||||
PC supporters who have to go around in companies or laboratories and don't want
|
|
||||||
to carry their paper logbook with them. The same holds true for people
|
|
||||||
traveling around a lot. The logbook database consists of plain ASCII files
|
|
||||||
which can copied easily between different computers to have local access, for
|
|
||||||
example on a notebook with no network connection.
|
|
||||||
<p></p>
|
|
||||||
<li>
|
|
||||||
<b>Shared Logbooks</b>. Logbooks can be shared by several people, for reading
|
|
||||||
and optionally for writing. This way workgroups can share and exchange
|
|
||||||
information like in a (simplified) news group. This is supported by the <i>Reply</i>
|
|
||||||
command in <b>ELOG</b> which creates "<I>threads</I>" of entries. Users can be
|
|
||||||
notified by email when new entries are added to the logbook. Compared to that
|
|
||||||
of a news server, the installation of <b>ELOG</b> is much simpler.
|
|
||||||
<p></p>
|
|
||||||
<li>
|
|
||||||
<b>Small Databases</b>. Since arbitrary attributes can be defined for a
|
|
||||||
logbook, it can be used as a small database with search facilities.
|
|
||||||
<p></p>
|
|
||||||
<li>
|
|
||||||
<b>Problem collections</b>. A system can consist of two logbooks, in one of
|
|
||||||
which users enter bugs or problems. If someone adds a problem, an email is
|
|
||||||
automatically sent to the administrator, who can then copy the entry to the
|
|
||||||
second logbook and add the solution to the problem. Users can then look up all
|
|
||||||
fixed problems.
|
|
||||||
<p></p>
|
|
||||||
<li>
|
|
||||||
<b>Shift Logbooks</b>. If the <i>Allow delete</i> and <i>Allow edit</i> flags
|
|
||||||
are off, an entry cannot be modified once it's been entered. This can be useful
|
|
||||||
for shift logbooks for example in accelerator control rooms where each entry
|
|
||||||
becomes a "<I>document</I>" with a time and author stamp. <b>ELOG</b> was
|
|
||||||
originally developed as a shift logbook for the <a href="http://pibeta.psi.ch">PiBeta</a>
|
|
||||||
and <a href="http://meg.psi.ch">Muegamma</a> particle experiments at <a href="http://www.psi.ch">
|
|
||||||
PSI</a>.
|
|
||||||
<p></p>
|
|
||||||
<li>
|
|
||||||
<b>File collections</b>. Since files can be attached to <b>ELOG</b> entries,
|
|
||||||
the system can be used to store and retrieve files. This can be used to store
|
|
||||||
configuration files, which need to be accessible by several people over the
|
|
||||||
web, or to store images. Since <b>ELOG</b> features an elaborate query
|
|
||||||
facility, entries can be searched for by specifying several categories.</li>
|
|
||||||
</ul>
|
|
||||||
<p>
|
|
||||||
<hr>
|
|
||||||
<a name="license">
|
|
||||||
<div class="section"> License </div>
|
|
||||||
<p>
|
|
||||||
<b>ELOG</b> is released under the <a href="http://www.gnu.org/copyleft/gpl.html">GNU
|
|
||||||
Public License</a>
|
|
||||||
.
|
|
||||||
<p>
|
|
||||||
<hr>
|
|
||||||
<a name="credits">
|
|
||||||
<div class="section"> Credits </div>
|
|
||||||
<p>
|
|
||||||
The author would like to give credits to following people:
|
|
||||||
<UL>
|
|
||||||
<LI><a href="mailto:fredp@dial.oleane.com">Fred Pacquier</a> for
|
|
||||||
this Web site and the French translation</LI>
|
|
||||||
<LI><a href="mailto:roktas@omu.edu.tr">Recai Oktas</a>
|
|
||||||
for the Debian package
|
|
||||||
<LI><a href="mailto:djek@xs4all.nl">djek</a>
|
|
||||||
for the Dutch translation
|
|
||||||
<LI><a href="mailto:Heiko.Scheit@mpi-hd.mpg.de">Heiko Scheit</a>
|
|
||||||
for many bug fixes and fruitful discussions
|
|
||||||
<LI><a href="mailto:jhcalvo@arnet.com.ar">Julio Calvo</a> for the Spanish
|
|
||||||
translation</LI>
|
|
||||||
<LI><a href="mailto:AlberT@SuperAlberT.it">Emiliano 'AlberT' Gabrielli</a></LI> for
|
|
||||||
his idea of scaling attached images
|
|
||||||
</UL>
|
|
||||||
<p>
|
|
||||||
<hr>
|
|
||||||
<a name="links">
|
|
||||||
<div class="section"> Links </div>
|
|
||||||
<p>
|
|
||||||
If your are reading this documentation from your local <b>ELOG</b> server,
|
|
||||||
check for updates on the <a href="http://midas.psi.ch/elog/">ELOG Home Page</a>
|
|
||||||
.
|
|
||||||
<p>
|
|
||||||
See also the <b>ELOG</b> project pages on <a href="http://sourceforge.net/projects/elog">
|
|
||||||
<img align="middle" src="http://sourceforge.net/sflogo.php?group_id=40505&type=1"
|
|
||||||
width="88" height="31" border="0" alt="SourceForge"></a>
|
|
||||||
<p>
|
|
||||||
<HR>
|
|
||||||
<div class="footer"> Content by <a class="nav" href="mailto:Stefan.Ritt@psi.ch">
|
|
||||||
Stefan Ritt</a>, Web pages by <a class="nav" href="mailto:fredp@mygale.org">Fred
|
|
||||||
Pacquier</a> - last modified on 16/01/2002 </div>
|
|
||||||
</BODY>
|
|
||||||
</HTML>
|
|
||||||
Loading…
x
Reference in New Issue
Block a user