We are using elog to allow users to enter their time spent on a project and we would like them to be able to see the entries that they themselves have

created but not the entries that other users have created.

Thanks,

Herman

 In that case you have to make one logbook per user and restrict the access to it using the "Login user = ..." directive.

 I understand.

Thank you for the quick response.

I am using the CMS ELog remotely as a monitoring tool.  Information is compartementalized into dozens of containers.  I can create a find query URL, say last day, which then reloads every X minutes in Firefox.  When new ELog entries are made, then appear in the refresh and catch my attention.  But, my interests are somewhere between a single logbook and all logbooks.  If I choose all CMS logbooks for example for one day, I usually end up with > 200 entries. 

In short, I would like the ability to:

1) Select from the list of available logbooks when doing a search

2) Have more canned choices from smaller time frames, such as 1 hour or at least one shift (8 hours).

I do not see how to do this in the current elogd.cfg syntax instructions.

Thanks, Alan

 First of all have you considered using the built in RSS feed? With an RSS reader new entries are shown in a local notification box similar to new email. Some people like it.

1) This is not directly possible, but there is a trick: Define a URL to each logbook and put it into the Bookmarks Toolbar of Firefox. If you have many logbooks, this will however clutter up your toolbar. Then I recommend to make a subfolder in the toolbar and put them into it. Now firefox has the neat feature that if you click with the right mouse button on the folder, it offers you "Open All in Tabs". If you select this, you get a tab for each logbook in fireforx, and you can browse through each logbook individually.

2) This function was there long time ago (since I needed it myself) but somehow vanished. I added it back in revision 2126. You can now craft an URL like

https://midas.psi.ch/elogs/Forum/past-8

to show the last 8 hours.

 You've probably seen my other posts on this subject.

I want to be able to re-edit some entries but I need some way to know the dates entries were re-edited.

Am I just approaching this the wrong way? Should I disable re-editing of entries and use threads to follow changes by posting replies to an entry?

The only problem with that is that if I make a mistake I will have to submit a new entry to fix it. 

Thank you for your advice.

Please read the FAQ

Apart from logging when and who, is it also possible to somehow log WHAT has changed (like $attribute + $old_value was changed by $who at $date)

 No, this is not possible.

With SSL enabled, I'd like to to grab the CN (Common Name) of the user certificate and use that as login authentication method.

I am thinking of the following scenario:

- users with read & write privileges need to have an SSL certificate loaded in their browser. The "Author" field will be pre-set to the CN of the user certificate.

- authorization may be subject to further granularity (e.g. only allow users whose certificate belongs to a certain organization)

- read-only, guest access (without certificate) may or may not be allowed

Is there a way to do that?

 I put your request on the wish list.

Hello All,

I am wondering if it is possible to configure ELOG to expand the TEXT column in the SUMMARY view? As it stands I get about 48 characters displayed per line in the in the TEXT column, with 3 lines getting displayed per ENTRY (approximately 144 characters per ENTRY). So what I'd like to do is see if it is possible to EXPAND the TEXT column in the SUMMARY view to allow say.... 100 characters per line, or say 275 characters per ENTRY when viewing the SUMMARY view?

Is this possible? If so, how does one go about doing this... I tried to search the site thoroughly before posting my question, I just didn't see it mentioned anywhere... Help please =)

Thanks!

agentdcooper

Summary lines = NNN

Hi,

when I choose the Spanish language, the command Copy To isn't allowed. I have had to change the language file and  change the line:

Copy To = Copiar a

to

Copy To = Copy To

Bye!

That's strange. I just tried (even with Spanish) and it worked for me. Which version of elog do you have installed? Can you send me your elogd.cfg file?

I intend to create a script that updates one of our elog logbooks based on mails it receives. I was hoping to be able to do this using the "elog" command line tool. Adding a new entry works fine, as does "replying" to an existing entry. The only thing I cannot get to work is editing an existing entry. All entries ahve several attributes and I intend not to use the "message" itself. I tried the following (on the machine this elogd is running on):

1. Create a new entry with Attribute1 set to "value":
   

   elog -a 'Attribute1=value' -x -h localhost -l 'LOGBOOK' -p 8080 -u USER PASSWD

   This works - the entry gets created and is displayed properly.
NOTE: I found that this does not work if LOGBOOK has any spaces in it - I would get error messages where the logbook was not found.
 

