this elog gives errors sending mail through PSI email server. (did not capture the error messages, sorry). K.O.

I have to import a csv with a date field, which represents the creation date

this date should be used as "date" timestamp which is set automatically, otherwise all entries get the current datetime as timestamp

Thanks

what is the format of the Date field in the csv file ?

My Date is date and not datetime. 

I came accross the admin guide and I was reading / searching for a way to sync logbooks across sites...
elogd mention "-m" and "-M" ... not elog but elogd... with that description :
synchronize logbook(s) with remote server

Does it sync all logbooks ? is there any examples somewhere or advice ?

Thanks :)

> I came accross the admin guide and I was reading / searching for a way to sync logbooks across sites...
> elogd mention "-m" and "-M" ... not elog but elogd... with that description :
> synchronize logbook(s) with remote server

If you would have followed the shown link to the "elogd.cfg syntax page", you would have found the chapter Mirroring:
https://midas.psi.ch/elog/config.html#mirroring

> Does it sync all logbooks ? 

Not necessarily, but that is the default.

> is there any examples somewhere or advice ?

See above: you'll find examples under #mirroring

> Thanks :)

You're welcome.

I have a little problem with elogd 3.1.0. The problem persists up to the latest ELOG version, even in the
development branch (V3.1.0-8196b81):

When I want to "Submit" a new entry, I get a javascript pop-up that asks me:

_This page is asking you to confirm that you want to leave - data you have entered may not be saved._

with the options:
"Stay on page" or "Leave page".

The entry is properly submitted if I agree to "Leave page".
But it is very confusing for my users: they are afraid to loose their entry text.

This problem only shows for some specific logbook configurations.
Below is a minimal logbook configuration that shows this problem:
if you select "entry = short", the pop-up is shown;
if you select "entry = long", the pop-up is not shown, the entry is created immediately.

Attributes = entry, when
Options entry = short{1}, long
Type when = datetime
{1} Show Attributes Edit = entry


(PS: it took me several hours to boil down my 120 line configuration into four lines :-) )

Thanks for the "boiling-down" of your config file. That helped me to reproduce the error quickly. It only occurs if you have a date/time attribute which is hidden as a conditional attribute. This is a unusual combination, that's why I haven't seen that bug before. Actually some 
JavaScript code checks the validity of the date attribute, but since it is conditionally not there, the JavaScript code crashes, which triggers the dialog box you see. It's now fixed in the repository.

/Stefan


> I have a little problem with elogd 3.1.0. The problem persists up to the latest ELOG version, even in the
> development branch (V3.1.0-8196b81):
> 
> When I want to "Submit" a new entry, I get a javascript pop-up that asks me:
> 
> _This page is asking you to confirm that you want to leave - data you have entered may not be saved._
> 
> with the options:
> "Stay on page" or "Leave page".
> 
> The entry is properly submitted if I agree to "Leave page".
> But it is very confusing for my users: they are afraid to loose their entry text.
> 
> This problem only shows for some specific logbook configurations.
> Below is a minimal logbook configuration that shows this problem:
> if you select "entry = short", the pop-up is shown;
> if you select "entry = long", the pop-up is not shown, the entry is created immediately.
> 
> Attributes = entry, when
> Options entry = short{1}, long
> Type when = datetime
> {1} Show Attributes Edit = entry
> 
> 
> (PS: it took me several hours to boil down my 120 line configuration into four lines :-) )

> Thanks for the "boiling-down" of your config file. That helped me to reproduce the error quickly. It only occurs if you have a date/time attribute which is hidden as a conditional attribute. This is a unusual combination, that's why I haven't seen that bug before. Actually some 
> JavaScript code checks the validity of the date attribute, but since it is conditionally not there, the JavaScript code crashes, which triggers the dialog box you see. It's now fixed in the repository.
> 
> /Stefan
> 

Thank you Stefan!
That works nicely now.
Apparently it was less work to fix than to isolate it ;-)

Andreas

> Apparently it was less work to fix than to isolate it ;-)

Well, I also spend like an hour on it.

Hey,

I want to submit an entry to elog remotley using the "elog" command. For example:

