Skip to content

Indexer: check production crates for profiled stubs of their parent collection #97

Open

Description

@johnf

Parent

Spec: indexer redesign

What to build

A check on production data, needed before shared entities and clashes land. Under the redesign, a collection, object or file described by a second crate is a clash, and it fails that crate's Index job (ADR 0006). A member crate that carries a profiled stub of its parent collection (the parent's @id, with the LDaC Collection profile) would therefore fail.

Check the production crates for:

  • member crates whose metadata includes a profiled entity whose @id is another crate's root
  • any other collection, object or file @id that appears in more than one crate
  • the same @id described as different kinds of entity in different crates

Acceptance criteria

  • A comment on this issue lists each affected crate and entity id, or says there are none.
  • For each case: whether the crate's data should be fixed, or the clash rule needs revisiting before the shared-entities ticket lands.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions