Is there any way to disable this use of only REFN/TYPE?

Sparkgapper

REFN is for user reference number, which makes it is a good place to store "reference" type things, and the subordinate tag (TYPE) can define the type of number so REFN can be used for multiple purposes if needed.

I like creation dates when I go back in my research to be able to learn when a person was created. You can also seach on creation dates to see all records created in some time span (such as on a research trip).

If you don't want them, you can unckeck "Add Creation Dates" in the general preferences. You can also uncheck "Track Change Dates" if you don't want them either. Both are checked by default because I think they enhance your records, but like almost everything in GEDitCOM II, you can customize it.

John

On May 23, 2012, at 8:15 AM, SparkMan wrote:

Hi John--- Please remove me from this discussion group. Thanks. - Richard

On May 23, 2012, at 11:55 AM, John Nairn wrote:

Thanks John and I think I will leave the Tracking.  It is just that I want to use the REFN as a family number if I can figure out how to build a macro to and use the TYPE as "Bates Family Number".  What are the associated Tags, other than TYPE, that go with REFN?  What I am thinking about is how to use this for multiple family references something like:
1 REFN                                          [REference Family Number]
2 FAMN BATES-York SC USA                [FAMily Name with Predecedent County, State & Country]
3 FANR 1.1.1.2.3                                [FAmily alpha/numeric NumbeR for the associated family name]
2 FAMN PRICE-Jones GA USA
3 FANR 1.1.2.4                          [each number is the individuals child/generation number within the family line]
                                                i.e.    [Predecedent].[first child of predecedent].[second child of 1.1].[fourth child of 1.1.2] = 1.1.2.4
etc...
This would allow several family lines to "own" each individual plus show the link with spousal families.  My primary concern here is when cousins marry it could cause multiple listings within one or more family lines.

The number (FANR) would also used tell each individual's generation from the predecedent by count of the number of decimal points.  i.e. 1.1.2.4 has three decimal points therefore this individual is third generation from predecedent.

I agree also about the "Creation Date" being a useful tool.  However, I would prefer to see that as a standard feature with its own Tags (CREA)? and file similar to CHAN.  

Sparkgapper

On May 23, 2012, at 9:55 AM, John Nairn wrote:

I changed your delivery to no email. Note that anyone getting this emails can customize settings and/or leave the group in their google account. The only problem is that some people enrolled with the wrong email and are not sure how to find the google account for that email. I don't know when google does not catch that problem when enrolling.

On May 23, 2012, at 9:52 AM, Richard Swanson wrote:

1 REFN (my number in any style)
2 TYPE (define the type of number)

GEDitCOM II gives you flexibility to decide how to enter these numbers. The advantage of using REFN is that it is part of the standard, the GEDitCOM II formats will display it well, and it might even be saved if loaded into different software through a GEDCOM file. For your case, you would probably want

1 REFN Bates-YORK SC USA
2 TYPE FAMN
1 REFN 1.1.1.2.3
2 TYPE FANR
1 REFN PRICE-Jones GA USA
2 TYPE FAMN
1 REFN 1.1.2.4
2 TYPE FANR

But this does not tie the FAMN and FANR together if there are more then one pair. You could do that with

1 REFN Bates-YORK SC USA/1.1.1.2.3
2 TYPE FAMN/FANR
1 REFN PRICE-Jones GA USA/1.1.2.4
2 TYPE FAMN/FANR

The REFN lines can have anything. Here you put one or two codes separated by a delimiter (e.g, the slash) and use the TYPE line to say which is which.

I think second might solve you issue, but you are not forced to use REFN. You could create a custom tag. GEDitCOM II will find them and if needed you could customize the display to show them any way you want. With custom tags you would drop REFN altogether such as

1 _FAMN Bates-YORK SC USA
2 _FANR 1.1.1.2.3
1 _FAMN PRICE-Jones GA USA
2 _FANR 1.1.2.4

Note the custom tags should (according to standard) begin in an underscore. When using custom tags, you can define and subordinate tags as done here to tie the FAMN and FANR together. GEDitCOM II will display them and some easy edits for format the display nicely and make it easy to add new ones.

I would recommend the second one, but it is your choice.

John

On May 23, 2012, at 10:00 AM, William G. Bates wrote: