In the password file, I see several same username, such as:

<user>

    <name>test</name>

    <password encoding="SHA256">iXhH.</password>

    <full_name>test me</full_name>

    <last_logout>Tue Apr 14 14:12:44 2009</last_logout>

    <last_activity>Wed May 19 09:39:32 2010</last_activity>

    <email>maqm@ihep.ac.cn</email>

    <email_notify/>

  </user> 

<user>

    <name>test</name>

    <password encoding="SHA256">iXhH.</password>

    <full_name>test me</full_name>

   <last_logout>0</last_logout>

    <last_activity>0</last_activity>

      <inactive>0</inactive>

    <email>maqm@ihep.ac.cn</email>

    <email_notify/>

  </user> 

<user>

    <name>test</name>

    <password encoding="SHA256">iXhH.</password>

    <full_name>test me</full_name>

    <last_logout>0</last_logout>

    <last_activity>0</last_activity>

      <inactive>0</inactive>

    <email>maqm@ihep.ac.cn</email>

       <email_notify/>

  </user> 

I don't know the reason why eLog can have the same username.

And what should I do to prevent these things happen?

Thanks!

I am attempting to setup an ECR (Engineering Change Review/Request) process in ELOG.

I have a logbook setup so that an original request is submitted with a status of "Approval Pending"

Options ECR Status = Approval Pending, Approved / In Progress, Completed / In QA, Closed

Once the entry is made, it is reviewed by several people who reply to the original entry and update the approval fields, adding any comments as a reply :

Options OPS Approval = Approved, Denied
Options ENG Approval = Approved, Denied
Options Director Approval = Approved, Denied

Once the final approval is obtained, they reply to the thread and update the ECR Status field to "Approved / In Progress"

This goes through our QA process, and is finaly updated with "Closed"

The problem is, I would like to keep the historical data of when the status of these entries are made. For example, in the message thread, I can see that reply #4 changed the "Status" field to "Approved". However, I can not seem to find a way for this to work with quick filtering. The quick filter always filters on the first entry on a thread, and not the last.

The other option would be to change the status of the first entry, but that seems silly as I am using replys instead of edits.

Any ideas on how to implement this "Status" field into my workflow? I am even open to losing the historical "status" and beeing able to change all entries on the thread on reply. (i.e. Reply #4 changes "Status" to "Approved", and the system changed all entries in the thread to "Approved")

Is there a way to open a form or table when clicking on New rather than going to a text field? Thanks, TS!

We upgraded to Elog 2.9.0-2402 and since then mails sent by Elog when posting an item are from the default account, not from the logged in user's mail address.

The configuration is, for the mail part :

Default Email From = Olivier.Callot@cern.ch

Use Email Subject = ELOG Computing Operations - $Subject ($Site - $System - $Production number)

Thanks for telling me which flag/option I have to set to restore the proper mail 'From:' field.

How about this:

Whenever a new file is uploaded, it would first be stored in a temporary directory. When the entry gets submitted, the files would be moved to the logbook directory and the entry edited accordingly.

Any wrongfully stored file would remain in that temp dir. Starting/restarting the daemon would cleanup that directory. Seems like a simpler approach and does not involve scripting the browser.

> It looks like the newest windows release of elog at
> http://midas.psi.ch/elog/download/windows/ is 2.81.
> 
>   elog281-1.exe	        23-Dec-2010 11:42 3.1M
>   elog-latest.exe       23-Dec-2010 11:42 3.1M
> 
> Can you post the 2.90 release.
> 
> Thanks.
> 
> -- rouilj

Yepp, done. I somehow overlooked it.

- Stefan

It looks like the newest windows release of elog at
http://midas.psi.ch/elog/download/windows/ is 2.81.

  elog281-1.exe	        23-Dec-2010 11:42 3.1M
  elog-latest.exe       23-Dec-2010 11:42 3.1M

Can you post the 2.90 release.

Thanks.

-- rouilj

Well, this is not so easy. When you leave the browser (via 'Back' or just by closing), it has no way to communicate with the elog server. I could put in some JavaScript, but if people switch off JavaScript there is no way. On the other hand it might be simple to write just a little shell script, which goes through all files on the server and checks if the file name occurs in some elog entry. This can probably be done with some combination of "find" and  "grep", but I'm not a shell script expert.