Logbook locking issue, posted by Steve Jones on Tue May 17 21:38:36 2005
|
Stefan, any ideas on this problem?
| Quote: | Our eLog is set to create logbook entry locks and after 30minutes prevent one from re-editing an entry, thus forcing a REPLY to be created.
SCENARIO: When an *attempt* is made to edit a logbook after the 30minute timer, one gets the message that EDITING is prevented and to use the browser "Back" button.
PROBLEM: The display now shows that particular entry to be locked, even though the attempt to edit was blocked. It appears that the lock flag is set prior to the "Edit" attempt being blocked and thus the lock flag is never "unset". |
|
Logbook architecture and availability, posted by Frank Baptista on Fri Dec 14 15:46:14 2018
|
I have a setting which makes ELOG a perfect solution, but there's a situation that I'm struggling to get my head around. We have 3 separate laboratories, each one containing a number of temperature chambers, which run almost constantly over a number of shifts. Each temperature chamber has it's own logbook (laptop). So far, pretty simple.
My dilemma is, our network goes down for maintenance/updates (more often than I'd like), but our operation cannot afford to stop during network interruptions.
With that said, I thought about whether I could run a "local" logbook on each laptop/chamber, and somehow mirror the local logbook to the main ELOG server.
Perhaps I'm over-thinking this...do you have any recommendations? |
|
Logbook aliases, posted by Yoshio Imai on Tue Dec 13 10:51:13 2005
|
Hi!
Is it possible to implement aliases for logbooks? We would like to use a new logbook for every beamtime, but many services need to read/write to the respective current beamtime logbook. It would therefore be nice to have logbook "aliases", so that e.g. a "virtual" logbook beam could be defined to be an alias/redirection to the current beamtime logbook, and all services could refer to that one instead of having to be reconfigured for each beamtime.
This could also help to make sure everyone on shift writes the entries to the correct logbook ... 
Yoshio Imai |
Logbook Title bar , posted by nick on Wed Apr 2 16:36:18 2003
|
Is there a way to change the title entry for individual log books, and
forms ive completely rebranded our system but ut stil says ELOG ENTRIES on
the summary screen |
|
Logbook Parser, posted by Alan Grant on Tue Aug 11 00:20:11 2009
|
We are exploring whether it's possible/feasible to import ELog logbooks into a another database for special purposes (plotting/statisical, etc). Target database is TBD (perhaps Access).
Does anyone have or know of a logbook parser program? From cut/pasting into, for example, Excel, it does appear that the data fields are already line-feed delimited so offhand it would seem possible to parse if one really wanted to pursue it.
Regards,
- Alan |
|
Log4j exploit, posted by Alan Grant on Tue Dec 14 19:16:57 2021
|
Is there any potential impact/concern with the Log4j exploit in Elog applications?
|
|
Log Thread Close Automatically, posted by tom on Sat Feb 20 14:57:27 2010
|
If you have a logbook and you create a new entry, is it possible to put a time limit on that new entry so that edits/replies are only valid for certain amount of time. I am looking for a way that would allow me to have a user start a new message, but after 8 hours, that message becomes locked and no one can edit or add to the message. This is for some shift work and we do not want users to go back after their shift and edit the messages. |
|
Locking the Text field, posted by Todd Corsa on Fri Jul 2 22:20:37 2004
|
Is there a way to disable editing of the textarea, but still allow editing
of other fields in the entry? (e.g. Fixed Attributes Edit = Text)
Also, is the data entered in that field accessible through a variable like
$author? I tried $text, but that doesn't seem to work.
Thanks,
-Todd
By the way... Nice work on this. It has a lot of good features. |