Importers do not import hierarchies with correct IDs... about ehri-rest HOT 2 CLOSED

@bencomp I should note this is pretty serious and could (and indeed, might already) cause major problems with validation. Unfortunately I can't see an easy fix with the current structure of the importers where we create child nodes before their parents; might be worth a chat to discuss approaches.

I can see a few different ways to go, but I think it might be worth consolidating the existing code before trying to implement them.

from ehri-rest.

Okay I had a go at this but I'm not really happy with the result. The EAD handler now keeps a stack of item identifiers as it traverses the hierarchy. This is then fed to the importer instance (instead of the depth) where it is used to build the eventual path ID (note terminology: identifier=c2, path ID=nl-r1-c1-c2.)

Unfortunately the extraction of meaningful identifiers for each unit isn't really robust enough at the moment, and I think we shouldn't go so far as to generate our own identifiers if there're not provided (this is a good use for preprocessing IMHO.)

from ehri-rest.