RootsSearch and more recent profiles - tweak for private view?

Question

I do enjoy the RootsSearch link!

A minor suggestion which would make life easier perhaps - though I do know the same link is in the Research tab - or so I understand.

When I find an unsourced profile for a person born in the 20th century (I don't know the cutoff or maybe it relates to whether the profile is open and not to the date of birth?)) - most such profiles don't offer the RootsSearch link, presumably to discourage searching on living persons or close relations of living persons.  (Just my guess!)

I suggest that we could include the link on the "private" view if we don't want to allow it on the public view for those profiles that don't allow the link.

Is this technically easy to accomplish? Would it conflict with some policy?

(Not sure whether this is a policy or a tech matter?)

Answer 1

> I don't know the cutoff or maybe it relates to whether the profile is open and not to the date of birth?

Yep, its totally dependent on the privacy settings of the profile, regardless of date of birth

Comments

Thanks Dennis, that clarifies the trigger.  I think it would still be of use to have the link appear on the private view.

---

Oh, I see what you mean... not sure that's even possible. Right now, the code can only search public profiles for comparison to the other sites.

---

I would assume - since one is logged in already - to  wikitree and potentially the external site ... let's say familysearch (where I do most of my searching now), that it's just pulling that visible data into the form.  If you are logged in you would already be viewing it if you had the rights (trusted list or manager) - it wouldn't breach security and doesn't transfer the data to the other site, it just gets it read for you to search the other site.

Answer 2

If you use RootsSearch a lot and would also like to use it on other websites then you might consider installing the RootsSearch Chrome Extension. The extension will work on any profile you can see. That's because it scrapes the website. The RootsSearch WikiTree app functions differently in that it uses the WikiTree API so the two might produce different results.

Comments

Thanks for making me aware of that extension.   I fear my browser and laptop are reaching their limits on extensions, but I am eager to check it out.  :)

---

Hmm - I will need to check if there is more than one extension -- the one I loaded seems to act like a book mark and doesn't populate the search fields.