Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 417 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Show attachments  Show only new entries    6459 Entries 
Goto page Previous  1, 2, 3 ... 416, 417, 418 ... 806, 807, 808   Next  
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  69336   Tue Mar 30 13:43:46 2021 Reply Richard Stamperrichard.stamper@stfc.ac.ukQuestionLinux3.1.3-1-1Re: Pre-fill Attribute with last entry

Just noting that, depending on what you want to achieve, you may be able to use the threading functionality so that a "new" entry is actually a "reply" to a previous entry.  This will allow you to populate attributes with values from that previous entry without having to rely on storing information outside the system, with all the attendant concurrency risks already identified.

Sebastian Schenk wrote:

I am glad, we could help.

I can see a caveat in the recommendation.
By having "Execute New = echo $attrib > /path/last_attrib" and "Preset attrib = $shell(cat /path/last_attrib)" as the most simple construction.
But there are cases, where /path/last_attrib can get out of sync with the elog by e.g. editing or deleting the last entry, which is the most likely one to edit or delete.

I am aware, that you can make the logic more complex to fix this issue,
but basically you have the same information stored in two locations and you have to keep them in sync for the system to be reliable.
I am not sure, if it will be more hassle to construct a script/config system to keep them in sync or to find a solution which gets the information from the elog database.

Dominic Schneider wrote:

Thank you very much.

So far I testet all functionalities and scripts to reach my goal. I will post a dummy of the solution later on for future purposes.

Best wishes 

Stefan Ritt wrote:

That would actually be my recommendation. There is a "execute new" which you can call when submitting a new entry.

Stefan

Dominic Schneider wrote:

Hi Stefan, hi Sebastian,

thank you for your help. Ok I see its not that simple.

Is there maybe a way of executing a Script on submitting, writing the values of the Attributes into an temporary file and loading the values from this file via a preset shell script when opening a NEW entry?

Best wishes & thanks in advance

Sebastian Schenk wrote:

Sorry Stefan, but it is possible as you have the scripting ability.

The idea is to use "Preset Test_Attribute = $shell(script_to_get_the_last_entry)", where the script asks elog about the details and parses them.
The problem here is, that the elogd already is working to resolve the click on "new entry" request (or similar) and the script can't call elogd until the page is delievered, what is to late.
(If it would, the elogd will hang.)

So the script either has to directly parse all the entry.log files in the logbook folder or you need a second elogd running, which can answer the request from the script.
This second elogd could run on a different port and it doen't need to be public as it only answers internal requests and could use the same config as the "primary" elogd.
My idea for the script uses the python elog module to establish the connection and do the parsing.

I hope this helps as a workaround.
Best wishes,
Sebastian

 

Stefan Ritt wrote:

Nope, there is no way to acces the last value of an attribute. Sorry.

Stefan

Dominic Schneider wrote:

Hi all together,

I struggle a lot with the following problem:
I try to prefill certain attributes with the value of exactly the same attribute in the last entry made in the same logbook.

I know I have to go with Preset, tried a view hours and searched the forum but i didn't find a thing. Am I overlooking a flag, an option or whatever, or is there just not such a functionality (which I dont believe)?

I thought about:
Preset Test_Attribute = $Test_attribute
Preset Test_Attribute = Re:$Test_attribute
Preset Test_Attribute = $shell(Command to somehow get last entry and this attributes value)
Not succesful though.

I would be very thankful for help, thanks in advance.

 

 

 

 

 

 

 

  65720   Wed Jan 30 10:28:50 2008 Question Richard Hardwickrch@skynet.beQuestionAllcurrentCross references within ELOG

How can I make a cross reference from one entry to another entry in the same ELOG logbook?

  65722   Wed Jan 30 19:22:23 2008 Reply Richard Hardwickrch@skynet.beQuestionAllcurrentRe: Cross references within ELOG

Stefan Ritt wrote:

Richard Hardwick wrote:

How can I make a cross reference from one entry to another entry in the same ELOG logbook?

Have a look at http://midas.psi.ch/elog/userguide.html, under the section "Adding stuff to a logbook". Basically you can write elog:<id>. At the moment, this works however only in the "plain" or "ELCode" encoding. For HTML encoding, I will add this functionality soon.

 

Thank you! The HTML functionality will be v. useful

  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

Goto page Previous  1, 2, 3 ... 416, 417, 418 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6