| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67429
|
Wed Feb 6 13:22:53 2013 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.9 | Re: Re-using IDs after move to another Logbook overwrite Entries |
| Barend wrote: |
|
I have tried to use the "Ticket ID" approach and with each new entry this Ticket ID is indeed increased automatically...
But when the last Entry (with the highest Ticket ID i.e. ID-0009) is move to another Logbook, the Ticket ID in the next new entry will be "ID-0009" again (based upon the last previous entry "ID-0008").
So this appraoch will also re-produce duplicate Ticket IDs.
Is it possible to have the Ticket ID preset with value based upon the Date & Time of the entry? Instead of holding a Date/Time format, use a calculated numeric format?
This way, each new entry will have a truely unique Ticket ID.
Thanks & Regards, Barend
|
Why do you move the last ticket in a logbook at all? The move functionality was more meant as an archive option, where you can archive old entries on an annual basis or so. If you just want to "close" a ticket for example, an attribute "Status" with options "open" and "close" will do it. Together with a quick filter you can easily show only open entries in an logbook that way.
Stefan |
|
67431
|
Wed Feb 6 18:18:24 2013 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Windows | 2.9 | Re: Re-using IDs after move to another Logbook overwrite Entries |
| Stefan Ritt wrote: |
|
| Barend wrote: |
|
I have tried to use the "Ticket ID" approach and with each new entry this Ticket ID is indeed increased automatically...
But when the last Entry (with the highest Ticket ID i.e. ID-0009) is move to another Logbook, the Ticket ID in the next new entry will be "ID-0009" again (based upon the last previous entry "ID-0008").
So this appraoch will also re-produce duplicate Ticket IDs.
Is it possible to have the Ticket ID preset with value based upon the Date & Time of the entry? Instead of holding a Date/Time format, use a calculated numeric format?
This way, each new entry will have a truely unique Ticket ID.
Thanks & Regards, Barend
|
Why do you move the last ticket in a logbook at all? The move functionality was more meant as an archive option, where you can archive old entries on an annual basis or so. If you just want to "close" a ticket for example, an attribute "Status" with options "open" and "close" will do it. Together with a quick filter you can easily show only open entries in an logbook that way.
Stefan
|
In the documentation:
>In addition to the #'s one may specify format specifiers which are passed to the strftime function. This allows to create tags wich contain the current year, month >and so on. Once the date part of the attribute changes, the index restarts from one. The statement
>Subst Number = XYZ-%Y-%b-###
>results in automatically created attributes
"Number"
of the form
>XYZ-2005-Oct-001
>XYZ-2005-Oct-002
>XYZ-2005-Oct-003
A little playing around with the %[Alpha character] s of strftime probably will generate a format that will suit your requirement - to the second if needs be.
For example I've checked that
Preset Ticket = T%y%m%d%H%M%S#
Generates a ticket number T1302061705141 at that particular moment.
Unfortuately for this to work, you have to have the "#" suffix, which will add a trailling "1" at the end of every ticket (unless you generate two new entries within a second of each other). There are plenty of ways to format all this available in strftime, and unless you keep changing the clock on your computer (which I am guilty of), the ticket numbers can be as unique as you care to make them, and sequentially increasing.
Having said that, I share the view with Stefan that the problem is moving a thread or entry to another logbook rather too early. Personally I keep a thread in the current log book for at least a month after it is "closed" before I move it, although partly that's because sometimes these threads come back to life. Although also because I ran into the same issue (moving the latest entry and finding the ID duplicated), and, realising the problem, then took the "wait" option to solve it.. |
|
65986
|
Thu Oct 2 20:21:15 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.7.4 | Re: Random Crashes |
| Wythe IT wrote: |
|
Running on windows server 2003.
Mysteriously from time to time i find ELOG has crashed and i must restart it.
Event log shows:
This has occurred twice so far in the month or less elog has been running. The platform is stable and i have no other issues or negative events besides incorrect ASP calls here and there. Thanks.
Faulting application elogd.exe, version 0.0.0.0, faulting module elogd.exe, version 0.0.0.0, fault address 0x0004b9c3.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
|
Unfortunately this is not enough information for me to conclude anything. You need to be able to reproduce the crash, then tell me exactly how you did it, so that I can reproduce it. Then I have a chance to fix it. |
|
67937
|
Tue May 26 22:03:05 2015 |
| Kamen Nikolov | kanikolov@gmail.com | Question | Windows | V2.9.0-239 | Re: RSS Feed Not Providing Time Stamps For datetime Attributes | Can anyone help? Do I need to do something different or could this possibly be a bug that is fixed in a newer version?
Thanks,
Kamen
| Kamen Nikolov wrote: |
|
Hello,
I am using the RSS feed feature of Elog (V2.9.0-2396). I have a couple of attributes of type "datetime" (Start Time and Stop Time). I don't have a "Time Format" statement, so just using the default format. I am passing the Start Time and Stop Time attributes to the RSS Title with $Start Time and $Stop Time, but when looking at the RSS title in IE11 browser, I only see the date and not the time. Is there any way I can see the time as well?
Additional info:
I'm also passing the creation time of the Elog with $entry time and this is displaying correctly (both date and time).
Please let me know if I am doing something incorrectly?
Thanks
|
|
|
67941
|
Wed May 27 10:50:41 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | V2.9.0-239 | Re: RSS Feed Not Providing Time Stamps For datetime Attributes | Hi Kamen,
I've just tried it for V3.1.0 (6ab0fd5) and the described behaviour is unchanged.
It is even worse if you don't specify the "RSS Title": datetime attributes are just displayed as seconds of the epoch then.
I think this is a feature of ELOG at the moment.
You'll either need to dig into the code yourself or wait for Stefan to fix it.
I have an idea for a quick workaround:
you can create new hidden attributes, that contains a copy of the datetime attribute as a string, set by the subst command. You could then use those string attribute in the "RSS Title": that should work.
Cheers
Andreas
| Kamen Nikolov wrote: |
|
Can anyone help? Do I need to do something different or could this possibly be a bug that is fixed in a newer version?
Thanks,
Kamen
| Kamen Nikolov wrote: |
|
Hello,
I am using the RSS feed feature of Elog (V2.9.0-2396). I have a couple of attributes of type "datetime" (Start Time and Stop Time). I don't have a "Time Format" statement, so just using the default format. I am passing the Start Time and Stop Time attributes to the RSS Title with $Start Time and $Stop Time, but when looking at the RSS title in IE11 browser, I only see the date and not the time. Is there any way I can see the time as well?
Additional info:
I'm also passing the creation time of the Elog with $entry time and this is displaying correctly (both date and time).
Please let me know if I am doing something incorrectly?
Thanks
|
|
|
|
67973
|
Tue Jun 9 13:22:25 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | V2.9.0-239 | Re: RSS Feed Not Providing Time Stamps For datetime Attributes | I fixed the problem in the current GIT version.
/Stefan
| Kamen Nikolov wrote: |
|
Can anyone help? Do I need to do something different or could this possibly be a bug that is fixed in a newer version?
Thanks,
Kamen
| Kamen Nikolov wrote: |
|
Hello,
I am using the RSS feed feature of Elog (V2.9.0-2396). I have a couple of attributes of type "datetime" (Start Time and Stop Time). I don't have a "Time Format" statement, so just using the default format. I am passing the Start Time and Stop Time attributes to the RSS Title with $Start Time and $Stop Time, but when looking at the RSS title in IE11 browser, I only see the date and not the time. Is there any way I can see the time as well?
Additional info:
I'm also passing the creation time of the Elog with $entry time and this is displaying correctly (both date and time).
Please let me know if I am doing something incorrectly?
Thanks
|
|
|
|
67220
|
Thu Mar 29 15:19:05 2012 |
| Stefan Ritt | lly thstefan.ritt@psi.ch | Info | Linux | All | ELOG V2.9. | Re: RSS Feed |
| leen smit wrote: | Hi All,
Just a quick message in the hope of helping other find an answer to the question: How to reach the RSS Feed???
I spend hours trying to find out what the correct URL is to reach the feed. The documentation on this is non-existent - at least we could't find this anywhere in the docs.
Answer: Just add elog.rdf at the end of the URL of the logbook!!
eg. http://midas.psi.ch/elogs/Forum/elog.rdf
Leen |
Actually the browser should show an RSS icon to help you subscribing to it. In Firefox 3 that was at least the case. Now they removed it. See here for a fix:
http://www.lifehacker.com.au/2011/03/rss-icon-brings-quick-rss-access-back-to-firefoxs-address-bar/
For other browsers it might be similar.
Best regards,
Stefan |
|
67221
|
Thu Mar 29 15:38:43 2012 |
| leen smit | leen.smit@gmail.com | Info | Linux | All | ELOG V2.9. | Re: RSS Feed |
I've just tested with Firefox, Chromium and IE, but no such icon appears. And for me this icon doesn't really help at all, as I'm using the feed to parse the logs
Besides, there is no mention of this Addon in the documentation, so the problem is still there: there is no easy way to find the feed URL.
|
|