* Property window unsourced facts

[laz_gen]

I am currently reviewing my file looking for unsourced facts from previous imports. I am navigating up and down through families looking at the property window facts recorded for each individual.

What I would like is to immediately see from the property window which facts have sources and which do not but can't see any way to configure that. I see a "More" column that shows various icons for image, note and witness but nothing to show the presence of a source.

I realise I can have the source window open and select each fact to see if a source is present but some individuals have a great many facts and that involves a lot of clicking. An overview would be much better.

I could probably write a query to search for unsourced facts but that would give me results not necassarily related to the family structure I am presently following.

Is there something I am missing?

[tatewise]

Start with the FHUG KB Download Unsourced Facts Query.

Then add a Rows tab filter that prompts for say an Individual record (or perhaps a Family record).
The filter would only include matching Individual owner records.

If the prompt were for a Family record then the Husband, Wife, and Child links would filter to include all matching Individual records as well as the Family record itself.

[laz_gen]

I take it then that there is no means to display fact source status in the property window, as per the first part of my question. A shame because I think that would be very informative as an overview.

A suggestion for the wish list perhaps?

Thanks for the pointer to the query, I am exploring that now.

[tatewise]

Sorry, I should have confirmed that there is no way to customise the More column.
Yes, that might be a reasonable Wish List request.

I have just thought of a workaround prompted by the FHUG KB new article Entering Standard and Custom Fields for Facts which explains how to customise the Facts tab to show various data fields under Show Fact Fields in the Property Box.

The idea is to prefix each fact with + or - or whatever text indicators you prefer, depending on whether it has a Source Citation or not.

At the start of each Summary Template use something similar to the following expression:
{=TextIf(Exists(%FACT.SOUR%),"+","-")} you can choose whatever text indicators you prefer.

Follow that with the name of the fact and {place} code so that for the Birth Event the whole Summary Template is:
{=TextIf(Exists(%FACT.SOUR%),"+","-")} Born {place}

[laz_gen]

Mike

That is an excellent solution.

I have just tailored about 10 of my most used facts and the property box now clearly shows those facts with a source and those without.

Incidentally I chose this symbol "§" to represent the presence of a source as it is just a little bit bigger and easier to see.

Shame this method is limited to text characters as a real icon would be that much better.

I will raise a new wish list posting for an icon in the More column to represent sourced facts.

Thank you

[jimlad68]

At the start of each Summary Template use something similar to the following expression:
{=TextIf(Exists(%FACT.SOUR%),"+","-")} you can choose whatever text indicators you prefer.

Yes, works a treat, I suppose it could be extended for other items like PLACe.

Certainly worth adding to the wish list in the "More" column, especially as the "More" column already includes "notes" and has space left for another 3 icons.

To speed the process up I took a backup of C:\ProgramData\Calico Pie\Family Historian\Fact Types\*\*.fhf, then edited the original *.fhfs directly in Notepad++.

[tatewise]

Yes, works a treat, I suppose it could be extended for other items like PLACe.

The PLACe value is usually included by default or by using the {place} code so why would an indicator be necessary?

[jimlad68]

The PLACe value is usually included by default or by using the {place} code so why would an indicator be necessary?

Yes, I often use the {_place} in the Advanced Summary template, but the box is often not wide enough to includel the detail, especially if using FH on just 1 screen. Additionally a marker/icon is a quick reference for that fact.

Dependant on the fact, In the Advanced Summary template I might also add the {note} or {%FACT.SOUR[1]>TITL%}: {%FACT.SOUR[2]>TITL%} : {%FACT.SOUR[3]>TITL%} : {%FACT.SOUR[4]>TITL%}, although the SOURce is overkill, some facts might just have little else than a source.

[laz_gen]

I made another edit to my Facts along the way.

When I edited my Occupation fact I added {value} to the end of the line so now the stored occupation shows in the list of facts in the property window.

{=TextIf(Exists(%FACT.SOUR%),"§","-")} Occupation {value}

I have also added the {address} term to the end of my Census and Residence Facts so the property window is now looking very good with lots of useful information on show as an overview.

[ADC65]

I made another edit to my Facts along the way.

I might be misunderstanding what you are describing here, but don't these lines already show their values in the property box?

Screenshot 2023-01-14 102034.jpg (40.41 KiB) Viewed 1253 times

Edit: I now see you have added Address rather than Place so I can see this would add extra information. But occupation?

Any chance you could attach an example screenshot as I'm interested in trying some of these.

Thanks

[tatewise]

Adrian, yes, certain fields are shown by default in the top pane of the Facts tab.
For Events the Place is shown and for Attributes the Value is shown but not the Place and never the Address or Cause.

However, here we are discussing customised Summary Templates which must specify explicitly all the fields to show.
So if only {=TextIf(%FACT.SOUR%,"§","–")} is specified then only one character § or – is all that is shown.
It must be supplemented with the name of the Fact and codes like {value}, {place}, {address}, etc, for them to be shown.
e.g.
{=TextIf(%FACT.SOUR%,"§","–")} Occu. {value} {address} {place}
i.e. Very similar to Sentence Templates.

See FHUG KB Entering Standard and Custom Fields for Facts especially under Show Fact Fields in the Property Box.

[ADC65]

However, here we are discussing customised Summary Templates which must specify explicitly all the fields to show.

Thank you Mike, that is the bit I missed

I did read the article yesterday, it's very informative and clearly explained, I will be having a go at implementing some of the techniques later.

[laz_gen]

I was hoping to extend this a little more with another condition.

{=TextIf(Exists(%FACT.SOUR%),"§","-")} Born {=TextIf(Exists(%FACT.ADDR%),{address},{_place})}

I am trying to test for the presence of an Address and if found display it, if not, then display the Place instead.

I can't seem to get this to work so wondering if more than one condition is allowed, or maybe I have the syntax wrong.

[tatewise]

You cannot use codes like {address} and {_place} inside functions.
See Wish List Ref 577 Sentence Template Functions to Replace Codes.

You must use %FACT.ADDR% and %FACT.PLAC% instead just like you did in the Exists(...) function although that function is not strictly needed.
e.g.
{=TextIf(%FACT.SOUR%,"§","-")} Born {=TextIf(%FACT.ADDR%,%FACT.ADDR%,%FACT.PLAC%)}
or
{=TextIf(%FACT.SOUR%,"§","-")} Born {=CombineText( ,%FACT.ADDR%, ,%FACT.PLAC%)}

[laz_gen]

Thanks again Mike, I was close but again fell foul of FH wierd ways of doing things. Works now as I would like.

I have only been using FH for a few years so have no historical experience of the program in its earlier stages but have been trying to form an understanding of how things work under the bonnet regarding functions and expressions.

I picture FH to have a "expression interpreter" that takes expressions like {=TextIf(%FACT.ADDR%,%FACT.ADDR%,%FACT.PLAC%)}, decodes them, and fetches the appropriate data items from the database.

Perhaps in an earlier release of FH there was a need for users to customise the sentences in their reports so CP created a "pre-processor" designed to process a set of user friendly alias commands {in curly brackets} and translate them into raw expressions that could be sent to the real expression interpreter.

This would translate, perhaps using a look up table, user friendly commands like {address} and translate them into %FACT.ADDR%

So your wish list request Ref 577 is for the "pre-processor" to be abandoned and only full expressions are to be allowed for tailoring the sentence structure.

Personally I think that would be a backward step removing a user friendly feature however if the pre processor were able to identify "full expressions" then it could pass them directly to the expression interpreter while also intercepting those sentence commands in curly brackets and translating them before passing them on.

In that way sentences could continue to be tailored using the sub set of curly bracket commands but users wishing to go a step further making more complicated sentence modifications would be able to build their sentences using the full set of data references.

[tatewise]

I don't have any problem with retaining the {codes} which would be necessary for backward compatibility anyway.

[RS3100]

Perhaps in an earlier release of FH there was a need for users to customise the sentences in their reports so CP created a "pre-processor" designed to process a set of user friendly alias commands {in curly brackets} and translate them into raw expressions that could be sent to the real expression interpreter.

I still customise many of the fact sentences in my project, both by editing the sentence templates and by editing or suppressing individual fact sentences. It allows me to include information that the default settings miss, avoid repetition and generally make the overall flow and appearance of reports less "robotic" than is otherwise the case. I would strongly protest at any attempt to remove that functionality!

[tatewise]

See New Wish List Request forum Property box icons (21446) posting that has led to the new Wish List entry:
Ref 593 Property Box, Facts tab, More column features.