I would find it useful, when constructing queries and customising column headings (and also for occasional manual edits to the GEDCOM), to be able to relate a piece of displayed data to the internal ways in which that data is identified. Let me try and explain this idea with an example.
In an individual's Property window, there's a pair of fields 'Born ____ in ____'. If I right-click in either of those fields, I currently get a pretty obscure set of choices ('open IME', anyone?). What I'd like to see is an additional choice, let's say 'About this data'. So if I selected that for the birthplace field, FH might tell me some or all of:
- the GEDCOM spec description of this field's purpose
- the GEDCOM storage form, and its approximate location in the file. For example:
Around line 12345:
01 BIRT
02 DATE xxx
02 PLAC xxx
- the FH way of referring to the data. For example:
INDI.BIRT.PLAC
- anything else that might be helpful.
ID:5245
* Explaining where data comes from
-
RogerF
- Famous
- Posts: 182
- Joined: 26 Apr 2009 16:32
- Family Historian: V6.2
- Location: Oxfordshire, England
- Contact:
Explaining where data comes from
Roger Firth, using FH to research the FIRTHs of Lancashire and Yorkshire, and the residents of the market town where I live.
-
Jane
- Site Admin
- Posts: 8441
- Joined: 01 Nov 2002 15:00
- Family Historian: V7
- Location: Somerset, England
- Contact:
Explaining where data comes from
The best location to find out about fields is the Columns tab on the Query window which gives you details of every field just select the field and check the bottom of the column for the description.
Those fields are Windows standard ones I think.
I suspect when a gedcom file is loaded in to memory there are no line numbers associated with the data.
On the Customise Property Tab you can already see the Data reference for the field and in most cases you can infer the gedcom structure from that.
Those fields are Windows standard ones I think.
I suspect when a gedcom file is loaded in to memory there are no line numbers associated with the data.
On the Customise Property Tab you can already see the Data reference for the field and in most cases you can infer the gedcom structure from that.
Jane
My Family History : My Photography "Knowledge is knowing that a tomato is a fruit. Wisdom is not putting it in a fruit salad."
My Family History : My Photography "Knowledge is knowing that a tomato is a fruit. Wisdom is not putting it in a fruit salad."
-
Jane
- Site Admin
- Posts: 8441
- Joined: 01 Nov 2002 15:00
- Family Historian: V7
- Location: Somerset, England
- Contact:
Explaining where data comes from
Roger, you have not responded on this do you still want it added?
Jane
My Family History : My Photography "Knowledge is knowing that a tomato is a fruit. Wisdom is not putting it in a fruit salad."
My Family History : My Photography "Knowledge is knowing that a tomato is a fruit. Wisdom is not putting it in a fruit salad."
-
RogerF
- Famous
- Posts: 182
- Joined: 26 Apr 2009 16:32
- Family Historian: V6.2
- Location: Oxfordshire, England
- Contact:
Explaining where data comes from
Yes please, Jane. I'm looking for a set of broader and more consistent data descriptions than the options you mention.
Roger Firth, using FH to research the FIRTHs of Lancashire and Yorkshire, and the residents of the market town where I live.
Explaining where data comes from
WL#495 has been raised for this wish
Please vote for it here:
http://www.fhug.org.uk/wishlist/wldispl ... lwlref=495
Please vote for it here:
http://www.fhug.org.uk/wishlist/wldispl ... lwlref=495
-
PeterR
- Megastar
- Posts: 1129
- Joined: 10 Jul 2006 16:55
- Family Historian: V7
- Location: Northumberland, UK
Explaining where data comes from
I have a V5 Plugin which shows all of the data references for any selected record. I can submit this to the Plugin Store if anyone is interested.Roger Firth said:
- the FH way of referring to the data. For example:
INDI.BIRT.PLAC
Peter Richmond (researching Richmond, Bulman, Martin, Driscoll, Baxter, Hall, Dales, Tyrer)