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]: Additional fields for Translation and Introduction #2241

New Issue
Open
opened 2026-04-25 00:05:20 +02:00 by adam · 7 comments
adam commented 2026-04-25 00:05:20 +02:00
Owner
Copy Link
Copy Source

Originally created by @ddrews-de on GitHub (Sep 7, 2024).

Type of Enhancement

Web Interface/Frontend

Describe the Feature/Enhancement

In addition to the Authors and Narrators there might be Translator(s) and the foreword / introduction done by someone special (author or special guest). It would be nice to have separate fields for these.
Translators might be implemented like authors as a separate list.
Forward / Introduction might be just an additional information.

Why would this be helpful?

Currently these people are often added into the Author field with the addition ' - translator' or ' - introduction' and in some cases there double entries in the authors list. And match all authors runs into errors every time.

Future Implementation (Screenshot)

2024-09-07 21_04_16-Audiobookshelf

Audiobookshelf Server Version

v2.13.3

Current Implementation (Screenshot)

2024-09-07 21_00_32-Audiobookshelf

Originally created by @ddrews-de on GitHub (Sep 7, 2024). ### Type of Enhancement Web Interface/Frontend ### Describe the Feature/Enhancement In addition to the Authors and Narrators there might be Translator(s) and the foreword / introduction done by someone special (author or special guest). It would be nice to have separate fields for these. Translators might be implemented like authors as a separate list. Forward / Introduction might be just an additional information. ### Why would this be helpful? Currently these people are often added into the Author field with the addition ' - translator' or ' - introduction' and in some cases there double entries in the authors list. And match all authors runs into errors every time. ### Future Implementation (Screenshot) ![2024-09-07 21_04_16-Audiobookshelf](https://github.com/user-attachments/assets/d5fd4904-a489-4fec-adae-275dc4512474) ### Audiobookshelf Server Version v2.13.3 ### Current Implementation (Screenshot) ![2024-09-07 21_00_32-Audiobookshelf](https://github.com/user-attachments/assets/996e26de-0168-4344-8543-315481905940)
adam added the enhancement label 2026-04-25 00:05:20 +02:00
adam commented 2026-04-25 00:05:20 +02:00
Author
Owner
Copy Link
Copy Source

@nichwall commented on GitHub (Sep 7, 2024):

Related to https://github.com/advplyr/audiobookshelf/issues/3211

@nichwall commented on GitHub (Sep 7, 2024): Related to https://github.com/advplyr/audiobookshelf/issues/3211
adam commented 2026-04-25 00:05:20 +02:00
Author
Owner
Copy Link
Copy Source

@ddrews-de commented on GitHub (Sep 8, 2024):

Related to #1877

@ddrews-de commented on GitHub (Sep 8, 2024): Related to #1877
adam commented 2026-04-25 00:05:20 +02:00
Author
Owner
Copy Link
Copy Source

@ddrews-de commented on GitHub (Sep 8, 2024):

The information for this book came from audible.de: https://api.audnex.us/books/1684571251?region=de
In the response, Johanna Hanink is referenced twice but with the same ASIN ID.
By looking into the other two issues, there are the following additional support roles for a book:

  • Translator
  • Introduction
  • Foreword
  • Contributor
  • Editor

Since there might be some upcoming additional roles, like "- used AI model", an implementation might be different from my proposal. Maybe an additional role attribute for authors, the roles put into its own table with name and identifier (like '- translator'), and in the settings the list can be edited for future additions.

@ddrews-de commented on GitHub (Sep 8, 2024): The information for this book came from audible.de: https://api.audnex.us/books/1684571251?region=de In the response, Johanna Hanink is referenced twice but with the same ASIN ID. By looking into the other two issues, there are the following additional support roles for a book: - Translator - Introduction - Foreword - Contributor - Editor Since there might be some upcoming additional roles, like "- used AI model", an implementation might be different from my proposal. Maybe an additional role attribute for authors, the roles put into its own table with name and identifier (like '- translator'), and in the settings the list can be edited for future additions.
adam commented 2026-04-25 00:05:21 +02:00
Author
Owner
Copy Link
Copy Source

@v4u6h4n commented on GitHub (Feb 9, 2025):

I'm so used to the fields available in zotero, that translator, contributor, editor and author seem sufficient to me, as contributor covers pretty much everything.

@v4u6h4n commented on GitHub (Feb 9, 2025): I'm so used to the fields available in zotero, that translator, contributor, editor and author seem sufficient to me, as contributor covers pretty much everything.
adam commented 2026-04-25 00:05:21 +02:00
Author
Owner
Copy Link
Copy Source

@Silther commented on GitHub (Mar 11, 2025):

If you have a translator, you should also be able to add the OV language

@Silther commented on GitHub (Mar 11, 2025): If you have a translator, you should also be able to add the OV language
adam commented 2026-04-25 00:05:21 +02:00
Author
Owner
Copy Link
Copy Source

@Phantomwise commented on GitHub (Nov 20, 2025):

I'm so used to the fields available in zotero, that translator, contributor, editor and author seem sufficient to me, as contributor covers pretty much everything.

Maybe have the contributor be two fields, one for the name and one for the type of contribution, so you don't lose any info like Foreword and Introduction? Kinda like how series is actually two fields, one for the series name and one for the book number.

That way if you have Author Name - whatever role that is not already supported, then it could still go into the contributor field automatically

It would also remove the need to multiply fields for every role, everything could just go in contributor, with the role as the type.

name = Stephen Fry
type = foreword

name = Charlotte Bronte
type = introduction

name = Abi Hynes
type = adaptation

name = Otto Penzler
type = editor

name = Alice Faulkner
type = whatever string you want

When adding a contributor you'd fill the two fields, and it'd display it as Name (Type)

@Phantomwise commented on GitHub (Nov 20, 2025): > I'm so used to the fields available in zotero, that translator, contributor, editor and author seem sufficient to me, as contributor covers pretty much everything. Maybe have the contributor be two fields, one for the name and one for the type of contribution, so you don't lose any info like `Foreword` and `Introduction`? Kinda like how series is actually two fields, one for the series name and one for the book number. That way if you have `Author Name - whatever role that is not already supported`, then it could still go into the contributor field automatically It would also remove the need to multiply fields for every role, everything could just go in contributor, with the role as the type. ``` name = Stephen Fry type = foreword name = Charlotte Bronte type = introduction name = Abi Hynes type = adaptation name = Otto Penzler type = editor name = Alice Faulkner type = whatever string you want ``` When adding a contributor you'd fill the two fields, and it'd display it as `Name (Type)`
adam commented 2026-04-25 00:05:21 +02:00
Author
Owner
Copy Link
Copy Source

@v4u6h4n commented on GitHub (Nov 20, 2025):

How about some basic predefined fields (author, translator, etc), and then a add contributor button, where the name of the field and the contents can be assigned by the user...?

@v4u6h4n commented on GitHub (Nov 20, 2025): How about some basic predefined fields (author, translator, etc), and then a `add contributor` button, where the name of the field and the contents can be assigned by the user...?
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#2241
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?