Gramps Web
approvedby David Straub
Link your notes to people, families, events, places and sources in a Gramps Web genealogy server. - This plugin has not been manually reviewed by Obsidian staff.
Gramps Web for Obsidian
Link your Obsidian notes to people, families, events, sources and notes in a Gramps Web family tree.
Features
-
Gramps links: the Insert Gramps link command searches your tree and inserts a link such as
[Johann Straub (I0044)](gramps://Person/handle/…). Clicking it opens the object in Gramps Web. These are the samegramps://links that Gramps uses in its own notes. Prefix the search with a type and colon to filter, e.g.person:orp:(also family/f, event/e, place/pl, source/s, citation/c, repository/r, media/m, note/n); the active filter is shown in the picker. -
Hover preview: hover over a link to see the name, Gramps ID, life dates and photo.
-
Embedded cards and notes:
```gramps person: I0044 ```Use
note: N0012instead to show a Gramps note. -
Optional inline search: type a trigger (off by default,
@@when enabled) to search while you type.
Setup
- In Settings → Gramps Web, enter your server URL and username.
- Enter your password and select Sign in, then select Test connection to check that it works.
The plugin assumes the Gramps Web app and its API are served from the same URL, which is the default setup.
Privacy
The plugin only talks to the Gramps Web server you configure. It sends search terms and the IDs of the objects it looks up. It never sends note contents or file names, and it has no analytics. Your password is not stored. The login tokens are kept in Obsidian's secret storage on this device and are not synced.
Requires Obsidian 1.11.4 or later. Works on desktop and mobile.
Support
If you find this plugin useful, consider sponsoring me on GitHub.
Development
npm install
npm run dev # watch mode
npm run build
npm run lint
License
MIT
For plugin developers
Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.