* creating a file for Ancestry with no facts for living individuals

[tatewise]

FH supports the standard PEDI tag for the standard Adopted, Fostered, Illegitimate, etc, options.
The custom _PEDI tag offers the separate relationships to just Father and just Mother.

Unfortunately, the Plugin change is a bit more complex than that.
Those lists you considered identify first each record type INDI, FAM, SOUR and secondly level 1 tag to delete SOUR, SOUR2.
Whereas, this one is in an INDI record, in a FAMC level 1 tag, and then multiple instances of the _PEDI subsidiary level 2 tag.
There is no mechanism in the Plugin to handle that level of nesting at present.

[BillH]

Mike,

Are you willing to make that type of change to the plugin with a little begging on my part? If so there is no hurry.

As to what to remove, I see things like this in the GEDCOM where each seems to apply to just the father or mother:

1 FAMC @F1827@
2 _PEDI Adopted (father)
2 _PEDI Birth (mother)

But I also see these:

1 FAMC @F2797@
2 _PEDI Illegitimate

and

1 FAMC @F5019@
2 _PEDI Step

where they don't say they are just for the father or mother. I'm thinking they too will result in a Ω record being created which is what I don't want. Maybe I should just say i want to eliminate any child relationship that results in Ω record.

Thanks!

[davidm_uk]

I've been following this thread with interest (although not understanding some of it) and didn't wan't to butt in for fear of confusing things.

I certainly hope to use it, and will give it a try once the development has settled down. I'm sure that with all of the options I'll be able to make use of it.

Bill, are you planning on updating your procedures document for the whole process?

[tatewise]

I have redesigned the Clean Ancestry Fields Plugin and renamed it Clean Unwanted Fields Plugin Version 0.2 Date 05 Mar 2017 as attached.

This version allows the user to simply edit the Plugin to adjust the Data References to be removed.
If either of you would care to experiment with it, then give it a go.

@Bill, regarding the PEDIgree tags, you are correct in that some both parent values use the _PEDI custom tag.
This has revealed another FH anomaly, where although both PEDI and _PEDI tags appear in Gedcom files, only PEDI ever applies via the FH Plugin API. So in Clean Unwanted Fields all PEDIgree fields are removed of both flavours.
(Export Gedcom File works directly on the Gedcom file so can process PEDI and _PEDI differently.)

@David, the procedures document has been captured in essence in how_to:exporting_gedcom_with_multimedia#export_to_website_without_sensitive_data|> Export to Website Without Sensitive Data unless Bill thinks otherwise. If there is a need for more specific details for particular websites, then that KB page can have subsections for those specifics, but a lot of the choices are down to personal preference, trial & error, and what you consider as sensitive data.

[ATTACHMENT deleted as now in Plugin Store.]

[BillH]

David,

Yes I will post my latest when I've got it completed. The KB is good, but I like to have a step by step detail of exactly what it is I'm going to do.

Mike,

Thanks so much. That's fine on the PEDI records. I don't need them anyway. I'll download the plugin and run it through it's paces a bit and let you know what I find.

Thanks again.

[tatewise]

David, may I suggest you create your own detailed step by step guide derived form the KB, because the fields you wish to exclude/include may well differ from Bill's, depending on what information you put where, whether you have used [[private text]], and used Private and Living flags, and how you wish to handle people with no birth & no death dates , etc, etc.

[BillH]

Mike,

I tested the new plugin, Clean Unwanted Fields, and it works great. The exact same number of items were removed using it as were removed with Clean Ancestry Fields (after I commented out the PEDI line). I put the PEDI line back in , ran my entire procedure, and now I have no Ω records in my final file which is just what I wanted. Everything else looks great as well.

I think this version can easily be used by other folks as it is easily tailored to each persons needs. It might make a good candidate to be published in the store along with Clean Living Persons.

David,

I have attached the updated version of my procedure in case you would like to use mine as a starting point. It can be tailored to your specific needs. I will give the warning that as it sits it applies only to me and you would definitely want to go through it to make any changes needed to fit your requirements.

Thanks

[davidm_uk]

Bill,
Thank you. Your warning is noted.

Mike,
Is Clean Living Persons Version 1.2.9 Date 03 Mar 2017 the latest version? Are both of the plugins from this thread likely to find their way into the Plugin Store?

[tatewise]

David, yes that is currently the latest version, and both should find there way into the Plugin Store.
I am discussing with Jane how best to proceed with Clean Living People/Persons.
In the meantime they soon will be available from how_to:exporting_gedcom_with_multimedia#export_to_website_without_sensitive_data|> Export to Website Without Sensitive Data.

Do either of you think these two Plugins need a progress bar?
They both run so quickly that I suspect not.

Attached is a revised Clean Unwanted Fields Plugin Version 0.3 Date 06 Mar 2017.
This now allows whole records to be deleted (the previous version lacked that ability).
If any Data References are unused/illegal they are listed with the final confirmation message.

[ATTACHMENT deleted as now in Plugin Store.]

[BillH]

Mike,

As far as I am concerned, no address bar is required. They do run very quickly as you say.

By deleting a whole record, do you mean deleting an Individual record and all its sub-records?

How would you delete an entire record. What would you add to the list of things being removed? Would an example in the comments be good?

Thanks!

[tatewise]

Records are what are listed in the Records Window, i.e. Individual, Family, Note, Source, Repository, Media, Place, etc.
The data within records are fields.
So to delete all Repository Records the Data Reference entry would be "REPO"; and for Notes it would be "NOTE"; and I will include an example.
I only added it for completeness, but Export > GEDCOM File and Split Tree Helper can do the same.

[BillH]

