Two questions about browser extensions:
- For users who currently upload data from Gramps to WikiTree via GEDCOM – could/should the WikiTree “Sourcer” browser extension be enhanced to pull data directly from Gramps Web or Gramps Connect?
- Could/should there be a browser extension that goes the other direction, and pulls data into Gramps (via Gramps Web or Gramps Connect) from other sites?
What this extension is: A browser extension that scrapes genealogy record pages (Ancestry, FamilySearch, etc.) and turns them into citations and profile data formatted for WikiTree.com. It has no connection to Gramps currently. Scraping is hard, and a moving target. But not for a gramps-web-api connection!
Getting data out (extension → Gramps):
Good news — the extension already converts everything it scrapes into one common, well-organized internal format (names, dates, places, parents, spouses, etc.) before it ever touches WikiTree. That means adding a “send to Gramps” option wouldn’t require touching any of the ~90 site scrapers. It would just need one new piece that takes that already-normalized data and hands it to a gramps-web-api frontend (gramps-web, gramps-connect, or gramps-web-api itself). This is a contained, additive project.
Getting data in (Gramps → extension):
This direction is actually easier than it sounds, and easier than any of the existing scrapers. Most scraping is painful because commercial sites only give you rendered web pages, so the extension has to hunt through page layout to find data — fragile and constantly breaking. Gramps Web and Gramps Connect are different: they’re not just webpages, they are backed by a real data service that can hand back clean, structured genealogy data directly, without needing to interpret any page layout at all. Your own Gramps Web/Connect login already has the credentials needed to make that request sitting in the browser. So instead of writing a “scraper,” this would essentially be writing a small connector that asks Gramps Web for the data it already has in a structured form — far more reliable and much less code than a typical site handler.
Bottom line: Both directions are plausible, and neither requires reworking the extension’s core design. Pulling data from Gramps is the easier and more robust of the two, since Gramps Web /Connect can supply clean structured data on request rather than needing to be scraped like a normal website.
In some ways this extension is much more than a wikitree scraper; it is a general genealogy converter. Although it will require constant upkeep to keep the scrapers working.