That question screams: please read the manual! Find command: https://elog.psi.ch/elog/userguide.html#browse

It is described in the manual at https://elog.psi.ch/elog/config.html#general

Entries per page = <number>

Funnily the default is "20". I have no idea why you see 6 entries.

This has nothing to do with the ELOG package, but only with your local configuration of that specific logbook.
You should contact your local ELOG administrator.

Or you might want to rephrase you question: do you want to have this text added in the text field when selecting the field specifier?
How that can be done depends on your specific configuration. Since you are apparently already using a form in the text field, it might be tricky.

How are we supposed to give you a hint when you don't post your configuration?

Here are the relevant excepts from the documentation:

Subst <attribute> = <string>
When submitting logbook entries, attribute values can be substituted by some text. This text can contain arbitrary fixed text and following values:

• $<attribute>: The entered value of the attribute itself
• $host: The host name where elogd is running
• $remote_host: The host name of the host from with the entry was submitted
• $short_name: The login name (if password file is present)
• $long_name: The full name from the password file for the current user
• $user_email: The email address from the password file for the current user
• $logbook: The name of the current logbook
• $date: The current date, formatted via "Date format"
• $utcdate: The current UTC date (GMT) and time, formatted via "Date format"
• $version: The version of the ELOG server in the form x.y.z
• $revision: The Subversion reversion of the ELOG server as an integer number
• $shell(<command>): <command> gets passed to the operating system shell and the result is taken for substitution.

Execute new | edit | delete = <command>
It is possible to execute a shell command on the server side after a new message has been submitted, edited or deleted. This feature has been used in the past for SMS notifications over a telephone system and for synchrnonization of the ELOG database with an external SQL database. The <command> can contain substitutions similar to the Subst command. In addition the list of all attachments can be referred to via $<attachments>. The text body of the entry can be referred to with $text. It should be noted that only the first 1500 characters of the text can be used, in order not to exceed the limits of the shell. Following (Unix) command writes a notification into some file:

Execute new = echo "New message wiht ID $message id of type $type from $long_name on $remote_host" >> /tmp/elog.log

It should be noted that this feature can impose a security problem. If someone can edit the elogd.cfg through the Config command of elogd, that person can put malicious code into elogd.cfg and execute it. This is even more severe if elogd runs with root privileges. To avoid such problems, the execute facility is disabled in elogd by default and has to be enabled explicitly with the "-x" command line flag. The administrator has to ensure then of course that only trusted people can edit elogd.cfg.

Have fun!

Andreas

I found the most limiting factor of ELOG to be the file access. ELOG stores all entries in files and therefore has a lot of disk access.

We found that an AFS directory for ELOG is unusable. We tried to store our logbooks on NFS, and it was barely usable but slow. Now we use a local disk on the server, that works fine.

If you want to speed up ELOG the best approach is a dedicated server with a local SSD storage.

Yes, you can see that in the logging file, if you turn on logging. You might want to read the manual https://elog.psi.ch/elog/config.html. Here's the relevant excerpt:

• Logfile = <file>
  This option specifies a filename which logs all login/logout activities and successful user connections for logbooks with user level access. The the logging level (see below) is larger than 1, also read and write accesses can be logged.
• Logging level = 1 | 2 | 3
  Specifies the logging level. The higher this value, the more information is logged. Default is 2:
  • 1: Log only logins and logouts
  • 2: Log also write accesses
  • 3: Log also read accesses

That would be a nice feature...

If you are good in parsing HTML you can achieve this feature: when you create a new entry "<elog-URL>?cmd=new", you'll get HTML source code that provides you with all possible attribute choices.

Disclaimer: this only works if you don't use Conditional attributes.