I see that images added for a person are just references to some location on my local disk.
This makes them extremely fragile - easy to break path by changing location, name, file extension, etc.
It also makes it hard to share a project with others.
Is there some option / plugin which can embed the binary image data into the same database as other info?
It seems this would be MUCH more user friendly (similar to defaults for most desktop applications)
If only text is supported, it can be base-64 encoded.
Ah, I just discovered that the Backup feature allows one to embed media.
This is good enough I suppose.
And there are built-in tools to resolve paths breaking when you move file around.
Eventually I expect someone will write a report that find all the media object that are NOT within the Relative Media path to create a “move file” script. There is already a too to download Media Object that have URL paths.
See the Media Management wiki page. That page needs someone to adopt it & give it some love. (It won’t be me since I don’t not use the Media feature.)
While it is true having the raw media files stored on the user’s hard drive could be a problem, proper file care is easily taken.
One, store your genealogy media in a folder for just that purpose. I store all my genealogy files in my main Genealogy folder in a named… you guessed it… Media folder. This location is stored in the Gramps Preference’s Base path for relative media paths. This path allows Gramps to manage files on your hard drive.
Besides the Media Manager, a handy addon tool is Media Verify.
When Gramps creates the Media record for an image on your hard drive, it also stores the image’s checksum. With this information, Verify can scour your base media path and locate the image file if you have moved or even renamed it.
I had all my census images in a common Census folder. It got too big so I broke the folder into sub-folders by country and for the US by year. I moved all the images to their new folders and in some cases renamed them. I no longer had to name an image ‘US 1880 …’ if that was the name of its folder. Using Media verify, it found all these files and fixed their Gramps path file entry.
One caution for this. If you edit the raw image on the hard drive; crop, resize, etc, the checksums will no longer agree. So before undertaking moving images or renaming them, the function Generate in Media Verify will reset all media checksums. Without checksums agreeing, verify will note that a media file cannot be found based upon its Gramps media path. Likewise, it will find the altered file and note that it is an extra file in the hard drive’s media folder.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.