Re: Add date and time stamp to file upload, posted by Fergus Lynch on Tue Oct 9 11:48:17 2007
|
| Stefan Ritt wrote: |
| Fergus Lynch wrote: | | I would like to request a new feature - add date and time stamp to file upload. We use ELOG (amongst other things!) as a change log and this would really allow allow more accurate records to be kept. For instance we upload router config files (to record changes)and having the exact upload date would be a big enhancement, especially when there are a lot of attachments. |
There is already a time and a date stamp. If you look in the logbook directory, you see attachments preceded with the date and time when they were submitted. You can see this date/time when you click on the attachment, such as in
http://midas.psi.ch/elogs/Config+Examples/040519_000348/elogd.cfg
where you will see it even in the URL (May 19th, 2004, 0:03:48) in the above case. I agree that this is not so obvious. If you make a proposal where this date/time should be displayed, I can easily add it. |
Hi, I think this would be great new functionality, so I would propose the date/time stamp for an uploaded file was placed just after the file size text that appears at the far right hand side of all attachments.
Many Thanks
Fergus |
|
Re: Add date and time stamp to file upload, posted by Stefan Ritt on Fri Oct 19 21:44:00 2007
|
| Fergus Lynch wrote: | | Hi, I think this would be great new functionality, so I would propose the date/time stamp for an uploaded file was placed just after the file size text that appears at the far right hand side of all attachments. |
I implemented this as you can see at elog:Linux+Demo/14 . The new feature will be contained in the next release, and will also work for entries made before this feature was implemented. |
Email Notification: Clarification on Attribute - can value be a string?, posted by Alan Stone on Thu Oct 25 23:55:28 2007
|
I encountered a rather insidious feature which had me scratching trying quite
a number of things over the past couple of weeks until I compared what two
different users were doing.
I had defined the attributes:
; attributes
Attributes = Author, System, Report, Subject
Required Attributes = Author, System, Report, Subject
Extendable Options = System, Report
Options System = Data Transfer, RelVal, Skimming, Reconstruction, CSA07, Global Running, T0 Operations, T1 Operations, DataOps, ProdAgent
#Options Report = General, Fix, Info, Job Report, Problem, Shift Summary, Test, Flummoxed
Options Report = General, Fix, Info, Job_Report, Problem, Shift_Summary, Test, Flummoxed
Thread display = $Subject, entered by $author for $system on $Entry time
Quick filter = Date, Report
Reverse sort = 1
and the Email Notification:
; email notification
Suppress Email to users = 0
Omit Email To = 1
Use Email Subject = $system: $subject
#Use Email From = Author Email
Email Report General = hn-cms-dataopslog@cern.ch, cms-dataops@fnal.gov
Email Report Fix = hn-cms-dataopslog@cern.ch, cms-dataops@fnal.gov
Email Report Info = hn-cms-dataopslog@cern.ch, cms-dataops@fnal.gov
#Email Report Job Report = hn-cms-dataopslog@cern.ch, cms-dataops@fnal.gov
Email Report Job_Report = hn-cms-dataopslog@cern.ch, cms-dataops@fnal.gov
Email Report Problem = hn-cms-dataopslog@cern.ch, cms-dataops@fnal.gov
#Email Report Shift Summary = hn-cms-dataopslog@cern.ch, cms-dataops@fnal.gov
Email Report Shift_Summary = hn-cms-dataopslog@cern.ch, cms-dataops@fnal.gov
I finally realized that logbook entries sent with a two-word Attribute value
(Shift Summary, Job Report) would not be forwarded to the CMS HyperNews
forum or Fermilab List Server. I incorrectly assumed that:
Email <attribute> <value> = <list>
an attribute could be a string.
Do I have to remove the spaces (replace with hyphens or underscores)?
Alan |
|
Re: Email Notification: Clarification on Attribute - can value be a string?, posted by Stefan Ritt on Fri Oct 26 11:18:59 2007
|
If you read
http://midas.psi.ch/elog/config.html#email
you will see the sentence:
If either the attribute or the value contains one or more blanks the string must be enclosed with quotation marks, as in:
* Email Type "Normal routine" = ...
so in your case you should write
Email Report "Shift Summary" = ... |
Print Function, posted by Adam Blandford on Wed Dec 5 13:10:52 2007
|
While it is possible to print a logbook using the standard web browser print command in the Full or Summary view, a dedicated print function allowing the user to print out a hardcopy of a particular logbook would be very helpful.
Cheers
Adam
P.S. Thankyou for the response in elog:65671 |
|
Re: Print Function, posted by Stefan Ritt on Wed Dec 5 21:33:48 2007
|
| Adam Blandford wrote: |
|
While it is possible to print a logbook using the standard web browser print command in the Full or Summary view, a dedicated print function allowing the user to print out a hardcopy of a particular logbook would be very helpful.
Cheers
Adam
P.S. Thankyou for the response in elog:65671
|
This is possible since the beginning: Click on Find, then check Display full entries and Printable output and hit Search. You get then a single page containing all entries from the logbook which you can easily print to get a hardcopy. |
inline button for upload image, posted by stephane on Wed Jan 23 15:37:58 2008
|
Hello,
In elog version 2.7.1.2004, when I want to upload an image, after browsing I obtain a error message like < Upload command not unauthorized>. That is strange is the file is right uploaded in the logbook directory but not appear in the entry.
Thank you for your help.
Stéphane |
|
Re: inline button for upload image, posted by Stefan Ritt on Wed Jan 23 16:09:10 2008
|
| stephane wrote: |
|
Hello,
In elog version 2.7.1.2004, when I want to upload an image, after browsing I obtain a error message like < Upload command not unauthorized>. That is strange is the file is right uploaded in the logbook directory but not appear in the entry.
Thank you for your help.
Stéphane
|
Thank you for reporting this problem. I found that it was related with switching ELOG to French (in the English version it always worked). I fixed this in revision #2006 and re-made the 2.7.1 distribution with the bug fix. |
|