Before GEDCOM7 ZIPs become a common situation

The project has gained a lot of real-world experience about Media problems in the years since the .gpkg (including Media objects) was implemented.

Generally, using the feature to import a backup for the same computer works pretty well … although there are some surprises.

Before GEDCOM’s new zip with media become common, maybe we should discuss strategies for resolving the issues that will affect importing those too?

We probably need Import options for:
  • GEDCOM ZIPs and .gpkg that allows ‘only media’ or ‘only genealogy tree data’
  • harmonization of slash or backslashes to the target OS’es standard
  • conversion of absolute paths to a subdirectory of a relative path root
  • option to redefine the Relative Media Path (that could be handled in the workflow instead of in code)
1 Like

Some issues:

  • 0012407: Segmented .gpkg archives
  • 0012407: Segmented .gpkg archives - Gramps - Bugtracker – Free Genealogy…
  • 0009667: Gramps package import won’t work if media directory already exists…
  • 0009232: Default base path for relative media paths is inappropriate. - Gramps…
  • 0007156: Gramps package import won’t work if media directory already exists -…