starred/audiobookshelf
1
0
Fork 0
mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-05-30 23:40:40 +02:00
Code Issues 1.0k Packages Projects Releases 10 Wiki Activity

[Enhancement]: Save new cover with different name than overwriting it. #1051

New Issue
Closed
opened 2026-04-24 23:30:16 +02:00 by adam · 4 comments
adam commented 2026-04-24 23:30:16 +02:00
Owner
Copy Link
Copy Source

Originally created by @Dr-Blank on GitHub (Apr 8, 2023).

Describe the feature/enhancement

I have enabled store cover with progress. And sometimes the folder has a cover.jpg already present in it which gets overwritten when the books are quick matched. There is no record of previous covers and the data is lost permanently.

The proposal here is to keep multiple covers by saving the new cover as maybe cover.1.jpg or cover (1).jpg, although I do not prefer whitespaces in file names.

Subsequent matches would simply increment the numbers to keep a record.

One caveat of this would be if someone keeps matching again and again and just keeps saving the same covers with different file names. One solution of this could be solved by hashing the file to see if it is one of the other covers.

Originally created by @Dr-Blank on GitHub (Apr 8, 2023). ### Describe the feature/enhancement I have enabled store cover with progress. And sometimes the folder has a `cover.jpg` already present in it which gets overwritten when the books are quick matched. There is no record of previous covers and the data is lost permanently. The proposal here is to keep multiple covers by saving the new cover as maybe `cover.1.jpg` or `cover (1).jpg`, although I do not prefer whitespaces in file names. Subsequent matches would simply increment the numbers to keep a record. One caveat of this would be if someone keeps matching again and again and just keeps saving the same covers with different file names. One solution of this could be solved by hashing the file to see if it is one of the other covers.
adam added the enhancement label 2026-04-24 23:30:16 +02:00
adam closed this issue 2026-04-24 23:30:16 +02:00
adam commented 2026-04-24 23:30:18 +02:00
Author
Owner
Copy Link
Copy Source

@hobesman commented on GitHub (Apr 8, 2023):

This and a few related scenarios were discussed in the comments here: https://github.com/advplyr/audiobookshelf/issues/1548

But neither of those started out as what you're requesting so I think it makes sense to have a separate request specifically for this aspect.

@hobesman commented on GitHub (Apr 8, 2023): This and a few related scenarios were discussed in the comments here: https://github.com/advplyr/audiobookshelf/issues/1548 But neither of those started out as what you're requesting so I think it makes sense to have a separate request specifically for this aspect.
adam commented 2026-04-24 23:30:18 +02:00
Author
Owner
Copy Link
Copy Source

@advplyr commented on GitHub (Apr 8, 2023):

Related to #1548 and #1204

Might be worth merging these

@advplyr commented on GitHub (Apr 8, 2023): Related to #1548 and #1204 Might be worth merging these
adam commented 2026-04-24 23:30:19 +02:00
Author
Owner
Copy Link
Copy Source

@Dr-Blank commented on GitHub (Apr 9, 2023):

Yeah, merging all these issues would be great as it all boils down to some kind of cover management system. And this system would address the point in the three open issues:

  1. Having the ability to keep multiple covers.
  2. Having the ability to store multiple covers on users file system.
  3. Having the ability to not overwrite any existing data.

Closing this issue as solving other two would inherently solve this one.

@Dr-Blank commented on GitHub (Apr 9, 2023): Yeah, merging all these issues would be great as it all boils down to some kind of **cover management system**. And this system would address the point in the three open issues: 1. Having the ability to keep multiple covers. 2. Having the ability to store multiple covers on users file system. 3. Having the ability to not overwrite any existing data. Closing this issue as solving other two would inherently solve this one.
adam commented 2026-04-24 23:30:20 +02:00
Author
Owner
Copy Link
Copy Source

@iconoclasthero commented on GitHub (Jul 28, 2024):

I have a FR somewhere about covers: my thought was the ability to specify the names.
It is my strong preference to have more ability to manipulate the files that ABS expects to have in directories and what it saves files as; cover.jpg and metadata.json are far to generic. my desired path for the cover that abs uses by default is
/

@iconoclasthero commented on GitHub (Jul 28, 2024): I have a FR somewhere about covers: my thought was the ability to specify the names. It is my strong preference to have more ability to manipulate the files that ABS expects to have in directories and what it saves files as; `cover.jpg` and `metadata.json` are **far** to generic. my desired path for the cover that abs uses by default is <author>/<title>/title -- Cover 01.jpg <author>/<title>/title -- metadata.json it is annoying as **** that I cannot make everything in MY folder start with the title of the book so that I can manipulate it on the CLI via autocomplete the way that I prefer.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
Mirrored from GitHub Pull Request
 sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#1051
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?