Adding proper metadata to releases. Why are we still trying to decipher release titles, why not add a little metadata JSON file to every release and make the info available to the search API?

Also keeping multiple different versions of a release in Arr apps, like ebook and audiobook in different languages. Right now I'd need 4 Readarr instances to get the English and German audiobook and ebook versions of a book, and don't even think about letting them manage the same root folder!

[–] AtmaJnana@lemmy.world 54 points 9 months ago (1 children)

Sorry, best we can do is some unrelated ASCII art.

[–] lud@lemm.ee 10 points 9 months ago

At least they sometimes include insane rants.

[–] spiderman@ani.social 8 points 9 months ago (1 children)

and following proper naming conventions too. why can't releasers decided to choose one single naming convention together so it makes our job better to automate things?

[–] Appoxo@lemmy.dbzer0.com 1 points 9 months ago (1 children)

Have you tried maintaining a standard at work?
Now imagine if several thousand people try to decide on a common standard.

[–] lars@lemmy.sdf.org 4 points 9 months ago

Several thousand people who tend to be less likely to follow the path most traveled, no less

[–] BrianTheeBiscuiteer@lemmy.world 1 points 9 months ago

A separate file or if the first few bytes of a file contained the metadata.

[–] rapturex@lemmy.dbzer0.com 1 points 9 months ago

Readarr honestly feels like the most barebones of all the arrs. I tried it for a bit and decided to just use Calibre to manage my library.

Sure, I need to manually grab stuff but it more than makes up for that with the other features it has.

[–] EtzBetz@feddit.de 1 points 9 months ago

I actually like the release titles. It's encoded in the name that way, there's a somewhat good standard for it, and it's one file. I rarely need more info than what's in the release title. And I would dislike having to carry a separate json with me.