2. Edit this entry to set a second attribute:

   elog -e 1 -a 'Attribute2=something' -x -h localhost -l 'LOGBOOK' -p 8080 -u USER PASSWD

   The result was: Error transmitting message. Running the same command with -v gives me a whole bunch of text with at the end this message (I've stripped the HTML): "This entry has in meantime been modified by someone else. Submitting it now would overwrite the other modification and is therefore prohibited." However, I know for certain that this entry is not being editied by anyone at that moment, so I'm wondering what I'm doing wrong here...

elog -a 'Attribute1=value' -x -h localhost -l 'LOG\ BOOK' -p 8080 -u USER PASSWD

Message successfully transmitted, ID=12345

 I fixed two things:

• The logbook can now contain a space. Enclose it in double quotes such as elog -l "LOG BOOK" ...
• The error you report comes from the fact that you are the first person using elog submissions together with "use lock=1" in the configuration file. This has never been tested and therefore does not work . So I fixed this by adding a new hidden parameter. If you update to SVN revision 2122, things should work

Concerning your request of editing existing entries by their idea, I agree with Yoshi that you could grab the ID upon the first submission. An alternative is to make a direct search on a logbook. Since this is not implemented in the elog command line tool, you have to use wget for it:

wget "http://localhost:8080/LOGBOOK/?mode=raw&Attribute1=something" -O elog.txt

A problem here is that the username and password are normally transmitted in an encrypted form as cookies by your browser after you logged in. Now you have to convince wget first to log in like

wget "http://localhost:8080/LOGBOOK/?unamee=USER&upassword=PASSWD"--save-cookies cookies.txt

followed by a second call to wget with --load-cookies cookies.txt. I tried that but was not successful since the login procedure above redirects to the elog listing page, and only the cookies set after the redirection were saved in cookies.txt. Maybe you can figure out how to do that. The only way I could get it to work is to supply the encoded password, which I manually obtained from the password file. The URL was then

wget "http://localhost:8080/LOGBOOK/?mode=raw&Attribute1=something&unm=USER&upwd=ENC_PWD" -O elog.txt

Tehe, leave it to us "stupid users" to break your nice little program in new and exiting ways... ;-) But: THANK YOU! Both things are indeed working now - that brings me one step closes to my automated logbook, which is great!

wget "http://localhost:8080/LOGBOOK/?mode=raw&Attribute1=something" -O elog.txt

wget "http://localhost:8080/LOGBOOK/?unamee=USER&upassword=PASSWD"--save-cookies cookies.txt

wget "http://localhost:8080/LOGBOOK/?mode=raw&Attribute1=something&unm=USER&upwd=ENC_PWD" -O elog.txt

I thought about grabbing the ID on first creation. The problem with that is that I really would have to run parallel "databases" - one in elog to keep the information I want plus a second one which maps the elog-IDs to the "real" IDs - and the second one would also have to deal with things like "ID exists", "ID doesn't exist", "ID gets deleted" and so on - just the kind of hassle I want to avoid. But what you suggest with wget will most likely be sufficient. The logbook in question is readable for everyone (only editing/writing requires authentication), so I can search without password hassle. In fact, this will work:

wget -q "http://localhost:8080/LOGBOOK/?mode=raw&Attribute1=something" -O -| grep '\$@MID'|awk '{print $2}'

Et voila, I have an ID. This will generate a bit more traffic than a parallel "DB", but I think it will be less susceptible to errors, as all information is kept within the elog logbook at all times. Thanks again for your help - time to do some scripting! :-)

hello all,

#1 i love ELOG : excellent app! i would like to ask/present a question here -- I have a couple of TYPE's defined as;

       Options Type = Day Shift, Swing Shift, Night Shift
What I'd love to be able to do, is depending on what TYPE was selected during the creation of a NEW ENTRY in the ELOG "shift log" I'd love to display in the LIST VIEW (full, summary, or threaded views) different color's based on which TYPE was selected...

for example, if someone chose "Day Shift" that would be listed with a GREEN background, if someone chooses "Swing Shift" that gets a BLUE background, and so forth... I am wondering how one would go about implementing this?

second question... instead of listing the column named TYPE, can I just change it somewhere in the config to "SHIFT" so that in the list view, and even when in the NEW ENTRY form, I'd like it to show "Shift" instead of TYPE --- really I am just wondering if I can change the verbage that ELOG is using for the term TYPE? Is that doable?

Thanks for the app, I look forward to any reponses! I been editing the CSS, and once done think I'll add it to yr Config Examples, as I don't see many CSS themes there...

-peace-

Style Shift Day = background-color:green
Style Shift Swing = background-color:blue

Attributes = Shift, Shift leader
Options Shift = Day, Swing, ... <and so on>
Options Shift leader = Mike, Edward, John, ... <and so on>