v0.8.0 — Correction memory and better library triage

v0.8.0 — Correction memory and better library triage

This release makes large libraries easier to review and helps you revisit names that return after corrections. Corrections still happen manually on Last.fm; the analyzer provides findings, suggestions and remembered choices.

New

• Browse every finding. Previous/Next controls show 100 cards per page, with a visible range and separate card/finding counts. Reports still cover the full library.
• Remember correction choices. Optionally record the spelling or album you kept when marking Fixed. Remembered choices appear on later findings and in reports, and survive Restore. Ignore does not replace your remembered choice.
• Album suggestions from library evidence. Missing-album and compilation rows offer non-compilation-like albums from plays of the exact artist and track, plus prior album choices. Each suggestion shows its evidence. Use fills the optional field; Fixed saves it. These are research leads, not confirmation of an original release.
• Follow-up triage. Follow-ups only and Follow-ups first bring repeat offenses and unresolved prior decisions forward.

Fixed and improved

• Fixed names can recur after their old plays disappear, even when the returning count is smaller than the original baseline or below ordinary discovery thresholds. The analyzer must observe that decrease in an accepted complete export first.
• Plays under an explicitly chosen kept spelling, including case aliases, do not trigger recurrence.
• Live/remaster labels no longer consume meaningful sibling or nested title parentheses. Keyword matching respects word boundaries; ordinary case-only groups are excluded without weakening invisible-character detection.
• CSV parsing preserves raw names and hidden whitespace, and supports quoted delimiters, escaped quotes and embedded line breaks. Invalid account headers, row widths and timestamps receive actionable errors.
• Stable name-based IDs avoid punctuation and Unicode collisions and remain stable when the most-played member changes. Existing saved decisions and correction choices migrate conservatively. Ambiguous or split prior groups ask for review; detection changes use a review explanation rather than claiming new listening.
• Older or unordered exports open for review without changing saved history. Storage failures and overlapping imports cannot overwrite unreadable history or mix results from different files.
• Search narrows missing-album and compilation rows. Counts, impact sorting and compilation bulk actions reflect the rows currently shown. Artist filtering includes variation aliases.
• Keyboard access and focus handling improve. Open details and unsaved correction fields survive paging, filtering and other actions within an import.
• Attribute-shaped metadata is escaped safely in fields and tooltips.

Getting a refreshed export

After editing scrobbles on Last.fm, lastfmstats may reuse its saved historical library and fetch only new plays. That produces a new CSV containing old metadata.

On the lastfmstats homepage, open Database and use Remove from database beside your username. Retrieve the library again by username, wait for the complete retrieval, then export. Avoid importing your old CSV back into lastfmstats.

Use complete exports and preserve their original file modification times. The CSV format cannot certify a full refresh; file chronology checks alone cannot detect an export that appends new plays to stale history.

Upgrade notes

Your existing decisions remain tied to your Last.fm username and browser. Some findings may ask for review where the old identity or grouping is ambiguous. No broad Fixed/Ignore decision is silently copied into uncertain new groups.

Correction memory is optional. Marking Fixed records your decision; it does not verify a correction on Last.fm. Direct retrieval, automatic correction verification and additional pattern detectors are outside this release. The planned pattern-detector release moves to v0.9.0.