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

[Feature Request] Multi-Library Support #131

Open
MichelfrancisBustillos opened this issue Nov 15, 2024 · 0 comments
Open

[Feature Request] Multi-Library Support #131

MichelfrancisBustillos opened this issue Nov 15, 2024 · 0 comments

Comments

@MichelfrancisBustillos
Copy link

MichelfrancisBustillos commented Nov 15, 2024

Feature Request: Multi-Library Support
I know it is already mentioned that this is being investigated, but I wanted to open a Feature Request to hopefully gain some traction on it.

Alternatives I've Considered
Running multiple instances is an option, but would require I either A) share multiple links with my users which they would have to bookmark/save or B) implement a 'landing page' with shortcuts to each library. While both are potential options, they add friction to the user experience and increase maintenance/setup workload.

Additional context
I currently have >1000 eBooks spread across 8 Calibre libraries. Having separate libraries allows for faster loading, as well as separation of genres (i.e. ensuring that books in the "Adult" section and "Children's" section never overlap). It also makes managing a large collection easier as columns, filters, formats, etc. can be managed per library (for example, Reference books are converted to PDF for easy reading and portability, while fiction books get converted to .Mobi to be read on Kindle Paperwhite). Switching to something like Calibre-Web would be huge in terms of usability (I have 10+ people who utilize my collection), but it isn't feasible without this support.
I am not extremely knowledgeable in web development, but I do have programming and dev experience and would be happy to assist where possible, including testing potential future versions against my libraries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant