Skip to main content

Sample scenario

Needs review

Holding an item back is a deliberate result. Each entry states why it was held and what would settle it, so nothing is quietly dropped.

Changing the sample scenario only changes local demonstration content. It does not send a request or change anything returned by the backend API.

Open items

Sample scenario

3

Waiting on a person.

Held for rights

Sample scenario

1

Context cannot be shown.

Held for ambiguity

Sample scenario

2

Two readings are equally supported.

Review queue

Every item lists what each source reported, so a reviewer can see whether the gap is in the evidence or in the coverage.

Sample scenario

Sample scenario. Local demonstration content for a capability the backend contract does not cover yet. Nothing in this section is sent, saved, approved, locked, or exported.

  • Ambiguous identifier match

    DEMO-review-01 · MOCK-record-1004

    Two records share a normalized identifier but differ in author list and year. Grouping them would change the reconciled count.

    Coverage limitation

    Full text unavailable, so the usage category cannot be verified from context.

    Absence of a record is a limit of the sources searched, not evidence of absence.

    What each source reported

    • OpenAlex: record present, context unavailable
    • Dimensions: record absent
    • Legacy reference workbook: record present, reference only

    Decision controls stay off in a sample scenario. Nothing here is sent, saved, or approved.

  • Rights restricted context

    DEMO-review-02 · SYN-record-1003

    The record is clearly citing the target, but no excerpt can be shown, so the usage category rests on metadata alone.

    Coverage limitation

    Excerpt restricted by rights.

    Absence of a record is a limit of the sources searched, not evidence of absence.

    What each source reported

    • OpenAlex: record present, excerpt withheld

    Decision controls stay off in a sample scenario. Nothing here is sent, saved, or approved.

  • Category disagreement

    DEMO-review-03 · SYN-record-1002

    Abstract-level context supports two different usage categories with similar support.

    Coverage limitation

    Abstract-level context only.

    Absence of a record is a limit of the sources searched, not evidence of absence.

    What each source reported

    • Dimensions: record present, abstract available

    Decision controls stay off in a sample scenario. Nothing here is sent, saved, or approved.