Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 380 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Show attachments  Show only new entries    6457 Entries 
Goto page Previous  1, 2, 3 ... 379, 380, 381 ... 806, 807, 808   Next  
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  67291   Thu Jun 21 05:29:59 2012 Reply Ken Harveyrichard.harvey@l-3com.comQuestionLinux2.9.1-2435Re: author field in reply

Andreas Luedeke wrote:

Ken Harvey wrote:

A. Tuttle wrote:
Look in https://midas.psi.ch/elog/config.html
--
Fun things to set are:
Preset on first reply <attribute> = <string>
and
Preset on reply <attribute> = <string>


I am a newbie to being the administrator to ELog, but have used it for a while now. We just updated and have the same issue with the reply now. Unfortunatley I am not much of a programmer, yet, still learning. In our config file it has "Preset Name = $long_name", "Preset Author = $long_name", "Preset on reply Author = $long_name". By looking in the Syntax of elogd.cfg section, it seems to be correct, but I am not sure. Can you give me a suggestion on how it should look? Or tell me why it is not working and lead me in the right direction on how to correctly set it up? Thank you for your time.


A common mistake is to think that "Author" is some kind of keyword: it is not.
You can use any defined attribute, if you want to use "Author" this attribute needs to be defined in the "Attributes=" command line.
Attributes = Author, ...
Then you can use the "Preset" command.
Preset Author = $long_name
Preset on reply Author = $long_name


I've just tested it with 2.9.0-2435 and it works fine.
If the following 4 line minimal logbook configuration does not work for 2.9.1, then please post again:
Attributes = Author
Preset Author = $long_name
Preset on reply Author = $long_name
Locked Attributes = Author

Cheers
Andreas


Thanks Andreas,

That cleared up a lot for me. With your information I was able to figure it out. I got rid of the Author and just went with Name, and now it all works good.

Again, thanks for your help,

Ken Harvey
  65732   Mon Feb 11 22:16:33 2008 Entry Richard Ecclestonerichard.ecclestone@cern.chBug reportLinux | WindowsV2.7.2Data Export:: Date Problem

Hi

Im currently experimenting with Elog to see if we can use it to track maintenance work. But Ive come up against a problem, When I export the data to a csv file,

the date has a comma inserted between the day of the week and the rest of the date. This means that all the fields are then shifted to the right after the date.

This looks like a bug to me, the test records included in the demo does not exhibit this problem, until a new record is added.

cheers Richard

 

  65735   Tue Feb 12 08:54:48 2008 Reply Richard Ecclestonerichard.ecclestone@cern.chBug reportLinux | WindowsV2.7.2Re: Data Export:: Date Problem

Stefan Ritt wrote:

Stefan Ritt wrote:

Richard Ecclestone wrote:

Hi

Im currently experimenting with Elog to see if we can use it to track maintenance work. But Ive come up against a problem, When I export the data to a csv file,

the date has a comma inserted between the day of the week and the rest of the date. This means that all the fields are then shifted to the right after the date.

This looks like a bug to me, the test records included in the demo does not exhibit this problem, until a new record is added.

  What about exporting record separated by a semicolong ";" ?

I fixed that in SVN revision #2040, the comma is simply replaced by a space in the date string.

Hi Stefan

Thanks for the quick reply.

We seem to be running 2012 - Which may explain the problem - I will see with our system administrator why we are not running 2040. By the way I also had this problem when running the windows version.

Cheers.. Richard

  65736   Tue Feb 12 10:52:17 2008 Reply Richard Ecclestonerichard.ecclestone@cern.chBug reportLinux | WindowsV2.7.2Re: Data Export:: Date Problem

Richard Ecclestone wrote:

Stefan Ritt wrote:

Stefan Ritt wrote:

Richard Ecclestone wrote:

Hi

Im currently experimenting with Elog to see if we can use it to track maintenance work. But Ive come up against a problem, When I export the data to a csv file,

the date has a comma inserted between the day of the week and the rest of the date. This means that all the fields are then shifted to the right after the date.

This looks like a bug to me, the test records included in the demo does not exhibit this problem, until a new record is added.

  What about exporting record separated by a semicolong ";" ?

I fixed that in SVN revision #2040, the comma is simply replaced by a space in the date string.

Hi Stefan

