Magazine Library Type

[majora2007]

Introduce a new library type called Magazines aimed for Magazines. The library behaves in the following ways:

• [x] Dedicated parser with a limited set of naming conventions
• [x] PDFs will open with the image reader instead of pdf reader due to how magazines are scanned/digitized
• [x] Due to a lack of metadata, the UI will be much thinner. No storyline tab, only Volumes/Issues
• [x] Group based on Date (March 23) and visible as Volume Number
• [ ] Reading list mode needs to ensure image reader is choosen instead of PDF when PDF is in magazine
• [ ] Support Side-car covers?
• [ ] Supports non-pdf, but by default selects only PDF file types

After talking with users, this is the current proposal:

1. There will be a limited number of parsing configurations available
2. UK World - 2018 April -> Series: UK World, Volume 2018, Issue 4. Volumes will be the Year of the magazine. Issue will derive from Month (converted to a number) or an issue number supported by # character. Issue number will override the month.
3. PDFs will open in the image reader by default.
4. Storyline tab will be removed, but Volume and Issue will remain

Supported Parsing:

Wired/
--- US/
---------Wired Vol 2010 #1.pdf
---- UK/
---------Wired Vol 2010 #1.pdf

Output:
Series: Wired (US)
Series: Wired (UK)

Wired/
--- 2018/
Wired #1.pdf

Output:
Series: Wired

Need Feedback on:

• Should these geozones be required in the series name: Wired (US)/ and not supported from parsing filenames and trying to split there?
• Should the pdf reader be used or should the image viewer be used? (Currently trying to hack the image viewer to be used is adding significant overhead)

[bhcompy]

PDFs will open with the image reader instead of image reader

I assume one of those is some other kind of reader?

[majora2007]

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.

[Enissay]

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

[majora2007]

@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?

[Enissay]

@majora2007 Here are a few concrete examples:

How it works

• Regular issues: HERE
• Special issues
  • Inside The Human Body
  • Inside Your Brain
  • Understanding Habits
  • ...

All About Space

• Regular issues: HERE
• Special issues
  • Black Holes
  • Space Exploration
  • Apollo Missions
  • ...

[Enissay]

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

[majora2007]

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?

[Enissay]

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 :>

[majora2007]

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.

[Cantello]

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

[TinuBE]

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.

[Enissay]

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