Thanks Mike

[tatewise]

Attached is a revised Clean Unwanted Fields Plugin Version 0.5 Date 08 Mar 2017.

I could not rest easy with the manual editing of the Plugin Lua script.
So I have added a simple line editor user dialogue with the Data Reference list saved in a file.
If used in Project mode, where you get the warning, then each Project has its own saved file.
If used in Standalone Gedcom mode as in this topic, then a separate global file is saved.

Please experiment with the editor, and associated error check.
It does not ensure Data References are valid, but does ensure they start and end with % and only use allowed characters.
Invalid Data References will get reported as unused at the end.

[ATTACHMENT deleted as now in Plugin Store.]

[BillH]

Mike,

I ran the new version and it works fine. I think this will be less daunting for some folks than editing the plugin itself.

As for the error checking, I tried a couple of things that didn't error out, I'm not sure if they should have.

1. INDI.FAMC.PEDI% (no % at beginning)
2. @@@INDI.FAMC.PEDI%

Neither of these showed up as unused on the confirmation window either.

Thanks

[tatewise]

As it says in the text above the edit box :-
"Any line that does NOT start with a % percentage character will be ignored."

The intention is that allows any commentary or blank lines to be included.
The initial % is so crucial that my thinking is that it would never be accidentally omitted.

[BillH]

Mike,

Sorry... I mis-read the window text. It is doing just what you said it would.

I have a question. Is the %REPO% line being excluded because of the - symbol in front of the %SOUR.AUTH% line? Is everything following that one - symbol excluded?

Thanks

[tatewise]

No, the space space %REPO% line is excluded for same reason as the tab Excluded Examples line, and the final blank line.
They do NOT start with a % character against the margin!
Perhaps it needs to emphasise the against the margin requirement.

[BillH]

Mike,

I wondered, but I wasn't sure if the % had to be in column 1 or could be anywhere. I think making this clear would be a good idea.

Thanks

[tatewise]

The latest Clean Unwanted Fields Plugin Version 1.0 Date 16 Mar 2017 has now been published in the Plugin Store.

It now automatically adjusts its window height to display all the Data References.
The advice above and below the Data References has been improved.
If everything in Data References pane is deleted then the original Ancestry defaults are restored after pressing Apply Data References.

The how_to:exporting_gedcom_with_multimedia#export_to_website_without_sensitive_data|> Export to Website Without Sensitive Data has been updated.

BTW:
Bill, am I right in thinking that the Family Historian popups for the initial Project Warning and final Please Confirm Changes both appear on your FH monitor, but the main dialogue window appears on your primary monitor?

Following my investigation to automatically adjusts its window height, I think I might be able to get the Plugin to remember its dialogue window position, but not 100% sure.

[BillH]

Mike,

That placement of the windows you describe is exactly what I am seeing.

Bill

[tatewise]

I think I have cracked it, so try these two attachments.

If you drag the main dialogue window to your FH monitor and use the Apply ... button, but then Cancel the changes, the new position should 'stick'. I might be able to get the position to 'stick' even when Closing the main dialogue, but thought best to check the basics worked first.

[ATTACHMENTS deleted as better versions attached later.]

[BillH]

Mike,

On Clean Living Persons this worked as you described if I dragged the window to my FH monitor, clicked on Apply, and then clicked on Cancel. After clicking on Apply the window flashed briefly on the primary monitor, but the confirmation appeared on the FH monitor.

On Clean Unwanted Fields it didn't work. I dragged the window to my FH monitor, clicked on Apply Data References, and clicked on Cancel. The next time I tried the plugin, the main window was back on my primary monitor.

Bill

[tatewise]

I don't entirely follow the 2nd sentence of 1st paragraph for Clean Living Persons.
Are you running on a standalone Gedcom file, or a Project?
On a standalone Gedcom file, when you run the Plugin, the main dialogue may flash on primary monitor and then move to FH monitor.
Are you saying that when you click Apply Rules in dialogue on FH monitor, the dialogue flashes briefly on primary monitor?
The Confirm Changes popup will always be on FH monitor.

I cannot explain why Clean Unwanted Fields behaves differently, as it essentially uses the same technique.
Can you try it again, and double-check it is the version downloaded from here.
BTW: If you run & move it on one Project, then that won't have 'stuck' for another Project, and standalone Gedcoms are separate again.
Each Project has separate sticky settings, and all standalone Gedcom share another set of sticky setting.

[BillH]

Are you running on a standalone Gedcom file, or a Project?

I've tried it on both. In both cases with the primary dialogue window on my FH monitor, I click on Apply Rules and the primary dialogue window goes away on my FH monitor and then flashes briefly on my primary monitor.

Can you try it again, and double-check it is the version downloaded from here.

I am running Clean Living Persons version 1.3.1 last updated 17 Mar and Clean Unwanted Fields version 1.0.1 last updated 16 Mar.

BTW: If you run & move it on one Project, then that won't have 'stuck' for another Project, and standalone Gedcoms are separate again.
Each Project has separate sticky settings, and all standalone Gedcom share another set of sticky setting.

All previous testing was done on the same standalone gedcom. I tried it just now on my main project and got the same results.

Thanks

[tatewise]

Has the Clean Unwanted Fields list of Data References been accumulating a top line such as ScreenPosition=-999,-999?

I discovered that Plugin does not handle negative screen position values in the same way as Clean Living Persons.

Think I have eliminated, or at least reduced, the brief dialogue flash on your primary monitor.

Clean Unwanted Fields now performs a better validity check on Data References and fixes a minor bug.

Try these two attachments :-
[EDIT: Attachments deleted as now in Plugin Store.]