Thanks for the quick reply.

We seem to be running 2012 - Which may explain the problem - I will see with our system administrator why we are not running 2040. By the way I also had this problem when running the windows version.

Cheers.. Richard

Hi Stefan

Our IT administrator has just downloaded and installed the latest source code from the site and installed it. We still now have version 2012?

Where do we get version 2041 ?

Cheers,  Richard

 

  65738   Tue Feb 12 20:40:53 2008 Reply Richard Ecclestonerichard.ecclestone@cern.chBug reportLinux | WindowsV2.7.2Re: Data Export:: Date Problem

Stefan Ritt wrote:

Richard Ecclestone wrote:

Our IT administrator has just downloaded and installed the latest source code from the site and installed it. We still now have version 2012?

Where do we get version 2041 ?

The bleeding edge version you get always from our SVN server, but you have to recompile it yourself. For your convenience, I just made you a version 2.7.2-3 containing the latest source code.

Thanks Stefan

Everything works now.

  65742   Fri Feb 15 15:46:38 2008 Reply Richard Ecclestonerichard.ecclestone@cern.chInfoWindowsELOG V2.7.Re: Message ID and trouble ticketing system

lance wrote:

Stefan Ritt wrote:

lance wrote:

I am trying to create a trouble ticket system however when you do a reply you get a new message ID.  I was hoping to use the message ID as a ticket number and just wanted to use the reply as an append to the orginal message id, however each reply creates a new message id. This would be a nightmare to track and if I closed the ticket I would have to close every log entry related to this.

Does anyone know how to either make the reply and appended reply (appended to the orignal message id) or how to create a field that automatically gives it a new trouble ticket number.

Has anyone configured a trouble ticket system that I could look at to get some ideas?

First of all, ELOG has been designed having shift logbooks in mind, so it probably will never be a perfect trouble ticket system. Nevertheless, there are some options which can help in that respect:

  • Use attributes Ticket and Status
  • Preset Ticket with a running ticket number via

    Preset ticket = TCK-#####

    This will increment the 5-digit ticket number whenever you create a new ticket, but will not update it when you do a reply

  • Use Status to determine the status of the whole trouble ticket chain (initial entry plus replies)

    Options Status = open, closed
    Preset Status = open

  • Once a ticked chain is closed, do the following:

    • Go to the threaded list display
    • Click on Select
    • Select the trouble ticket chain
    • Click on Edit
    • Now change Status from "Open" to "Closed"
    This will then modify the Status of the whole chain from "Open" to "Closed"

Stefan,

Thanks for this, I had already implemented the Preset Ticket Nr = TT-##### but I didnt use the threaded and Select to close the ticket, very nice tip thanks. I think this program can be have several uses, and working very well. The trouble ticketing will work for us.

Once again thanks for the very speedy support.

Lance

 

 

Hi

I tried the 'Preset ticket = TCK-#####' method to create unique numbers for our application. This worked very nicely until we replied to a earlier message, if we then create a new message the system creates a sequential number after the last message number we replied to. For example if we have 10 messages. If someone replies to message number #2 then when a new record is created it is then assigned number #3 not #11, thus making a duplicate entry for #3.

 Any ideas?

Cheers Richard

  66122   Fri Dec 19 14:59:29 2008 Blink riboribo1@hispeed.chQuestionLinux2.7.4lost elogd.cfg

 

Hi
I’m running SLES Linux Box with Elog 2.7.4, until yesterday everything was running perfectly. Now elog is not running anymore, because the elogd.cfg where i made changes for my use is lost.....(arghhhhh......) The logbooks ar still under /usr/local/elog/logbooks aviable.
Now i would like to upgrade to the latest version of elog. How to i made my logbooks available ?
thanks for your feedback.
ribo
  69821   Wed Aug 7 22:54:03 2024 Question Walter Reviolreviol@anl.govQuestionAll2Can Elog make a table?

Hi!

I like to format an Elog "directory" such that all entries make/occur as a table. Say: 5 columns and a large number of rows. In a sense, make an excel spreadsheet in Elog. Is this possible? How can this be done? Is there perhaps a template?

Thanks in advance.

Walter Reviol

reviol@anl.gov

Goto page Previous  1, 2, 3 ... 379, 380, 381 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6