david/library-manager
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases 10 Packages Wiki Activity Actions

Design metadata source lookup and enrichment workflow #5

New issue
Closed
opened 2026-06-11 08:06:23 -07:00 by david · 1 comment
david commented 2026-06-11 08:06:23 -07:00
Owner
Copy link

Design metadata source integrations for two primary workflows:

  • Adding a wanted author and discovering works, series, editions, identifiers, and aliases from metadata sources.
  • Filling missing or weak metadata on scanned/imported items, including title, author, narrator, series, publisher, publication date, identifiers, descriptions, covers, genres, and language.

Requirements:

  • Keep provider credentials and rate-limit behavior backend-side.
  • Store lookup results as source-attributed metadata evidence before changing canonical records.
  • Preserve conflicting source values for operator review.
  • Define source priority and confidence rules before automatic promotion.
  • Include cache/provenance fields so large imports do not repeatedly query providers and operators can audit where values came from.
Design metadata source integrations for two primary workflows: - Adding a wanted author and discovering works, series, editions, identifiers, and aliases from metadata sources. - Filling missing or weak metadata on scanned/imported items, including title, author, narrator, series, publisher, publication date, identifiers, descriptions, covers, genres, and language. Requirements: - Keep provider credentials and rate-limit behavior backend-side. - Store lookup results as source-attributed metadata evidence before changing canonical records. - Preserve conflicting source values for operator review. - Define source priority and confidence rules before automatic promotion. - Include cache/provenance fields so large imports do not repeatedly query providers and operators can audit where values came from.
david commented 2026-06-11 09:12:16 -07:00
Author
Owner
Copy link

M2 metadata resolver foundation completed.

Implemented internal/metadata with:

  • Backend provider contract for wanted-author lookup.
  • Backend provider contract for missing-item enrichment.
  • Source-attributed enrichment evidence.
  • Confidence-based result ordering.
  • Provider error propagation and duplicate-provider validation.
  • Unit tests with fake providers.

Real external providers remain future implementation work, but the resolver contract is ready for app/API work.

M2 metadata resolver foundation completed. Implemented `internal/metadata` with: - Backend provider contract for wanted-author lookup. - Backend provider contract for missing-item enrichment. - Source-attributed enrichment evidence. - Confidence-based result ordering. - Provider error propagation and duplicate-provider validation. - Unit tests with fake providers. Real external providers remain future implementation work, but the resolver contract is ready for app/API work.
david closed this issue 2026-06-11 09:12:17 -07:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
v0.2.8
v0.2.7
v0.2.6
v0.2.5
v0.2.4
v0.2.3
v0.2.2
v0.2.1
v0.2.0
v0.1.0
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
david/library-manager#5
No description provided.