Nicola

Whilst FH lets you enter Q1 1882 as a date it doesn’t store it that way – it stores it as bet jan 1882 and Mar 1882 – the program does the conversion

If you can post here what it actually shows, we can probably give you a better idea of the way to solve it

Regards

John Hanson FSG

Nicola

I should also, of course, pointed you to the article in the Family Historian User Group article on importing from any product including Rootsmagic

Importing to Family Historian – Family Historian User Group – Knowledge Base (fhug.org.uk) – select Rootsmagic from the list at the bottom

Did you know that you can now do a direct import from Rootsmagic which might solve some of your issues

Regardss

John Hanson FSG

Nicola

I have been reading the details in the FHUG and it strongly recommends the direct import rather than Gedcom so as to avoid missing information, etc that Rootsmagic might not include in the GEDCOM

Regards

John Hanson FSG

There is also a plugin that will convert RM dates to FH ones. It works well as that is how I transferred my RM data a couple of years ago.

David

David

Thanks for that – however that was last updated in March 2021

Version 7.0.8 was released later in the year and introduced the direct import which also resolved a number of the issues raised elsewhere
If you still want to import via GEDCOM (not the recommended route) then the plugin might still be relevant

Regards

John Hanson FSG

Katrina,

The ‘Search and Replace’ plugin should be able to convert such “Q1 1875” date phrases to genuine BET JAN 1875 AND MAR 1875 dates that optionally get displayed by FH as Q1 1875.

It is a little complex as it involves Lua Patterns to perform the bulk conversions.

Would you be interested in how to do that?

Katrina,

Use Tools > Plugins > Plugin Store… to download and install the ‘Search and Replace’ plugin.

Run the plugin and set the following options as shown in the screenshot below.

Leave the Search Scope at All Records & Events/Attributes.

In the Basic Filters ensure only Date fields is ticked so changes are focussed on them.

In the Search Criteria select LUA Pattern Mode so that wildcards for year digits are enabled.

In the Search box enter “Q1 (%d%d%d%d)” to match the Q1 date phrase where (%d%d%d%d) captures the year.

In the Replace box enter BET JAN %1 AND MAR %1 to substitute the Date Range for Q1 in the captured year.

Click the Search & Replace button, untick Confirm every item found and click Replace.

That should produce a Result Set listing all the changes.

Repeat that process for Q2 with APR & JUN, Q3 with JUL & SEP, and Q4 with OCT & DEC.

Eric,

The FH/GEDCOM formal format for a Date Range is BET <date> AND <date>.

However, FH is quite tolerant and accepts BET, BTW, BETWEEN, etc, in uppercase or lowercase when dates are entered.

Yes, FH displays a Date Range in lowercase as btw <date> and <date>.

If Tools > Preferences > General ‘Use quarter date display format’ is ticked then certain Date Ranges are shown in Qn yyyy format.

That is what is happening with your BET JAN 1875 AND MAR 1875 example (if you untick the quarter date option it displays btw Jan 1875 and Mar 1875).

But they do not affect the underlying GEDCOM Date format and are very different from a Date Phrase which is enclosed in “quotes” such as “Q1 1875”.

Thanks for letting us know Nicola

Regards

John Hanson FSG