Login user = user1, user2, user3, user4, user5

Deny New = user4, user5
Deny Reply = user4, user5
Deny Duplicate = user4, user5
Deny Edit = user4, user5
Deny Delete = user4, user5
Deny Select = user4, user5
Deny CSV Import = user4, user5

Sorry to bother you. I could see in past Forum entries that the question of  "Simple Math" has come up before, although the answers were not all that simple.

Can you do simple math (i.e. attribute A + attribute B = attribute C) in ELOG ?

Thank you for putting up with my questions.

Mike

No, you can't. The only way is to export a logbook to CSV, then import it in a spreadsheet program, then do the math there. 

 You can pass numerical attributes to an external command via "Execute new =...".  This external command can then do the math and pass the result _back_ to the logbook either as a new entry or as an edit with the command-line client "elog".

For example, given a new entry with (numerical) attributes A and B, if you have

Execute new = add_them.pl $A $B $message id

in your elog.cfg file, then $A and $B will be passed to the add_them.pl perl script.  Now have the perl script (or bc, or whatever you want to use) do the appropriate math and submit the result.  For example, your perl script might include

$C=$A+$B

$D=$A*$B

elog -a C=$C ... -e "$message id" "Sum as edit"

elog -a D=$D ... "Product as new entry"

How do you allow users to change password for a given logbook when the user keeps getting prompted for admin password to enter the change password feature?

I have Allow password change = 1 set global and at each logbook hoping that would work.

It allows them to change the password when and only when the user gets past the admin login when clicking CONFIG.

help

 Thats what we get for having two people working on the install and configuration.  LOL

When first creating and setting up the configs, we had  Admin Password = xxxxx  entered in each logbook config.  Once we created a password list we no longer needed that entry.

This was why each user who had login credentials was being asked to provide the admin password when trying to change their password. 

I didn't get your point completely, so is this issue now resolved? 

 Yes we had listed within each individual logbook config "Admin Password = xxxx".  this was causing the admin login prompt when users wanted to change their own passwords.  The "Admin Password =xxxxx" cannot reside on each logbook config when you use a password list and allow users to change their passwords.

i cannot view images in elog, either as attachments or as icons,

safari 3.2.1 mac os x 10.5.6

Thank you

David

Can you give me some more information? Can you see attachments in the Demo Logbook like here ? What about other browsers? Can you try to start elogd without keep-alives (using the "-k" flag)?

 Hi. I have a same problem... It works well with other browsers, like firefox and internet explorer, but not with safari (with and without keep-alives). 

The demo logbook in the link works fine with safari, though. 

Thanks.

Tsuguo

Thanks for reporting this bug. I finally found the reason and fixed it in revision 2191. I made a new release 2.7.6 which contains all the collected bug fixes from the last few months.

When I try to set

Protect Selection page = 1

in the config file elog crashes. Attached is my config file.

elog 2.7.5 built Apr  8 2009, 16:52:07 revision 130

Actually your combination of "bottom text" with "protect selection page" caused the trouble. If fixed the bug in revision 2189.

Hi guys,

Is there any simple way to export the ELOG data in a more readable way, except copying the .log files????

Thank You in advance,

Urian.

Click on Find, then select Export to: ..., then click Search.  I know it's a bit hidden, but this way one can restrict the subset of entries to be exported.

 but that method does not export all the data, only the subject lines and category etc.

it does not export the body of the threads.

The CSV option does not export the body, since in CSV, only single line items are allowed. But both the XML and the RAW option exports also the body text. 

I'm (ab)using elog as a database and would like to use conditional attributes, like:

Attributes = PC Name, Operating System, Version, Distribution
Options Operating System = Linux{1}, Windows{2}
{1} Show Attributes Edit = Operating System, Distribution, PC Name
{2} Show Attributes Edit = Operating System, PC Name, Version

Problem is that there are several conditions and the list of attributes is rather long. Also, since it's a
rather dynamic environment I have to make new attributes all the time, and adding them to all "show attributes"
 lists is not only tedious, but bound to cause errors as well.
 

So... 

I was thinking, would it be an idea to make the list of attributes to be shown or hidden on a per attribute base.

 

Like:

Attributes = PC Name, Operating System, Version, Distribution

# hide specific attributes
Hide attributes = Distribution, PC Name

# or configure which fields should be shown allways
Show Attributes = Operating System, Version

# add attributes based on OS
Options Operating System = Linux{1}, Windows{2}
{1} Show Attribute Edit = Distribution
{2} Show Attribute Edit = PC Name

(just thinking out loud here).

> I'm (ab)using elog as a database and would like to use conditional attributes, like:
> 
> Attributes = PC Name, Operating System, Version, Distribution
> Options Operating System = Linux{1}, Windows{2}
> {1} Show Attributes Edit = Operating System, Distribution, PC Name
> {2} Show Attributes Edit = Operating System, PC Name, Version
> 
> Problem is that there are several conditions and the list of attributes is rather long. Also, since it's a
> rather dynamic environment I have to make new attributes all the time, and adding them to all "show attributes"
>  lists is not only tedious, but bound to cause errors as well.
>  
> 
> So... 
> 
> I was thinking, would it be an idea to make the list of attributes to be shown or hidden on a per attribute base.
> 
>  
> 
> Like:
> 
> Attributes = PC Name, Operating System, Version, Distribution
> 
> # hide specific attributes
> Hide attributes = Distribution, PC Name
> 
> # or configure which fields should be shown allways
> Show Attributes = Operating System, Version
> 
> # add attributes based on OS
> Options Operating System = Linux{1}, Windows{2}
> {1} Show Attribute Edit = Distribution
> {2} Show Attribute Edit = PC Name
> 
> (just thinking out loud here).

Sure such a think can be implemented, but I have no time right now to do so. I will put it on the wish list.

Hello!

First I would like to thank you for making such a good free software available:). Then right back into the busness. I have a question to developers. I used the following Options to get the logbook entry  which defines the licences expiration date (See the attachement). Now I would like to ask on how to configure eLog to send an e-mail notification when this date is reached?

Attributes = Licence Expiration date
Type Licence Expiration date = date
Date format = %A, %B %d, %Y

The ideal solution would be to have configurable variable which would automatically send a notification X days before the expiration date is reached. Do you think this would be possible feature request to this Forum into eLog wishlist?

BR,

Tero Suominen

That's not possible with ELOG, which is meant as an electronic logbook. You need a calendar application for that. 

 Hi! Thanks for the quick response. Do you have any suggestions on which calendar applications I should start looking for for this purpose?

Thanks,

Tero

You could write a shell script, run it through cron and send mail from that. (even in windows I assume)