Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Read List Matching - Add Match Year Column for Verifying Correct Match #1114

Closed
4 tasks done
gardn701 opened this issue Apr 25, 2023 · 1 comment
Closed
4 tasks done
Labels
enhancement New feature or request released

Comments

@gardn701
Copy link

Describe your suggested feature

While komga matches correct 90%+ of the time on read list importing, if there are multiple series of the same name then the match is suspect. While this is easy to detect if it becomes flagged as a "duplicate book", there are many instances where it is matches but no warnings appear. Trying to detect this is incredibly tedious by clicking the book to see what year it is in the popup. Without altering the matching logic to compare the year in read list metadata to issue year already in library and give a warning or better match, this would be easy to fix by improving the read list matching table data with year data on the match side. Either formatted in the series name like the "Requested Series" text or simply a new column with the year, so that on visual inspection we could quickly compare and see what is a correct match.

For reference, I've seen this issue appear when matching DC titles like Deadman 1985, and it auto matches to Deadman 2018 even though the 1985 series exists in library.

Thanks!

Other details

No response

Acknowledgements

  • I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
  • I have written a short but informative title.
  • I have updated the app to the latest version.
  • I will fill out all of the requested information in this form.
@gotson gotson added enhancement New feature or request and removed triage labels Apr 25, 2023
@gotson gotson closed this as completed in 0f89cf3 Jun 28, 2023
@github-actions
Copy link
Contributor

🎉 This issue has been resolved in v1.0.0 (Release Notes)

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request released
Projects
None yet
Development

No branches or pull requests

2 participants