Design Review: resource map indexing strategy
Mid to long term design review:
Current design is that resource maps are not indexed until all referenced objects are indexed or accounted for (archived/obsoleted).
This causes issues showing links to documents that are known - and could prevent resource maps from ever being indexed - if there are references to unknown ids.
The design works this way so that the data relationships are only introduced into the index when the entire resource map can be processed. An alternative would be to build/re-build the relationships (resourceMap, describes, describedBy) on each update of every document. Would entail querying the index for resource map referencing the current document and building the relationship links between the indexed documents for each event the index responds to. Would add a fair amount of re-work to the index parsing api controller logic (XPathDocumentParser) and a fair bit of new processing load on the CN.