mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-05-30 23:40:40 +02:00
[Enhancement]: Add an Original Publication Year to the Details pane #1034
Assignees
adam (Adam Melkus)
Clear assignees
adam (Adam Melkus)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/audiobookshelf#1034
Reference in New Issue
Block a user
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?
Originally created by @cupanoodle on GitHub (Mar 22, 2023).
Describe the feature/enhancement
It would be good to be able to add the year of the original publication for a book since it is often different to the audiobook publication year.
For example The Colour of Magic by Terry Pratchett has an original publication year of 1983 but there are numerous audiobook adaptations with widely ranging publication dates. In the case of this book I just used 1983, but now I have two editions of the same book and it would be convenient to be able to put both the original publication year and the audiobook publish year.
@iconoclasthero commented on GitHub (Feb 21, 2024):
This is pie-in-the-sky thinking...and as such, maybe it belongs in a separate ER, but I would like ABS to someday have the ability to use, e.g., AI, to find the original publication date so I don't have to deal with finding the original publication date.
Also, given this, an option as to which date to use for record keeping and sorting would be important. E.g., my books are saved as e.g.,
/library/books/audiobooks/Last, First/Title: Subtitle (YYYY)/Title -- Audiobook.opusand YYYY is for the original publication date. Admittedly, this can be a bit out of format occasionally (e.g.,../Homer/The Iliad (Emily Wilson trans. - Audra McDonald narr.) (700 BC)/The Iliad -- Audiobook.opus) but generally works to capture and store the information most relevant to me published over the last 2 millenia (all but 9 books).@iconoclasthero commented on GitHub (Jul 29, 2024):
Hey, so I'm back to this.
How about instead of having the DB accept two dates as a single item (e.g.,
1988, 2013) allow the field to accept more than one date. Once the data's captured, dealing with it is something that can be done later/OYO.So for the e.g., ABS would record two dates in the db,
19882013.When presented with these dates, I'm going to assume that the < value is what I put in for the original date and > is what I put in for the current pub. that I have.
FWIW, I do have to remove all the matched dates and put the actual publication date of all the books in manually ...
@cupanoodle commented on GitHub (Jul 31, 2024):
Two dates in the same field would likely work (similar to how the author and narrator fields work).
On the UI it would be nice if in there was a quick way to differentiate two editions of the same audiobook without having to click into them, but that could be a future improvement. For now I just deal with it.
the web UI seems to have a way to tell but not the android app.
@scapix commented on GitHub (Aug 17, 2024):
following tags that can/should be used to populate this field:
mp3
mp4
https://docs.mp3tag.de/mapping-table/
https://www.exiftool.org/TagNames/ID3.html
https://www.exiftool.org/TagNames/QuickTime.html
https://www.exiftool.org/TagNames/QuickTime.html#iTunesInfo
@scapix commented on GitHub (Aug 17, 2024):
you can find original/first publish year for any book on www.goodreads.com
@iconoclasthero commented on GitHub (Aug 30, 2025):
I don't trust goodreads as it uses crow-sourced "librarians" (now) and used to allow just anyone (e.g., me) to add data; I only use it as a last resort. Mostly I just google the book and let google give me it's best guess. If I had to trust one source, it would be wordcat....though usually I'll be lazy and trust Wikipedia if there's an issue with what google tells me:
.
.
Yeah, I think they're arrays in the database now? I don't feel like messing with sqlite right now to verify, but IIRC, it's in the form of ca.
"Last1, First1", "Last2, First2", ... "Last-n, First-n"for authors and narrators now, so there's no reason it couldn't be easily converted over to an array. I'm looking at a book now that I'm going to change from 2017 to 1992 and Audible lists as 2020 because the point is that the book (sans the "new afterword") was researched, written, and published >30 years ago which—when evaluating the veracity and relevance of a [non-fiction] text—is the most important.That said, I'd be happy to just be able to have it list
1992, 2017, 2020i.e., for original, edition w/ new afterword, audiobook edition. If this could be further mapped onto something like @scapix mentioned, great, but as long as the individual fields were somehow broken out in the metadata.json, i'll just freetext them into my .opus files withopustagshowever it makes sense if/when such is implemented.