-
Notifications
You must be signed in to change notification settings - Fork 17
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
[Enhancement] Add additional coverart to yaml files by web-scrapper #12
Comments
It may be possible to add all available images to the yaml, but it is be impossible to automatically check if it is a coverphoto. To extract the data yourself you may check the official APIs |
Thanks for the API link. Didn't know this. I will try it out. The schema (if multiple images are available) behind the images seems to be the following: -a-: Cover → 01-0184-98-0558 -a- JDDP1qZK.png→ 01-0184-98-0558-a-JDDP1qZK.png I checked it for several Tonies. I will proceed with some more and update here. Update 1: I found e.g. this tonie? (2000000120 → Audio Content, not a Tonie?) with just a single image. In such a case a cover cannot be found, but i think is not a real tonie, isn't it?
|
Conclusion:inside the "images" list it seems to be the following schema (this is valid for "category=Tonies"): ['images'][0] → "Cover" → Always present, filenames contains mostly "-a-" but not always From my point of view, only index [0] and [1] is relevat and usefull. [1] is alreay added. if you can add [0] as key "cover" it would be very nice. I scraped quick and dirty throug the first 100 ids and dumped only data of "category=Tonies":
|
@SciLor this could be a nice thing for the detailspage I want to add in the web gui. |
At the moment, only the path to the image with the Tonie figure itself is stored inside the YAML file.
Here is an example for Tonie 01-0001:
where image points to:
It would be very nice to additionaly store the image path to the "cover":
e.g.
Maybe is also possible to add cover image to tonies.json that i can extract URLs from a single point.
The text was updated successfully, but these errors were encountered: