Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
 Back  |  Find  |  Login  |  Help 
icon5.gif   Re-using IDs after move to another Logbook overwrite Entries, posted by Barend on Wed Jan 2 15:38:19 2013 
    icon2.gif   Re: Re-using IDs after move to another Logbook overwrite Entries, posted by David Pilgram on Thu Jan 10 22:07:10 2013 
       icon2.gif   Re: Re-using IDs after move to another Logbook overwrite Entries, posted by Stefan Ritt on Fri Jan 11 08:17:37 2013 
          icon2.gif   Re: Re-using IDs after move to another Logbook overwrite Entries, posted by Barend on Thu Jan 24 10:42:13 2013 
             icon2.gif   Re: Re-using IDs after move to another Logbook overwrite Entries, posted by Stefan Ritt on Wed Feb 6 13:22:53 2013 
                icon2.gif   Re: Re-using IDs after move to another Logbook overwrite Entries, posted by David Pilgram on Wed Feb 6 18:18:24 2013 
Message ID: 67429     Entry time: Wed Feb 6 13:22:53 2013     In reply to: 67428     Reply to this: 67431
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Question  OS: Windows  ELOG Version: 2.9 
Subject: 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 

ELOG V3.1.5-3fb85fa6