A custom (by content) ‘lite’ Gramps XML file has been generated via an addon, but still need to created some “fake entries” for passing the complete validation tests (DTD, rng, XSD). Also there is a versioning issue if one does not care on current gramps branch: need to match the DTD version set on XML header too, and not only for the gramps’ version.
I did not go too far on these “fake entries” experience. They are all attributes on primary objects (handle, change, type). So, without a valid number for change, you could get an issue on import. Same for the handle.
A little bit strange, as I was not able to fully reproduce some issues reported on
Maybe need to modify the behaviour around Source primary object data import, which during testing, was not able to fully support the ‘old style XML’ (ie. ID value only), or to only limit import for People or Places data. Buffer issue somewhere on XML import with old ID method? Anyway, maybe no one still keeps some old backup files with the ‘old style’. And even such file, there is maybe so many upgrades since Gramps 1.x, that failure might raise at the beginning of the upgrade process (and not on sources mapping with ID only). Maybe a possible “corner” issue (import and custom source data set) for CSV import of Import Gramplet?
This “tiny” Gramps XML generator runs with lxml lib, but maybe few differences with ElementTree API (built-in lib).