elog -h elog-server-adress -l EO -a Fill=111

But this does not generate a new entry. Instead the terminal jumps to an empty new line and the command does not respond to any further inputs anymore (CTRL+C to get out). I have to add a message:

elog -h elog-server-adress -l EO -a Fill=111 "test"

also using an empty string does not work:

elog -h elog-server-adress -l EO -a Fill=111 ""

I could add a whitespace as a work-around, but I'm not sure if this is a bug or a feature.

To put this in some context: I want to create entries for certain measurements automatically, where all relevant parameters are already attribute fields. In the usual case the actual message will be empty but might be used if the operator wants to add a note after the meausrement has been done.

The "command does not respond" means that the program starts reading in the main message text from the console. You can type several lines of text, and finish it off by hitting Ctrl-D (Ctrl-Z under Windows).

I see your point of having empty texts. Indeed the "" on the command line does not work presently, so you have to add a space as a workaround. I modified the elog code (committeed to bitbucket repository) to accept "" as empty text to suit your needs.

/Stefan

Hi Edmund,

Stefan already supplied a fix, but you could as well use a workaround: provide an empty file as text. The following works for Linux:

elog -h elog-server-adress -l EO -a Fill=111 -m /dev/null

We recently tried upgrading the ND280 elog instance to elog 3.1.0. [1] We seem to have some problems with this 'auto-save' functionality.  Specifically, it doesn't seem to play nice with the fact that we prefer to disable user's ability to edit old messages.  So we have (up to now), had the following set of commands specified in elogd.ccfg

Menu commands = List, New, Reply, Delete, Duplicate, Copy to, Move to, Find, Help

The problem is that we now get auto-saved messages, but no ability for the user to actually go back and finish the draft message.  You can see an example of this state in this test elog

http://neut17.triumf.ca:8080/demo/

Clicking on the draft message you can see that it can't be editted.  If you try to click 'new' then edit the draft, you get the message 'Error: Command "Edit" not allowed'.  So we had zombie draft messages, until we added the edit command back; but that defeats our preference that users not mess up old messages.

In general this auto-saving seems like a useful feature.  So the ideal solution for me would be to have some mode where users could edit/finish draft messages, but where we could still disable users from editting completed/finished messages.  Ie, where we can omit 'Edit' from the menu command, but still get auto-save.

A less ideal, but perhaps simpler solution would be that if an elog has omitted 'Edit' from the menu commands, then this auto-save/save functionality is disabled so that we don't get uneditable draft messages.

[1] https://midas.psi.ch/elogs/Forum/67855

Hi Thomas,

Menu commands = List, New, Reply, Delete, Duplicate, Copy to, Move to, Find, Help

The problem is that we now get auto-saved messages, but no ability for the user to actually go back and finish the draft message.  You can see an example of this state in this test elog

Arghhhh! Guess how many people asked me for the autosave feature! I worked really hard on it (including an airplane flight to Japan!), not the next guy comes "can we disable that feature?". 

I agree that this feature has many side effects, and I have to adress one by one, but in the end the community will benefit. Think of starting a draft at one computer, and finishing at another one. Lazarus won't help you there.

Nevertheless , I added a "Save drafts" which you can set to zero. But I would rather prefer if people tell me their problems, and I fix them, instead of siletnly just disabling this feature and keeping the bugs there unresolved.

Oups, now I feel almost a little bit sorry for asking    But thank you anyway!!!

You should see it that way: there are millions of possible applications for a smart electronic logbook like ELOG, and most possible combinations of flags and options will make sense for some of them

I changed the code such that editing of draft messages is always possible, even if the "edit" command is not allowed otherwise. Update is in GIT. Please check if that works at ND280.

Menu commands = List, New, Reply, Delete, Duplicate, Copy to, Move to, Find, Help

The problem is that we now get auto-saved messages, but no ability for the user to actually go back and finish the draft message.  You can see an example of this state in this test elog

Hi again,
Hope I'm not draining to much time from you guys !

here is the scenario (fake one just to understand the logic..):
My main logbook as a Option attribute Called "Electrician availables" 
My second logbook is a list of workers and there capacities Moptions : "Electrician", "Plumber", "Genius"

