> Thank you.  I had added the "Move To" and this works at the log entry
level (i.e., "Move
> To <name>) but in the threaded view one does not get the enumerated list
of logbooks.

You get the "Move To" button only after pressing "Select", otherwise it does
not make sense. See attached screendump and config example.

> > Thank you.  I had added the "Move To" and this works at the log entry
> level (i.e., "Move
> > To <name>) but in the threaded view one does not get the enumerated list
> of logbooks.
> 
> You get the "Move To" button only after pressing "Select", otherwise it does
> not make sense. See attached screendump and config example.

Hmmm.  I like the little buttons with the pull-downs for selections. 
Unfortunately, I don't get that.  With a config of:

Find Menu commands = New, Find, Select, Config, Change password, Logout, Help, Admin
Menu commands = Back, New, Edit, Delete, Reply, Find, Move To, Copy To, Config, Help

my screen only shows the "toggle" and "delete" buttons.  Was there a recent rev
that allowed this to happen (I didn't see a comment on this).  

BTW, on a log entry screen, is the appropriate behavior for the "Move To" option
to show multiple "Move To" links (one for each logbook) or should there also be
pulldowns?  

Thanks

Under 2.5.4-2 build1.460, when I edit the demo elogd.cfg the following happens:

- I start with
URL = http://cde-tx32-sds01.subdom.dom.com:8080/

- When I go to edit the global section of the config file, the *display* of
the string is changed to:
URL = <a
href="http://cde-tx32-sds01.subdom.dom.com:8080/">http://cde-tx32-sds01.subdom.dom.com:8080/</a>

- Saving this results in an error in that the rendered url is invalid.

Our current running version is 2.5.4-build1.413 and this behavior is not
evident.  I've looked through the diffs but could not identify the genesis
of this new behavior.

Thanks

I have a question about ELOG. Let's say after the user finishes his shift 
and passess on to the next user on duty. A staff member would want to look 
through the entries and vet them. The staff could lock the entries to 
maintain integrity of the information. How can that be done with ELOG? Can 
you enlighten me. Thank u.

> Hmmm.  I like the little buttons with the pull-downs for selections. 
> Unfortunately, I don't get that.  With a config of:
> 
> Find Menu commands = New, Find, Select, Config, Change password, Logout, Help, Admin
> Menu commands = Back, New, Edit, Delete, Reply, Find, Move To, Copy To, Config, Help

Unfortunately menu commands are case sensitive, so you need a "Move to" instead a "Move
To". I changed this in the code so future versions will not be case sensitive any more.

> BTW, on a log entry screen, is the appropriate behavior for the "Move To" option
> to show multiple "Move To" links (one for each logbook) or should there also be
> pulldowns?  

On the log entry screen, only menu links are possible for internal reasons, that's why I
have chosen that display mode. I agree that it can look clumsy if you have many
logbooks, but there is the "move to = <logbook list>" option to restrict the number of
target logbooks.

This problem has been fixed in revision 1.462

One possibility is to use the option "Restrict edit time = <hours>". This way
an entry can only be edited let's say 8 hours after it has been created.

Another way is to maintain two logbooks, a "scratch" logbook and an "archive"
logbook. Users would put their entries into the scratch logbook, the staff
would examine it and move them to the archive logbook, where all users only
have read access to. To move entries between logbooks, you have to put the
"Move to" command in the configuration file like:

Menu commands = Back, New, Edit, Delete, Reply, Find, Move to, Config, Help

> This problem has been fixed in revision 1.462

Thank you!