GenoPro Support Forum

Is there a way how to do it at the moment?

Unless Genopro can give you a better answer, for the time being I suggest:

1) in View -> TL Pictures, sort your picts by ID No. The highest Nos should be your latest picts.

2) outside Genopro, in your pictures directory, make sure the columns/fields: Date Modified, Date Created and Date Picture Taken are visible. These fields may give you a hint.

From the 2 above points, you should have a good idea/approximation of your latest Picts.

I could add a field to read the timestamp of the .jpg file and display it in the Table Layout.  This feature would be similar as the filesize (KB) and the image size (width and height).

Dan I do not think this is the solution. It can help in some cases but you can sort the files (JPGs) in the folder on your disc. The timestamp of the JPG has nothing to do with the date where the picture was added to GenoPro database.

Please consider seriously to add date/time stamp (field-at least internal) to all important objects in the GEnoPro database. There is even more possibilities: one date/time stamp for the date where the field (picture, source, birth...) was added first and second date/time stamp for the last modified information. Especially this one is really important.

It is not the same as record all the actions to be able to do Undo (and possibly to find out the date/time of an action).

All the professional genealogic software has such kind of date stamp and I think that GenoPro is on the way to be really professional too.

Anyway thank you for your work.

Jan

The good news is we will implement a feature to record the date & time of any object (individual, family, picture, place, source, etc).  We also plan to record who (which user) modified the object and keep a history of the modifications.

We are facing a technical problem because the timestamp cannot be part of the object itself for the following reasons:

1. The detection of a modified object is done when computing an Undo entry.  If an object is considered modified, then adding a timestamp will modify the object again.  Using this approach, we will need a mechanism to update the timestamp, yet bypassing the Undo.  Also, each modification will require the Undo manager to re-synchronize twice, which would affect the performance.
2. GenoPro merges identical records such as identical pictures, places and sources.  Two object are identical regardless of their timestamp, however this would fail if the timestamp is stored in the object itself.
3. In the future, we plan to implement a true multi-user version of GenoPro.  For this, we will need a special differentiator to detect which object have been modified in order to merge them on the server.  Having a timestamp part of the object will complicate things.
4. Someone could flush the modification history, yet the family tree should not be considered as modified.  We plan to offer a mechanism for people to share their family trees on the web, and others could download portions of it.  The user may choose to not download the whole modification history of each object.
5. We need a mechanism to group the modification history, such as one history entry per day to avoid having a long log of meaningless modification history.  Some people save many times per hour, and we may want to update the timestamp instead of creating a new timestamp in the log.

The solution is to treat the timestamp (and the user who modified the object) as metatdata.  In other words, the modified date & time is not data, but extra information about the data itself.  A good analogy is the bold tag <b> in HTML.  This tag <b> is not part of the text, but a directive to better display the text.  The tag <b> is optional and can be removed without changing the content of the text.  The same can be said about the timestamp.

As a result, we need to revise our architecture to implement the metadata, from merging duplicates, copy & paste, saving to disk and handling the Undo/Redo.

Edited: Friday, August 25, 2006 by GenoProSupport

1. Is it an option to have some symbol combination which will add text label timstap/sig as i.e. in wikipedia "~~~~". And if someone wants to remove it he has to remove text. It wouldn't much affect undo-redo, or all labels should be added automaticaly at file save/close to places edited during session?! BTW It would require some sort of entering some log-in info for the editor!
2. It would be a problem then! Unless if separated with some separator as in mail/news programs "--" and then the text after might be simply ignored and more recent value or both values written if values are the same as well one might be ignored!
3. As I suggested, some text label within symbols at the end of note (data), i.e.-- ($last modified by "User" at YYYY.MM.DD HH:MM$)

Web design is not my area of expertise, but I thing that some symbol combinations could be easily defined as metadata begginings / ends and they might be as well written as text references in some fields of person's properties. I.e. you might add a new tag where could revision history of one's data be recorded i.e. "User1 , date, time, added this date, removed this data, edited this label etc." And there might be an option to flush this data from file to reduce size...

---

"εν οιδα οτι ουδεν οιδα" (Σωκρατησ)  - "The only thing that I know is that I don't know anything" (Socrates)