TMG-L Archives

Archiver > TMG > 2003-06 > 1054483028


From: "Darrell A. Martin" <>
Subject: [TMG] Auto relation tag - my wishes
Date: Sun, 01 Jun 2003 10:57:08 -0500
References: <5.1.0.14.0.20030531203304.00a3f7a0@pop.sprynet.com>
In-Reply-To: <3ED96734.63E871ED@infoave.net>


At 09:38 PM 5/31/03 -0500, Richard Brogger wrote:
>Darrell A Martin wrote:
> >
> > Hi:
> >
> > I am interested enough. I would like the created Tags to differ from other
> > event Tags *only* in the manner in which they are created; in other words,
> > that the display and printed output would be governed in the same way as
> > non-Relationship Tags.
> >
> > Darrell
> >
>Hi Darrell,
>
>Yes, that would be one of the advantages. It is also a reason why it
>would require the ability to turn them off for P1's Person View. Can
>you imagine Andy's focus Person View with thousands of Relation Tags
>and some tags listing over a thousand relationships. <grin>
>
>Richard Brogger

Hi, Richard:

It is dawning on me that we may be talking about two different, although
closely related, things. I would like to be able to create a TAG (in the
fullest sense of the word) for each member of my dataset, that would be
*something like* this:

Tag: Rel-Tag
P1: Person to whom related Role:Rel-Target
P2: Related person Role:Rel-Self
Sentence: R:Rel-Self <is | was> the **rel term** of R:Rel-Target
The sentence should be fully user modifiable.
The user should be able to select whether this Tag
is primary, and if so Rel-Tags for all other
Rel-Targets should be set to non-primary. This
selection should be separate for P1/Rel-Target
(default NO) and P2/Rel-Self (default YES).
The user should be able to select whether Tags
would be created for "not related" conditions
(default NO).

(( NOTE: An alternative system might put the "Rel-Target" only in the Tag
memo field as text, not linked as a person at all. In this alternative, the
Rel-Self person would be the only person linked to each Tag, except for one
"Rel-Tags have been created for" Tag for the Rel-Target person. Although I
recognize some advantages this alternative might have, I do not
particularly like it. ))

It is understood that it would be possible for a fanatical user to go
overboard with this feature and create gazillions of Tags, cluttering up
PVs beyond belief (if non-primary tags are selected for display) and
generally making the program look semi-usable, at best, to someone else.
However, doing so would not actually damage any data.

Once created, these Tags should not change without direct positive user
action. (My reason for wanting this is mostly performance based. Otherwise
automatically maintaining these Tags wouldn't bother me ... once I have my
20 GHz PC, with the 3 ms access time hard drive, and 4 GB of memory.)

There should be a parallel feature "delete all Rel-Tags where (person ID)
is Rel-Target".

If this feature were used for a target person for whom Rel-Tags had already
been created, all of those existing Rel-Tags should be deleted first. Then
the new Tags should be created. (The point is not the method, but that
there needs to be a "refresh" procedure that "updates" existing Tags. This
would need to include deleting Tags that would not be created in the new
instance, whether because of a change in the selection criteria or because
of a change in the underlying data.)

I would find such a feature useful. It is not exactly a burning priority
with me, however [grin].

Darrell


Darrell Allen MARTIN
a native Vermonter currently in exile in Addison, Illinois
www.darrell-martin.net/genealogy/

This thread: