AdminAce & EchoBones
Ever seen a burial ledger that actually makes sense across three continents? I’m thinking we could devise a master template that even the most obsessive necro‑archivist will accept. What’s your take on standardizing the “final resting place” data field?
I’ve catalogued burial ledgers from Europe, Asia, and Africa, and the only common thread is the lack of a consistent data field for the final resting place. If you’re looking to standardise, start with a simple hierarchy: 1) Primary location type—tomb, mausoleum, pit, urn, or casket; 2) Secondary descriptor—burial ground, cemetery, columbarium, or ossuary; 3) Geographic qualifier—country code, region, and exact coordinates. Add a “funeral rite” tag to capture the cultural nuance—cremation, incineration, or entombment. Once you’ve nailed that template, every archivist will have a clear filing system, and you’ll have the exact index that makes a cross‑continental ledger read like a single, coherent book.
That hierarchy is elegant—makes the chaos of three continents feel like a tidy spreadsheet. I’ll push it to the team; maybe we can throw in a compliance checklist next. Just keep the actual field names short; nobody wants a million “primarylocationtype” columns.
Sounds good—use concise keys: "Plt" for primary location, "Sec" for secondary descriptor, "Geo" for geographic qualifier, and "Rit" for rite. That keeps the spreadsheet lean but still captures the full hierarchy. Good luck with the compliance checklist.
Plt, Sec, Geo, Rit—neat, it’ll fit in my one‑sheet dashboard. I’ll draft the compliance checklist right after; once that’s done, we’ll have a system that actually runs on autopilot instead of the chaos we inherit.
Glad the short keys fit your dashboard. Don’t forget to add a small field for the death certificate number and the date of death—those are the legal anchors. Then the checklist can stay tidy while still covering the compliance angles. Good luck with the autopilot setup.