Open majora2007 opened 9 months ago
PDFs will open with the image reader instead of image reader
I assume one of those is some other kind of reader?
PDFs will open with the image reader instead of image reader
I assume one of those is some other kind of reader?
The image reader is what you'd experience when opening archives. From what I saw with magazines, they are mainly scans and as such, the aren't going to need the full power (or limitations) of the PDF reader itself.
What about the folder tree requirements ? Many/most magazines have specials, and many others have geographical editions (WIRED US, UK, ME). Something like this:
wired/
├── me
├── special
├── uk
└── us
Also, some naming conventions which help keeping the collection ordered:
# 91 is the issue number
Magazine.091.2024.04.pdf
#10 is the issue number
OtherMagazine.2023.01.010.pdf
@Enissay I noticed different geographical editions. How would you expect them to be organized? I currently have them grouping under the issue.
Can you give me an example of Specials?
I noticed different geographical editions. How would you expect them to be organized? I currently have them grouping under the issue.
What do you mean under the issue, I am new to Kavita so forgive my ignorance xD
Anyhow, an easy way is as I showed above: all editions separated in sub-folders under the same Magazine name So when I open a given magazine: I would have many sections/tabs: wired_me (for middle east edition), wired_us (for US edition), ...
wired/
├── me
├── special
├── uk
└── us
What I'm asking is how you are consuming them and how they are named/grouped.
For example, based on what I've done so far, you'd have: Wired (UK) Wired (US) Wired (ME)
as different Series. Then Volumes (representing the year) and Issues. Specials I can add support for as well.
The reason I broke it up like this is because UK and US editions of the same magazine Issue 1 will have different ISBNs, so it makes sense that they are broken up by series.
Is this aligned with your own understanding or are you suggesting something else and if so, what?
Yes, that sounds reasonable enough! Not sure if the docker nightly has any of these changes but I would be glad to test it out. The current Manga/Comic options are not fully fitting my use case :>
It's in development, but nearing the end of the first pass and there will be a nightly soon. I HIGHLY encourage feedback as I don't collect magazines and this is being made to help the community.
I know that this was supposed to be exclusively for magazines, but I have some old-ish newpaper archives that are also organized like maagzines, just on a daily basis. Would this overwhelm the parser or would it be okay?
Berliner Zeitung/
├─ Berliner Zeitung - 1945-05-22.pdf
├─ Berliner Zeitung - 1945-05-23.pdf
├─ Berliner Zeitung - 1945-05-24.pdf
├─ Berliner Zeitung - 1945-05-24 (Beilage).pdf
├─ Berliner Zeitung - 1945-05-25.pdf
I have some old Magazine from Micky Maus. I have saved the Files like this:
Micky Maus Magazin ├─ 1951 ├── Micky Maus Magazin -v1951 #01.cbz ├── Micky Maus Magazin -v1951 #02.cbz ├─ 1952 ├── Micky Maus Magazin -v1952 #01.cbz ├── Micky Maus Magazin -v1952 #02.cbz ├─ 1953 ├── Micky Maus Magazin -v1953 #01.cbz ├── Micky Maus Magazin -v1953 #02.cbz
But the Structure-Parsing does not working. I have also tested with Special (SP) instead of # . still the same.
I know that this was supposed to be exclusively for magazines, but I have some old-ish newpaper archives that are also organized like maagzines, just on a daily basis. Would this overwhelm the parser or would it be okay?
Berliner Zeitung/ ├─ Berliner Zeitung - 1945-05-22.pdf ├─ Berliner Zeitung - 1945-05-23.pdf ├─ Berliner Zeitung - 1945-05-24.pdf ├─ Berliner Zeitung - 1945-05-24 (Beilage).pdf ├─ Berliner Zeitung - 1945-05-25.pdf
I think this is similar to: https://github.com/Kareadita/Kavita/discussions/2541
Having a Magazine structure in Kavita would be amazing, I’ve not imported mine yet as I’ve not got a folder structure fully sorted for them yet (I have 100s) , plus as it’s not a fully supported feature, I’m prepared to wait a bit longer.
My planned (partially implemented) folder structure is theme based, so “Sport & Leisure”, “Cooking”, “Health & Fitness” etc. and I’m considering a level below e.g Entertainment / Movies
├─ Magazines
├─ Sport & Leisure
├─ FIFA World Cup - March 2024.pdf
I noticed that when magazines (pdf) are organized like this then the specific volume does not show a count of issues in the volume:
Title/Title Vol. 2024/Title Vol. 2024 #01
Title/Title Vol. 2024/Title Vol. 2024 #02
Whereas when named like either of these, it does show the count on the volume, but not all issues are shown when clicking on the volume or even under the issues tab. Only first issue in each volume, get shown, and so all but the first issue in a volume is inaccessible.
Title/Title Vol. 2024/Title Vol. 2024 ch01
Title/Title Vol. 2024/Title Vol. 2024 01
Also, items in Title/Title Vol. 2024/Specials
don't seem to stand out in any way, and are just listed as regular issues.
Thanks for an awesome project by the way!
Introduce a new library type called Magazines aimed for Magazines. The library behaves in the following ways:
After talking with users, this is the current proposal:
Supported Parsing:
Need Feedback on: