* What is a permanent record number?

[BEJ]

I find several references to "permanent record numbers" in the Knowledge Base, Forum, FH Help, Plugin Store, and GEDCOM resources. However, I cannot to find a definition or explanation of what they are.

What is a permanent record number?

[tatewise]

The RFN tag is a standard GEDCOM field and therefore supported by FH but its purpose is somewhat vague.
The GEDCOM specification says:

RFN {REC_FILE_NUMBER}:=
A permanent number assigned to a record that uniquely identifies it within a known file.

PERMANENT_RECORD_FILE_NUMBER:= {Size=1:90}
<REGISTERED_RESOURCE_IDENTIFIER>:<RECORD_IDENTIFIER>
The record number that uniquely identifies this record within a registered network resource. The number will be usable as a cross-reference pointer. The use of the colon (:) is reserved to indicate the separation of the "registered resource identifier" (which precedes the colon) and the unique "record identifier" within that resource (which follows the colon). If the colon is used, implementations that check pointers should not expect to find a matching cross-reference identifier in the transmission but would find it in the indicated database within a network. Making resource files available to a public network is a future implementation.

REGISTERED_RESOURCE_IDENTIFIER:= {Size=1:25}
This is an identifier assigned to a resource database that is available through access to a network. This is for future GEDCOM releases.

RECORD_IDENTIFIER:= {Size=1:18}
An identification number assigned to each record within a specific database. The database to which the RECORD_IDENTIFIER pertains is indicated by the REGISTERED_RESOURCE_NUMBER which precedes the colon (:). If the RECORD_IDENTIFIER is not preceded by a colon, it is a reference to a record within the current GEDCOM transmission.

[BEJ]

Thanks. I had found those and was confused. Guess I’ll add permanent record number to the list of unknowns and move on. Unless, you know of a good reason to use them. One online resource suggested they were used by Family Search/LDS.

[Valkrider]

Thanks. I had found those and was confused. Guess I’ll add permanent record number to the list of unknowns and move on. Unless, you know of a good reason to use them. One online resource suggested they were used by Family Search/LDS.

The permanent record number defined in Gedcom and use of a unique id per individual used by various genealogy programs is used to link individuals to families / spouses and to link sources to records etc. there is no need for you to worry about them.

Family Search use a different unique number like G9QF-JJL to refer to a unique individual in their 'world tree' of all individuals.

[BEJ]

Thanks for the info. I’ll move on.

[KFN]

The RFN tag has been deprecated and replaced with EXID in GEDCOM v7.

Defined as "An identifier maintained by an external authority that applies to the subject of the structure."

Basically, Any record type (INDI, FAM, SOUR, etc) can have an EXID, if an external authority has created that permanent number or identifier to a an instance of one of these record types (A specific Person or Family) then you would provide that Identifier and who used that identifier.

It could be used for genealogy societies that number individuals or families that all members uses to refer to and identify their ancestors. A Source Book could have a permanent number ( International Standard Book Number (ISBN)) that could go here.

Probably not very important for 99% of users!

[BEJ]

Ah ha. And now we just need to wait for v7 to become commonly adopted. Thanks.

[AdrianBruce]

Ah ha. And now we just need to wait for v7 to become commonly adopted. Thanks.

Not to mention someone taking on the role of creating these EXIDs...

[KFN]

Ah ha. And now we just need to wait for v7 to become commonly adopted. Thanks.

Not to mention someone taking on the role of creating these EXIDs...

The EXID concept is used in several places in V7. The best example is the suggested requirement for App creators to provide an EXID when they implement a custom tag! Thus telling other Apps where to find a definition and use for their custom tag. I hope these get used in the future!

[AdrianBruce]

... The best example is the suggested requirement for App creators to provide an EXID when they implement a custom tag! Thus telling other Apps where to find a definition and use for their custom tag. ...

Oh that would work - not a difficult workload and useful.