.gpkg importer with options?

Ideas
1

Can importer plugins be made with options?

The relative media path and media objects of Gramps XML .gpkg files often cause complaints when importing to a different OS or when doing repeated tests.

Perhaps there could be an importer option to ignore Media files and paths? Or maybe a Gramps .gpkg importer plugin that skips those?

Media directory c:\users\name of file.gpkg.media exists. Delete it first, then restart the import process

Also, the menu for import file types is … ambiguous for non-exports. They might see a file with a .gramps or .gpkg extension. But the menu does not give a clue.

“Gramps package (portable XML)” what the heck does THAT mean? Isn’t XML implicitly “portable”? Ok, so gpkg is an abbreviation for Gramps package and Gramps was a backronym. But that isn’t very helpful to the average user. And while I know the difference between a “Gramps XML Family Tree” and a “Gramps package (portable XML)”, why should it be so complicated that Aunt Martha needs to look it up?

image
image969×548 81.6 KB

The Export dialog has different labels and tooltips:

image
image1066×706 67.1 KB

feature request filed - 13873: Harmonize importer/exporter menus

2

When I plan to share a Gramps export file (here on Discourse, or with a family member), it seems necessary to save it as an uncompressed .gramps XML and inspect the data. Then, for increased compatibility, I might use a text editor to trim out the chunks with Relative media path, unused tags, researcher, name-formats, namemaps, bookmarks.

If it is really important that others can access the data, I might even labor to import the XML file into the 4.28 GrampsPortable and export the compressed .gramps file in its broadly compatible XML format (making certain to clear the Researcher/Owner data in the GUI)

It would be nice to be able to do all this using an alternative exporter plugin.