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. 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.
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. Work groups 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.
--- 2177 Thu Jan 1 00:00:00 1970
+++ 226548 Thu Jan 1 00:00:00 1970
@@ -2,18 +2,23 @@
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:
+ 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:
.
- * Has its own daemon, no need for a full-fledged server (e.g. Apache).
+ * Personal logbooks: Personal notes can be written into ELOG and can then be
- * Being a Web application, search, browse and edit notes from anywhere.
+ retrieved from anywhere with a Web browser.
- * Includes a tool to create and access notes from the command line.
+ * Shared logbooks: Logbooks can be shared by several people, for reading and
- * Stores notes as simple as plain text; no special formatting.
+ optionally for writing. Work groups can share and exchange information
- * Uses customizable mail-like headers (RFC 2822) to categorize the notes.
+ like in a (simplified) news group.
- * Supports RSS feeds for entries.
+ * Small databases: Since arbitrary attributes can be defined for a logbook,
- * Exports to CSV (comma-separated-values).
+ it can be used as a small database with search facilities.
- * File attachments (e.g. images, archives).
+ * Problem collections: A system can consist of two logbooks, in one of which
- * Supports workgroups, shared logbooks.
+ users enter bugs or problems. Whenever someone adds a problem, an email
- * Message threads, mail notifications for a forum-like usage.
+ is automatically sent to the administrator.
- * Hosts one or more logbooks stored in separate sections on the host.
+ * Shift logbooks: If the Allow delete and Allow edit flags are off, an entry
- * Remotely clone logbooks on separate servers.
+ 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.