Hi! I’m thinking of making an addon to link my gramps database with online services. My current idea would be to save these online data as json for each linked person so that I can check later what has changed. Where should I save these data?

It seems as though linking a JSON Media object would have the least chance of making the Tree excessively large & slow. The individually-sized-portion scrapes in JSON could be hung as a dated media object, placing that media object in a subfolder of your Preferences Media path. If you anticipate a …

What about just storing it as a Person attribute?

Isn’t the potential size of a JSON too large for a Attribute?

At least regarding the data schema, I don’t see any length limitation: gramps-project/gramps/blob/master/gramps/gen/lib/attribute.py#L250-L251 "value": {"type": "string", "title": _("Value")} Not sure if t…

[image] DavidMStraub: At least regarding the data schema, I don’t see any length limitation My concern was the practical limit of the Edit Attribute window. It displays only a single line of text with no scroll controls. So it would be impractical to manually examine even a minimal JSON withi…

A different approach than external files or the Attributes internal data structure. There is an existing add-on that a Note in the Associations to store specially formatted data. The DNA Segment Map Gramplet add-on uses a “DNA” custom type Note in the Association element. You might adapt this add…

Best practices for saving addon specific data

Development

Topic		Replies	Views
JSON inside table Development third-party-addon , tools , data-import	33	628	December 16, 2025
JSON schema specification Development metadata	16	1662	May 16, 2022
The Road Ahead for database representations Development database	40	933	November 15, 2024
Media compression tool and media format change tool Ideas media-records , third-party-addon	13	202	May 17, 2026
Merge best practice Gramps Web	2	477	June 28, 2023

Best practices for saving addon specific data

Related topics