a b c d e f g h i j k l m n o p q r s t u v w x y z
Description: Logbook system to manage notes through a Web interface
The Electronic Logbook (ELOG) provides a Web interface to manage notes. Its
general purpose is to make it easy for people to put and access information
online; in the form of short, time stamped text messages with optional HTML
markup for presentation, and optional file attachments. ELOG has its own
daemon, there is no need for a full-fledged server (e.g. Apache). It stores
notes as simple as plain text; no special formatting. Its features:
.
* Personal logbooks: Personal notes can be written into ELOG and can then be
retrieved from anywhere with a Web browser.
* Shared logbooks: Logbooks can be shared by several people, for reading and
optionally for writing. Workgroups can share and exchange information like
in a (simplified) news group.
* Small databases: Since arbitrary attributes can be defined for a logbook,
it can be used as a small database with search facilities.
* Problem collections: A system can consist of two logbooks, in one of which
users enter bugs or problems. Whenever someone adds a problem, an email is
automatically sent to the administrator.
* Shift logbooks: If the Allow delete and Allow edit flags are off, an entry
cannot be modified once it's been entered. This can be useful for shift
logbooks for example in Physics experiments where each entry becomes a
"document" with a time and author stamp.
* File collections: Since files can be attached to ELOG entries, the system
can be used to store and retrieve files.
.
Homepage: http://midas.psi.ch/elog
Description: Logbook system to manage notes through a Web interface
The Electronic Logbook (ELOG) provides a Web interface to manage notes. Its
general purpose is to make it easy for people to put and access information
online; in the form of short, time stamped text messages with optional HTML
markup for presentation, and optional file attachments. Its features
include:
.
* Has its own daemon, no need for a full-fledged server (e.g. Apache).
* Being a Web application, search, browse and edit notes from anywhere.
* Includes a tool to create and access notes from the command line.
* Stores notes as simple as plain text; no special formatting.
* Uses customizable mail-like headers (RFC 2822) to categorize the notes.
* Supports RSS feeds for entries.
* Exports to CSV (comma-separated-values).
* File attachments (e.g. images, archives).
* Supports workgroups, shared logbooks.
* Message threads, mail notifications for a forum-like usage.
* Hosts one or more logbooks stored in separate sections on the host.
* Remotely clone logbooks on separate servers.
--- 16966 Thu Jan 1 00:00:00 1970
+++ 2177 Thu Jan 1 00:00:00 1970
@@ -2,25 +2,18 @@
The Electronic Logbook (ELOG) provides a Web interface to manage notes. Its
general purpose is to make it easy for people to put and access information
online; in the form of short, time stamped text messages with optional HTML
- markup for presentation, and optional file attachments. ELOG has its own
- daemon, there is no need for a full-fledged server (e.g. Apache). It stores
- notes as simple as plain text; no special formatting. Its features:
+ markup for presentation, and optional file attachments. Its features
+ include:
.
- * Personal logbooks: Personal notes can be written into ELOG and can then be
+ * Has its own daemon, no need for a full-fledged server (e.g. Apache).
- retrieved from anywhere with a Web browser.
+ * Being a Web application, search, browse and edit notes from anywhere.
- * Shared logbooks: Logbooks can be shared by several people, for reading and
+ * Includes a tool to create and access notes from the command line.
- optionally for writing. Workgroups can share and exchange information like
+ * Stores notes as simple as plain text; no special formatting.
- in a (simplified) news group.
+ * Uses customizable mail-like headers (RFC 2822) to categorize the notes.
- * Small databases: Since arbitrary attributes can be defined for a logbook,
+ * Supports RSS feeds for entries.
- it can be used as a small database with search facilities.
+ * Exports to CSV (comma-separated-values).
- * Problem collections: A system can consist of two logbooks, in one of which
+ * File attachments (e.g. images, archives).
- users enter bugs or problems. Whenever someone adds a problem, an email is
+ * Supports workgroups, shared logbooks.
- automatically sent to the administrator.
+ * Message threads, mail notifications for a forum-like usage.
- * Shift logbooks: If the Allow delete and Allow edit flags are off, an entry
+ * Hosts one or more logbooks stored in separate sections on the host.
- cannot be modified once it's been entered. This can be useful for shift
+ * Remotely clone logbooks on separate servers.
- logbooks for example in Physics experiments where each entry becomes a
- "document" with a time and author stamp.
- * File collections: Since files can be attached to ELOG entries, the system
- can be used to store and retrieve files.
- .
- Homepage: http://midas.psi.ch/elog