Bonjour.
Je voulais partager un nouveau projet généalogique axé sur la gestion documentaire que j’ai découvert récemment. Il y a plein de bonnes idées dont l’équipe de développement pourrait s’inspirer pour améliorer la gestion des médias dans Gramps ou peut être permettre une communication entre les 2 logiciels avec une API. Bonne découverte.
Perhaps you could extend an invitation to Yohann to this thread? Since the documentation is in French, the invitation should probably be written in that language by a native speaker.
The Djehooty introduction mentions Gramps several times. Maybe he would be interested in collaborating so that the 2 might work seamlessly? Or at least exchange data? I recall no indicators that Gramps will be expanding its media object cataloging capabilities in the near future.
The description of tracking provenance and cross-referencing with meta data is intriguing. And vaguely reminiscent of our discussion (in another thread) of tracking artifacts.
The project’s website is available in English:
Another idea could also be to use Paperless NGX, which also runs using Docker. Here’s what I recently posted on a genealogy Discord server:
Document Management
I’m not sure where to put this, so I’ll post it here. I’m thinking about this following <@415180903124434964>’s question about humidity damage to personal documents and the responses from <@640553586782240808>. A temporary—or conservative—solution might be to photograph everything (or scan it, if you’re not moving moldy documents back and forth across the scanner glass) and archive these photos/scans as backup copies, just in case.
The question of how to organize one’s genealogical documents often arises on genealogy forums/groups, even if I haven’t seen it much here. Where and how should one store PDFs, screenshots, scans… following which naming conventions, etc.?
One idea could be to use a document manager—in this case, I’m thinking of Paperless NGX, an open-source, self-hosted software. It offers many features, such as defining categories and tags, providing shareable document links, etc.
It’s not specific to genealogy but could likely be a very practical tool for anyone not using genealogy software that natively supports document management (I don’t have this issue with Gramps, but I’m still considering how I might use it—for example, for those doing genealogy online, like on Geneanet, etc.). It also supports multiple users, which is useful for those working on genealogy together.
It runs on Docker, regardless of your operating system, which means you can, if desired, run multiple instances—for example, one for personal administrative documents and another for genealogical documents.
Good evening,
I am the developer of Djehooty. I am responding in French here, but please feel free to let me know if you prefer me to switch to English elsewhere.
Currently, Djehooty takes a rather different approach compared to traditional genealogy software, adopting a very “document-centric” methodology. This means that research begins with documents rather than individuals, as things stand at this stage of development.
Djehooty is built upon a REST API that enables communication between the backend and frontend. From the outset, I have envisioned opening this API to other clients that might wish to query the database (locally or remotely). I haven’t yet delved deeply into considerations regarding compatibility with software like Gramps, but creating a bridge would be entirely feasible if it proved useful.
@emyoulation This thread is truly very interesting—thank you! It’s a shame I didn’t come across it sooner. It precisely highlights one of the needs I’ve also identified with my own family archives and tracking of objects (passed down across generations, sometimes between sellers and private individuals, often among members of the same family, but also when family heirlooms end up in museums). I will take the time to read everything thoroughly and respond with my own reflections on this topic.
@PLegoux I saw your message on Discord 
but didn’t respond at the time. I have looked into Paperless-ngx (and other DAM tools like digiKam). I briefly considered using it, as the tool is indeed interesting! However, I ultimately chose to develop my own application to better meet my specific genealogy-oriented needs.
Please don’t hesitate to ask any questions or share remarks about Djehooty—I’ll be delighted to respond.
We should probably try to draw the attention of @DavidMStraub to this thread.
Gramps Web might be better positioned than Gramps to collaborate with another REST API?
Yes, thanks 
@yoann your motivation sounds very similar to the motivation for Gramps Web. I recently wrote up my personal motivation for working on it in this blog. In the last 1-2 years, Gramps Web has grown a solid community of motivated contributors.
Gramps Web is also based on a REST API, but with Gramps itself (the Python library) at its core, making it interoperable with Gramps, the desktop app. We also have a sync client.
Concerning document-centric reserach – I actually think that’s the right philosophy, and also the one I’m following when using Gramps. Gramps has a powerful three-level source management system (repository > source > citation) where documents can be stored as attached files or as rich text notes. From there, you can then link people, events, and places.
I suggest you look around in the Gramps Web documentation a little bit, and if there is any opportunity for collaboration, do let us know.