You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Indexer: shared entities kept per crate, and clashes fail the job #104
A crate link table in our own models: one row per (crate, entity) pair, indexed both ways. For people, organisations and software it holds that crate's derived copy.
It is the only record of which crates contain an entity. meta.crateId is dropped, and per-crate counts and deletes use the links.
A crate that mentions a person without the LDaC profile gets no link.
Winner: a shared entity's row and search document are wholly one crate's copy: a crate whose metadata licence is open first, then the lowest crate id. Copies are never merged.
Delete and reindex:
Deleting a crate removes its links, then the entities and documents with no link left.
A shared entity whose winning crate goes is rebuilt from the next crate's stored copy, without reading the repository.
Reindexing a crate that no longer contains an entity drops its link the same way.
Clashes: a collection, object or file another crate already holds, or an id described as a different kind of entity, fails the second crate's job, with an error naming both crates and the entity. The holder keeps the row.
The migration may empty the old Entity and File rows: there's no upgrade path for existing data.
Activity