Context
When a music entity (artist, album, etc.) already exists and is re-scraped, the scrape may return different metadata (e.g., a better thumbnail URL). Currently we log & skip these conflicts.
Desired Behavior
Track pending metadata changes from re-scrapes so the admin can review and accept/reject field-level updates to existing entities — similar to how pending_review / verified / rejected works for links today.
Options to explore
- New
music_entity_pending_changes table with field name, old value, new value, status
- Or extend the existing link review pattern
Related
PR #82 — decided to defer this to keep scope manageable.
Context
When a music entity (artist, album, etc.) already exists and is re-scraped, the scrape may return different metadata (e.g., a better thumbnail URL). Currently we log & skip these conflicts.
Desired Behavior
Track pending metadata changes from re-scrapes so the admin can review and accept/reject field-level updates to existing entities — similar to how
pending_review/verified/rejectedworks for links today.Options to explore
music_entity_pending_changestable with field name, old value, new value, statusRelated
PR #82 — decided to defer this to keep scope manageable.