So my question is:

Is it possible to load my main logbook attribute "Electrician availables" Options based on all the "Electrician" found under my second logbook ?

Thanks :)

> Hi again,
> Hope I'm not draining to much time from you guys !
> 
> here is the scenario (fake one just to understand the logic..):
> My main logbook as a Option attribute Called "Electrician availables" 
> My second logbook is a list of workers and there capacities Moptions : "Electrician", "Plumber", "Genius"
> 
> So my question is:
> 
> Is it possible to load my main logbook attribute "Electrician availables" Options based on all the "Electrician" found under my second logbook ?
> 
> Thanks :)

I think that this is neither possible nor reasonable. Of course everything is possible with shell- and java-scripting, but that would be a software
package on top of ELOG.
Keep in mind we are talking about an electronic logbook here, not about a relational database.

Cheers
Andreas

Good day,

I'm new to Elog and I find it really nice and straight foward...

I still have a few questions that I couldn't address reading the manuals.

-I'm creating a logbook with a lot of attributes. I would like to know if there is a way to name (display) my attribute differently then it's original name. That way I could program $attrib1; $attrib2, etc, and map a name to display the column accordingly... Is it something possible ? 

-Is it possible to hide the field "Entry Time" when creating or editing an entry ?

-I saw the Cell Style fonction to set Color (really nice...), My attribute1 is a worker name; Attribute2 is how the work is going on (stop, ready, in process) I would like to hide Atribute2 in list mode but change Attribute1 cell color based on Attribute2 status... is it possible to do so?

-When using "Show Text = 0" (i'm only using attributes), creating a new entry present the menu "Submit", "Save", "Preview" and "Back".... Pressing "Save" leaves the page, shows "OK with a number" and "Preview" is useless. Is it possible to tune what button should be present or not ? I would like to remove Save and Preview....

For the info, my config file

[GCT]
Theme = default
Show Text = 0
Enable attachments = 0
Show attachments = 0
Use lock = 1
Bottom text = 
Comment = Gestion de la charge de travail
omit email to = 1
Suppress Email to users = 1
Suppress default = 2
Suppress Email on edit = 2
Resubmit default = 2
Enable browsing = 0
Back to main = 1
List after submit = 1
'Mode commands = 0
Menu commands = Select, edit, Delete
List menu commands = Select, New, Find
Attributes = #Réception, #Galée, Infographiste, Traitement, Réviseur, Révision, Contrôleur, Contrôle, Correcteur, Correction, Contrôle final
List display = Edit, #Réception, #Galée, Infographiste, Traitement, Réviseur, Révision, Contrôleur, Contrôle, Correcteur, Correction, Contrôle final
Fixed Attributes Edit = #Réception
Preset #Réception = #####

Format #Réception = 0,attribname,attribvalue,5,5
Format #Galée = 0,attribname,attribvalue,10,10
Format Infographiste = 0,attribname,attribvalue,2,2
Format Réviseur = 0,attribname,attribvalue,2,2
Format Contrôleur = 0,attribname,attribvalue,2,2
Format Correcteur = 0,attribname,attribvalue,2,2

Options Infographiste = ??, ML
Options Réviseur = ??
Options Contrôleur = ??
Options Correcteur = ??

Preset Infographiste = ??
Preset Réviseur = ??
Preset Contrôleur = ??
Preset Correcteur = ??

Extendable options = Infographiste, Réviseur, Contrôleur, Correcteur 

ROptions Traitement = ., En cours, Prêt, Vérification
ROptions Révision = ., En cours, Prêt
ROptions Contrôle = ., En cours, Prêt
ROptions Correction = ., En cours, Prêt
ROptions Contrôle final = ., OK

Cell Style Traitement En cours = background-color:#FF0000 
Cell Style Traitement Prêt = background-color:#33FF33
Cell Style Traitement Vérification = background-color:yellow

Cell Style Révision En cours = background-color:#FF0000 
Cell Style Révision Prêt = background-color:#33FF33
Cell Style Révision Vérification = background-color:yellow

Cell Style Contrôle En cours = background-color:#FF0000 
Cell Style Contrôle Prêt = background-color:#33FF33
Cell Style Contrôle Vérification = background-color:yellow

Cell Style Correction En cours = background-color:#FF0000 
Cell Style Correction Prêt = background-color:#33FF33
Cell Style Correction Vérification = background-color:yellow

Cell Style Contrôle final OK = background-color:#33FF33

Cell Style Contrôle final En cours = background-color:#FF0000 
Cell Style Contrôle final Prêt = background-color:#33FF33
Cell Style Contrôle final Vérification = background-color:yellow

Thanks alot for your help :)

Hi Francois and Andreas,

On Francois' first question, I wonder if Francois is using attrib1, attrib2... as the actual attribute names in the config file.  If this is the case, Francois, you can name attributes with suitable names in the configuration file and dictate which ones appear in the List and Threaded display modes. In the List Display, those names appear along the top row at the top of each column, which I think is what you want. 

This example of three lines in a config file (made up).

Attributes = Worker, System, Organisation, Customer, Status, Ticket

List display = ID, Date, Organisation, Customer, Worker, System, Status, Ticket

Thread display = $Ticket: $Worker. $Organisation / $Customer, ($message id).

In list display, those words ("Organisation", "Customer" etc) are those that appear at the top of each column.  In Thread Display, note how you can use punctuation.  Also (not shown here) you can colour the line in Thread Display depending on the attribute System (which is akin to your question on cell style colouring) a feature not much used in this forum, and the Icon at the beginning of the line depending on the attribute Status. 

This is in the documentation, but perhaps it's not clear to all that - apart from the system defined attributes - any word can be used as an attribute name, and that "attrib1" "attrib2" is just shorthand for "any words you wish to use as attribute names".

Otherwise, if you want a different word along the top if the column in the List Display (and also in the form for making a new entry) for the attribute that appears in that column, why not just use that different word as the name for the attribute?

On the third point, about Cell Style, it would be good for having attrubute 2 able to dictate the colour of the cell of attribute 1, and no need to show attribute 2 in the List Display.  But take your point that it can be done in a shell script.

I only saw Andreas' edited version of the original enquiry, so I didn't see the orignal config file under discussion - so most of my previous entry is totally pointless.  Sorry about that.

Indeed there was a bug when you have "Show Text = 0". I fixed that in the current GIT version. I also hide the "Preview" button if "Show text = 0" since it really makes no sense there. I made a Windows Patch 3.1.0-3 which  ontains this fix.

Wow !!! Im impressed :):):) I didn't expect such a fast reply !!!

Thanks alot Stefan, I will try it right away !!

Andreas, I really like the idea of hiding attrib 1 and attrib2 and fill attrib3 with a script (I guess using elog.exe command line) ?
I play a little with it and I can modify an attribute with the command line but I cant figure how to set the cell style based on the attrib2 and 
replace attrib3 value with attrib1 value... (basicially I need help !!!) do you think you could help me ?

> Wow !!! Im impressed :):):) I didn't expect such a fast reply !!!
> 
> Thanks alot Stefan, I will try it right away !!
> 
> Andreas, I really like the idea of hiding attrib 1 and attrib2 and fill attrib3 with a script (I guess using elog.exe command line) ?
> I play a little with it and I can modify an attribute with the command line but I cant figure how to set the cell style based on the attrib2 and 
> replace attrib3 value with attrib1 value... (basically I need help !!!) do you think you could help me ?

The downside of a script is, that it needs to execute on the server: you need to have the proper syntax for the shell of your operating system.
Here's a little example for a bash shell script, just to give you an idea (that would be for Linux, I have no experience with Windows):

Allow HTML = 1
Attributes =  person, mood, color
Default encoding = 2
Options person = John, Bill, Kate
Options mood = calm, upset
Subst color = $shell(if [ "$mood" == "calm" ] ;then echo "green"; else echo "red";fi)
Change person = <font color="$color">$person</font>
List Change person = <font color="$color">$person</font>
Show Attributes = person, mood
Show Attributes Edit = person, mood
List display = ID, Date, person


Disclaimer: When I've tested it locally the HTML was displayed as source. Stefan, any idea? (ELOG V3.1.0-5be245e)