* FindMyPast Hints

[gerrynuk]

I still cannot see a way to reject FMP hints from data sources outside the UK which are not covered by my FMP UK sub. I raised the problem with FMP but they claimed it was a matter for Calico Pie. Does anyone know if Calico Pie is working on a solution?

It is particularly problematic for ancestors with common surnames, where similarly named people pop up all over the world, creating hints that cannot possibly be correct but which I cannot reject and are now clogging up the "hints" screen.

[tatewise]

Only Calico Pie know if they are working on it, because they do not divulge their planned updates to anyone.

If you have not already done so, then report the problem to Calico Pie Support.
The more complaints they get the more likely they might fix it.

[gerrynuk]

Will do, Mike!

[Jane]

My understanding is that part of the function is entirely within the Find My Past Web site, so it would be better to raise the issue with FMP, I know Calico already have, but if enough subscribers complain directly to FMP it might help the cause.

[tatewise]

This topic has been raised more than once, but as far as I can recall, Calico Pie have never provided any advice about the best way forward for users with only a regional subscription rather than a World subscription. Perhaps Simon could give us some clues to possible solutions, such as complaining to FMP.

[gerrynuk]

When I previously raised the issue with FMP I was not really surprised that they tried to put the pass the buck back to Calico Pie although I agree with Jane that FMP must be involved as it is their data - both genealogical and subscription - that is part of the problem. In any event, FMP must be part of the solution even if they reject any responsibility for the problem.

[Valkrider]

I suspect that FMP only have one API, makes sense as it is easier to maintain, and that is on all records in their dataset. Also about a year or so ago they brought all their separate country infrastructure into one master for all their countries and then an individuals login is what allows access to individual datasets. The API probably is not as sophisticated as the browser based login system.

I, personally, doubt that this is a Calico Pie issue and it is an FMP one and perhaps they are trying to encourage us all to take out a worldwide subscription.

[tatewise]

Another mystery is the 'hints' cache held in the Project data that is in format only understood by FH.
If all the management of Accepted/Rejected 'hints' is performed by FMP, what is in the 'hints' cache?

[Valkrider]

Mike

I wonder if the API is really dumb and if FH is required to send it accepted and rejected hints when the hints are requested through the API. To me this would make sense in that it requires the calling application to store that sort of data and transmit it when it calls the API. It is how I would code it anyway but until we can see exactly what the FMP API requires then it is purely guesswork.

[tatewise]

Colin,
The FMP API is documented here http://api.findmypast.com/docs/hints-api.
It seems that the basic response gives counts for Rejected, Accepted, and New, presumably maintained by FMP.
However, there is an option to Update hint status that perhaps FH could use to set 'hints' according to a user request.
Then users could apply that for World 'hints' they cannot access.

This is all part of why it would be useful if Simon Orde of Calico Pie could give some hints on what is feasible.

[AdrianBruce]

Not sure how useful this is but I've tried to put my thoughts down. They may replicate yours or be off-beam.

... what is in the 'hints' cache?

I just accepted and rejected some hints, closed FH, then deleted my hints cache (I don't make much use of this, so no sweat. Your mileage may vary). When I opened FH again, the accepted and rejected hints were back. So "clearly" the results of the hints acceptance / rejection are held in that cache.

Note I don't understand the purpose of that Update Hint Status option in the API. It seems odd that this API allows hints to be rejected if the rejection is held in the cache. However, the documentation says, "This endpoint can be used if you wish to handle the displaying and categorising of hints rather than using our Hints UI". I think FH uses the FMP Hints User Interface, so this option may not be relevant.

Looking at what happens on screen, I get the impression that all the actions after clicking the number of hints on the FH focus screen take place in FMP code - presumably the FMP Hints User Interface. This FMP UI goes continuously through to the accept / reject this hint options, which take place after the detail of the hint has been displayed (which, of course, is when the subscription issue appears). (I don't see any option in that API to specifiy the subscription to be used).

So for what it's worth, I think only FMP can break into that chain - either that or Calico Pie have to provide their own method of "displaying and categorising of hints" rather than using the FMP Hints UI. Which is a big job, probably.

So either FMP or Calico Pie could fix this (plenty of opportunity there to says that it's the other guy). Maybe... And since I'm not really au fait with the type of documentation in the API any more, it would indeed be useful to get Simon's comments on this, so we understand the scale of the job.

[DavidNewton]

Just for the record the FMP hints via RootsMagic work in the same way - apart from the fact that RootsMagic uses your browser and not an internal browser.

David