| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
65898
|
Tue Jun 3 12:47:13 2008 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | All | latest | Re: Re: $entry time not readable by Subst, else not datetime type? |
| Dennis Seitz wrote: | | Do you mean '$entry time', or did you create a new parameter? (I don't see $entry date in the elogd.cfg reference) |
Yes, of course I mean '$entry time', sorry for the misspelling. |
|
65901
|
Thu Jun 5 01:38:17 2008 |
| Dennis Seitz | dseitz@cosmology.berkeley.edu | Question | All | latest | Re: Re: $entry time not readable by Subst, else not datetime type? |
| Stefan Ritt wrote: |
| Dennis Seitz wrote: | | Do you mean '$entry time', or did you create a new parameter? (I don't see $entry date in the elogd.cfg reference) |
Yes, of course I mean '$entry time', sorry for the misspelling. |
Well, we really appreciate the way you keep adding features and making improvements. I thought you might have slipped a new one in! |
|
1832
|
Fri May 19 12:19:38 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | ELOG V2.6. | Re: Re: $datetime display |
| Fergus Lynch wrote: | Apologies for being so dense but try as I might I cannot get the $datetime display to show only Day, Month , Year,hour and minutes, NOT seconds.
I dont nee the seconds display!
Could you please clarify the systax for me. |
Can you show me the elogd.cfg syntax you try to use? |
|
1833
|
Fri May 19 14:01:34 2006 |
| Fergus Lynch | flynch@alternativenetworks.com | Request | Windows | ELOG V2.6. | Re: Re: $datetime display |
| Stefan Ritt wrote: |
| Fergus Lynch wrote: | Apologies for being so dense but try as I might I cannot get the $datetime display to show only Day, Month , Year,hour and minutes, NOT seconds.
I dont nee the seconds display!
Could you please clarify the systax for me. |
Can you show me the elogd.cfg syntax you try to use? |
Hi There!
See in bold below (I'm sure this is me being dense, so thanks for quick reply)
Fergus
Theme = default
Comment = Recording work carried out on any core system
Time format = %B %d, %Y, %H:%M
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Status |
|
1834
|
Sat May 20 09:48:52 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | ELOG V2.6. | Re: Re: $datetime display |
| Fergus Lynch wrote: |
| Stefan Ritt wrote: |
| Fergus Lynch wrote: | Apologies for being so dense but try as I might I cannot get the $datetime display to show only Day, Month , Year,hour and minutes, NOT seconds.
I dont nee the seconds display!
Could you please clarify the systax for me. |
Can you show me the elogd.cfg syntax you try to use? |
Hi There!
See in bold below (I'm sure this is me being dense, so thanks for quick reply)
Fergus
Theme = default
Comment = Recording work carried out on any core system
Time format = %B %d, %Y, %H:%M
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Status |
What about
Time format = %B %d, %Y, %H:%M:%S |
|
1835
|
Mon May 22 10:37:36 2006 |
| Fergus Lynch | flynch@alternativenetworks.com | Request | Windows | ELOG V2.6. | Re: Re: $datetime display |
| Stefan Ritt wrote: |
| Fergus Lynch wrote: |
| Stefan Ritt wrote: |
| Fergus Lynch wrote: | Apologies for being so dense but try as I might I cannot get the $datetime display to show only Day, Month , Year,hour and minutes, NOT seconds.
I dont nee the seconds display!
Could you please clarify the systax for me. |
Can you show me the elogd.cfg syntax you try to use? |
Hi There!
See in bold below (I'm sure this is me being dense, so thanks for quick reply)
Fergus
Theme = default
Comment = Recording work carried out on any core system
Time format = %B %d, %Y, %H:%M
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Status |
What about
Time format = %B %d, %Y, %H:%M:%S |
Thanks, did the trick and working perfectly (I was being dense!) |
|
67424
|
Thu Jan 10 22:07:10 2013 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Windows | 2.9 | Re: Re-using IDs after move to another Logbook overwrite Entries |
| Barend wrote: |
|
Hi Stefan,
I have observed following behavior when I move entries from one logbook to another:
- The first entry in "Open" get ID "1"
- When I move this Item to "Closed", it will keep ID "1" as I have used "Preserve IDs = 1"
- A new entry in "Open" gets ID "1" again
- When I move this item to "Closed" it will overwrite the previous ID "1" in "Closed"
- A new entry in "open" gets ID "1" again....
Every new entry in "Open" will get the next higher ID Number related to the highest available ID number/entry in "Open".
Upon "move to Closed", the previous entries in "Closed"will be overwritten.
Is there a way to prevent the usage of a previously used ID Number when entering a new ID?
I.e. If an entry with ID "1" has been used in "Open" and moved to "Closed", have the next entry in "Open" use ID "2"?
Kind regards,
Barend
|
Hi Barend,
The counting of entries, or even "tickets", only works within a particular logbook. If you archive a set of entries to another [archive] logbook, the archived set disappears from view of the original logbook. Should that entry, from logbook to archive, be the *latest* thread, then there is the danger of over-writing message ID, Ticket No and the like.
My policy to prevent the problem is to archive only threads that are say (depending upon use) a month after last entry..
|
|
67425
|
Fri Jan 11 08:17:37 2013 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.9 | Re: Re-using IDs after move to another Logbook overwrite Entries |
| David Pilgram wrote: |
|
| Barend wrote: |
|
Hi Stefan,
I have observed following behavior when I move entries from one logbook to another:
- The first entry in "Open" get ID "1"
- When I move this Item to "Closed", it will keep ID "1" as I have used "Preserve IDs = 1"
- A new entry in "Open" gets ID "1" again
- When I move this item to "Closed" it will overwrite the previous ID "1" in "Closed"
- A new entry in "open" gets ID "1" again....
Every new entry in "Open" will get the next higher ID Number related to the highest available ID number/entry in "Open".
Upon "move to Closed", the previous entries in "Closed"will be overwritten.
Is there a way to prevent the usage of a previously used ID Number when entering a new ID?
I.e. If an entry with ID "1" has been used in "Open" and moved to "Closed", have the next entry in "Open" use ID "2"?
Kind regards,
Barend
|
Hi Barend,
The counting of entries, or even "tickets", only works within a particular logbook. If you archive a set of entries to another [archive] logbook, the archived set disappears from view of the original logbook. Should that entry, from logbook to archive, be the *latest* thread, then there is the danger of over-writing message ID, Ticket No and the like.
My policy to prevent the problem is to archive only threads that are say (depending upon use) a month after last entry..
|
I generally consider using the ID as ticket number a bad idea. The ID is the "primary key" (in terms of database language), and must be unique inside a logbook. So when moving entries between logbooks, there will be always problems.
Why don't you define an attribute "Ticket ID" and use that one? That won't change when you move the entry between logbooks:
Attributes = Ticket ID, Subject, ...
Preset Ticket ID = ID-#####
|
|