diff --git a/doc/userguide.html b/doc/userguide.html index 059b4eaf..c8dd69d3 100755 --- a/doc/userguide.html +++ b/doc/userguide.html @@ -77,11 +77,11 @@ Just to be clear, some definitions of terms that will be used throughout the gui
Usually you will be given a URL (through mail, a Web page etc.) to access the ELOG server.
-If several logbooks are defined on the server, the entry page may be a list of all logbooks, with their descriptions and links to enter the logbook you want to use (this may be disabled). +If several logbooks are defined on the server, the entry page may be a list of all logbooks, with their descriptions, number of entries, and links to enter the logbook you want to use.
Alternatively, you may be taken directly to a specific logbook. By default you will see the latest entry, but the administrator may have defined a different "default view" for the logbook, like the list of the day's entries, or the last 10 entries, etc. (depending on what is most convenient for that logbook's purpose).
-Note : it is generally not recommended to link directly to a specific entry in a logbook by its URL, because under certain circumstances such addresses might change. It is possible to achieve the same result with a "search" URL (see below). +Each entry in a logbook is identified by an unique ID, which is last part of the URL when that message is displayed. This ID might be used to create a bookmark in a browser pointing directly to a specific entry.
There are four ways through which access to a logbook may be controlled : it may be open for all to read ; it may require a common "read" password for all users ; it may require each user to have an individual user account (login name) and password ; finally, access may be granted or not depending on the address of the workstation you are using.
@@ -198,7 +198,7 @@ For the quality of the information committed to the logbook, you need understand