* Records Window

[Ron Melby]

As always, I am sure this is covered somewhere, but having read all the knowledge base, and searched the forums, my head is too full or I missed it, or I have unusable search skills.

I am on the records window.

Indi>Fam>Note>Sour>Repo>Subm>Plac>Head

(written out) those are the tabs available to me.

here is a place record.
[P1576] (WW1)
Text: (WW1)
(that is a paste from the clipboard)
obviously a military attribute and not a place.
I would like to fix that, so I click on the record, and am taken to that unlinked record. I go nowhere. I can fix the text of that record, but cannot get to the underlying INDI record which is what I want.

Am I missing something, or must I write a query to accomplish this?

[tatewise]

Ron, firstly you have not got all the Records Window tabs shown. (Submission & Media missing)
See how_to:key_features_for_newcomers|> Key Features for Newcomers under how_to:key_features_for_newcomers#records_fields_multimedia|> Records & Fields & Multimedia.

If as you say it is an unlinked Place record with its Links entry 0 then it has no underlying Individual record.
So you can simply delete that unused Place record.

Otherwise, the way to find its parent record is the same as in your previous @NOTEPOINTER@ (15490) posting.
i.e.
Use the View > Record Links command or run the Where Used Record Links Plugin.

[Ron Melby]

Yes, exactly what I thought. (it is linked to one record) So, I will make queries for all the tabs, which to me is a strange situation.

[tatewise]

Ron, not sure what you mean by "make queries for all the tabs".

No Queries need to be harmed in the execution of this thread

Did you find the parent record of the WW1 place?

[Ron Melby]

I will make a query for each type of tab. One thing I will need is line number. Since most are unfixable in the program.

these are just a few of my problems
1 OCCU
2 DATE 1881
2 PLAC Mariner

The one I talked about at the outset

*1 whatever
*2 whatever
2 PLAC 1DB8-F7
* I say whatever because I cannot get back to the record from the Places tab to the Indi.*whatever*.plac. like I can in a query
One thing I will need is line number. Since most are unfixable in the program. Then I can go directly to the line number and fix it.
I have fixes in sources, as well typical situation, I may have 7 children on the 1820 source, and 5 on the 1830 source, What happened to the children in the 1830 source? That has a plugin that does that, so that helps. The where used might work ok, with some more fixing, because I can only have one record at a time. I want 1 AFN but cant seem to see how to get that thru the software. Additionally when going thru events in detail to make my query for them remember where I wanted a contains clause?---- I saw ROLE and under that MDCL, but cannot see how to make that tag sequence

If I put 1AFN in the file by hand, it works correctly and FH displays it correctly. So..........

[tatewise]

I have some advice regarding some of your comments.
You need to spend some more time learning how use all the FH features.

You say: "Since most are unfixable in the program".
However, most will be fixable in FH but may need a Plugin.
Your example of an OCCUpation fact where the PLACe Mariner needs to become the Occupation is certainly fixable within FH.
Just Copy & Paste the text Mariner from Place: box to Occupation: box.
Then delete the text Mariner from Place: box.
That is quicker than trying to edit the GEDCOM file line by line.

You can get back to whatever from the Places tab by using the Where Used Record Links Plugin.
You can also use the Tools > Work with Data > Places > Where Used button, but only one Place at a time.

You say: "The where used might work ok, with some more fixing, because I can only have one record at a time.
The Where Used Record Links Plugin allows any number of records to be preselected and all will be traced back to their parent record or fact or whatever in the Result Set.
If you start with no records selected, that Plugin will prompt you for your selection.

You are correct that after adding an AFN via the All tab right-click Add Miscellaneous > Add Automated Record Id the program does not allow a value to be entered.
But you can use Add Miscellaneous > Add Custom Id and Add Miscellaneous > Add Permanent Record Number so why is AFN so important?
GEDCOM defines AFN Automated Record Id as "A unique record identification number assigned to the record by the source system." which is why FH does not allow users to add it.

ROLE under MDCL is the Role of a Fact Witness linked to MDCL fact.
Fact Witnesses are added to facts in the Facts tab by right-click Witnesses > Add or in the All tab right-click Add Witness.
However, 1 MDCL is not a valid GEDCOM fact tag, so I suspect it has been imported from some other product (FTM?).
It is shown with a star bullet in the All tab to show it is an Uncategorised Data Field (UDF).
They can be fixed as explained in how_to:handling_unrecognised_data_fields|> Handling Uncategorised Data Fields (UDF) and in this case the Change Any Fact Tag Plugin can fix it, but you will need to understand the workings of standard and custom facts and UDF. Possibly the Extended Set custom fact Medical Condition would be appropriate.
If I am correct that it came from importing from another product, then I advise you study how_to:index#importing_to_family_historian|> Importing to Family Historian.

[Ron Melby]

No, it is not quicker than editing line by line, FH "edits" line by line. (I don't edit line by line) I can search for and replace those quicker than anything I can do in FH. 4 keystrokes per fix. I dont know LUA yet, but in RPGs I could write the fix in less than 5 minutes, I expect when I learn the language it wouldnt take long to write the code either. If OCCU is *LANK and whterh or not there is date and PLAC is not *BLANK and does not contain a comma, move plac to occu and delete place.

It is cumbersome to do anything in FH of the nature of fixing. Fixes are not something FH works well at.


I also have to say that OOOps, FH does not handle AFN correctly, but at least it doesnt mess with it too badly. But it does so in a non-standard way.

[DavidNewton]

I think there is some confusion here with AFN = LDS Ancestral File Number and RIN = Automated Record Number. Either or both can be added via the All tab as long as there is not an occurrence there already and either can be edited in the All tab by right clicking and editing the field that shows up. I would like to know how FH fails to correctly handle the LDS Ancestral File Number.

Also, if extensive use is required, either or both numbers can be exposed as editable fields on the main tab of the property box

David

[Ron Melby]

Yes, thats well hidden isnt it, David? LOL. Thanks.
It would be nice if all the tags could be in the add fact screen, much less running around, and all the facts could be configured from the tools>fact type screen. I can add AFNs considerably faster in editpad.

**Also, if extensive use is required, either or both numbers can be exposed as editable fields on the main tab of the property box
I read a great deal in the knowledge base and these forums (nearly a years worth, before my first post) I dont see how to do that. There is a great deal I would expose and a great deal I would hide in facts, and in that vein, I saw a deal by Jane where there is this property box modifier (it did military tab and some others) well, I tried to figure out how to work that, but it led me in circles. It is not intuitive. I dont see how there is muchto edit in the property box, I go to tools>preferences>property box. If there is some other non-centralized functions for this, I would certainly love to be enlightened on where those directions and instructions can be had.

tatewise: the reason that 1 AFN yadda yadda is important is because FamilySearch uses that to find records. Far superior to MyHeritage and FindMyPast, and most importantly, free.
My reading of pages 25 and 38 in the standard differs from your statements,

Thank you both tatewise and David.

[DavidNewton]

I'll try to answer the customization question.First click the cog menu at the top right of the property box

SettingsMenu.JPG (22.12 KiB) Viewed 9070 times

Selecting Customize data entry leads to

CustomisePropertyBox.JPG (62.47 KiB) Viewed 9070 times

I have already added a custom item "Numbers". If you want to add a new one yourself then uncheck 'Show most commonly used... and the top item in the bigger list is then <custom item> (for advanced users). Back to Numbers. Select and Edit Custom Item gives this

PropertyBoxCustomItem.JPG (62.17 KiB) Viewed 9070 times

This shows as two items in a row and the Data Reference is easy to add via Select which gives you the data tree. Once you have the basics play with it to select what suits you best.

The other tabs that can be edited come from the Tab Dropdown at the top of the Customize Property Box window.

David

[Ron Melby]

That is a great help, I can do place names at quite a good clip now.

Uhhhhhhhhhhhhhhhhhhhhhhhhhhhh how do I get the data assistant window up again?

I have saved this thread (as I have most I have been in on, and some others,0 LOL.

[DavidNewton]

In the edit custom item screen click the Select button at the right end of the field box.

David

[tatewise]

I apologise for confusing the LDS Ancestral File Number (AFN) with the Automated Record Id ~ mea culpa.

Customising the Property Box is introduced in the book Getting the Most From Family Historian in Chapter 2. Editing Records with the Property Box at about page 26.

Sorry, but you did not specifically say you wanted a bulk programmable solution for the Place to Occupation fix.
If you ask nicely on this Forum, then the more expert users are often able to write a Plugin for you.

There is a common misconception of what is formally known as a Fact in GEDCOM and what is not.
Events and Attributes such as Birth, Death, Marriage, Census, Occupation are Facts that all support the same sub-fields of Date, Age, Place, Address, Note, Cause, etc, and such Facts are all configured via Tools > Fact Types.
Whereas, the LDS Ancestral File Number is not a Fact according to GEDCOM and is therefore handled differently.

Did my explanation of ROLE under MDCL help at all?

It is quite difficult to respond quickly to a posting that has so many different threads.
It would be easier to deal with each issue separately.

[Ron Melby]

Yeah, the 1 MDCL fact tag, dont know what that is.

I dont see MDCL in the GEDCOM standard yet. But way back when in the custom stuff....
it was used like this:

2 CAUS cakked from cancer.
2 MDCL diabetes.

so usually CAUS was immediate and MDCL was where the secondary went

The trouble is, and let me remind everyone, I am trying to fix several GEDCOMS from different sources, different releases, different lengths of time being built, now, they have lots of junk ways that they thought were cute at the time.
1 CENS
2 DATE 1881
2 PLACE John was widowed, and in the house were Mrs. Jimmy Seville widow, and her three children John Thomas (7), Cloth Ear, (13) and Fred, Jr. (2). He was an Out of Employ, greengrocer.

and consider any lousy thing you really don't want to happen, its in there. I am trying to get them from junk to eminently portable across softwares. And hopefully, when they go into book form, they will flow pretty nicely.
Here is a situation I am going to be grappling with...
I have a general event....
1 EVEN
2 TYPE NEWS
2 SOUR
3 PAGE
2 NOTE

Same standard event for OBIT
in these events go newspaper articles.

Now, I am hoping that in this thread was the seed of a plan in which I can put some of those news events by changing them to say WED type, in the marraige record, so the wedding announcement and the golden anniversary announcement and the like can be with the Marriage.

And the standard places horrid restrictions, linear complex events would be nice:
1 _ATTR WWI, US NAVY, MMO2
2 TYPE MILT
1 EVEN
2 TYPE MILT
2 DATE 12/21/1943
3 PLAC France
2 NOTE Battle of the Chavs
2 DATE 12/24/1943
3 EVEN MILT
4 CAUS fell off a bridge and tore hip
4 MDCL lost arm in the fall
or some such nonsense
But the EVENT type will not 'include' the attribute.

but I can do multiple EVEN MILT(s)
the ATTR is a searchable way to find the war, the branch and several other things
the EVEN is easier to port.
and there is no way to link them, that is, if I have those two things, no matter when they are added, they clump in that order.

Your answer helps, tatewise, in that it is now a road I probably wont go down. have to figure out how to handle MDCL.

[tatewise]

If you want the GEDCOM to be "eminently portable across software" then you will have to confine your data to a subset of GEDCOM 5.5 & Draft 5.5.1 that is well supported by many products, and will be very restrictive.

Study the plugins:help:export_gedcom_file:export_gedcom_file|> Export Gedcom File Plugin conversions needed for each Product as described in the plugins:help:export_gedcom_file:output_formats|> Export Gedcom File ~ Output Formats and you will see what I mean.

[Ron Melby]

Oh, yeah, the struggle is real.