Thanks. I got it working so far. One minor glitch:

I have one topgroup (with 2 subgroups),

  electronics

       trigger

       power

and onother topgroup (only 1 subgroup)

 mechanics

   detector

When I get the login screen for the second (with the only one subgroup) it says in the header:

   "Several logbooks are defined on this host. Please select the one to connect to:"

and below only the one group (detector)  is shown, so actually nothing to select.

This may be possibly achieved by not defining a subgroup for the second one and leaving it as a topgroup,

but I don't know how it behaves, when the group admin decides to create a subgroup. Can he do

without requiring superuser or elog permissions?

--

Christoph

No. You can either search one logbook or all logbooks. There is however the way to have separate groups of logbooks, which are "invisible" from each other. Like running several elogd daemons at the same time. Then your search on all logbooks will only run on the logbooks of one group. Check the documentation for "top groups".

- Stefan

Have a look at "top groups" in the documentation 

Is it possible to have many roots with one elogd (or run several elogds), such that you can seaparate different groups or themes from each other:

electronics

       trigger

       power

mechanics

       detector

       support

Thanks.

Christoph

Is there a way to setup a search, to search several log books but not all the logs books at one time?

Thanks

Carl

Hi,

I'm currently trying to setup a logbook which will contain process descriptions. One of the attributes will be the resists that are used. This could be more than one resist, hence I try to use MOptions but users should also be able to add materials to the selection list. When I write the following, I get some problems though:

Required Attributes = Name, Author, Resists
MOptions Resists =  Nano Copolymer EL-10, S1813
Extendable options = Resists

If a user wants to add a resist, he gets a textbox to add the new resist (which will contain what was already toggled), but there is now way to select also other resists that are already available, without saving the post and than edit it again. Previously selected resists are deselected when a new resist is added (if the user had emptied the textbox) and one can not save the newly added attribute option without saving the whole entry.

Is there a nice way to implement this (am I overlooking an obvious solution), or is this not possible at all. I guess an ideal solution would be to get some sort of ok button when one adds an attribute option and after confirming the new value that one gets back to the checkboxes without exiting the edit mode.

Regards,

Michaël

PS: This is the complete config for this logbook:

Theme = default
Page Title = $logbook - $Name
Edit Page Title = $logbook
Comment = Photolithography Processes

Quick filter = Name, Resists
Preset Author = $long_name
Reverse sort = 1

Attributes = Name, Author, Resists
Sort Attributes = Resists, Name, Author
Required Attributes = Name, Author, Resists
MOptions Resists =  Nano Copolymer EL-10, S1813
Extendable options = Resists
Sort Attribute Options Resists = 1

List display = Name, Author, Resists

If you use an attribute "Entry" then the internal variable "entry time" will expand to the last value of
"$Entry"+" time", e.g. if you use it in "Thread display = $entry time, ..."

One side effect is, that the logbook selection page defaults to use
Last submission = $entry time by $author
Which then expands to an undesired result.

This is not really a bug, rather something you'll need to keep in the back of your mind.

A query to a logbook can crash the demon.

Query:
https://pc8059.psi.ch:444/SwissFEL+Injector/?jcmd=Find&m0a=10&d0a=27&y0a=2011&npp=1&reverse=0

gdb dump:
SSLServer listening on port 444 ...

Program received signal SIGSEGV, Segmentation fault.
show_elog_list (lbs=0xae72618, past_n=0, last_n=0, page_n=0, default_page=1, info=0x0) at src/elogd.c:20797
20797         message_id = msg_list[index].lbs->el_index[msg_list[index].index].message_id;