-
Notifications
You must be signed in to change notification settings - Fork 92
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
Support for xml based third party metadata formats #96
Comments
Some relevant comments on the forum: [quote="matthew" post=2058]
[/quote] [quote="selmf" post=4883] [ol] As you can see this is a feature that isn't implemented quickly. If you want to help out, you can create a bug on our Github page and start working on collecting the info that is needed to actually start the task. [/quote] [quote="Luis Ángel" post=4884] Some help with this would be great, anyone? |
A first issue I am seeing is that the way we manage libraries is placing our data in a hidden directory in the root directory of the collection in question. That does not really align very well with the concept of a central xml file to "rule them all", so we will have to think about how to handle this or if we're going to handle this at all. Another issue is that the way per-file metadata is stored is not consistent. Sometimes it is in the archives, sometimes not, it might even be "hidden" using special NTFS filesystem features. Supporting all of these variants probably doesn't make sense. Metadata format seems to be roughly what ComicVine is giving us (@luisangelsm is that more or less correct?) so mapping should be possible. We also still need some test files. If anyone is interested, Pepper and Carrot is a great open source web comic we have used for testing and showcase purposes in the past, so you could grab a cbz of it and tag it via ComicRack. |
Based on you response in the forum, I guess we could begin attempts for support with the .xml files stored within CBZ and CB7 files. The following entries have no information stored in the .xml file:
This is the content of the .xml file:
Below are screenshots of the editor itself with all entries filled in. Web alone has been filled in later, and has a entry in the .xml file. Every file scraped by cbnack's ComicRack ComicVine scraper has the following information appended:
Example: If Immortal Hulk, issue 14 were scraped:
If all else fails, we can use this information to recursively run the YAC scraper for all the files. I would need some documentation on the way YACReader stores metadata info to compile a map of CR to YAC tags. Could anyone point me in that direction? |
YACReaderLibrary stores its metadata in a hidden directory called .yacreaderlibrary which contains a directory with covers and a database file called library.db. |
I've done a basic mapping. Please take a look and let me know if I've got anything wrong. |
Thanks for taking the time to do this. This should be enough for me to writing a first draft for an importer. I still need to do some investigations on my own to see for which technical option to support XML in general we should opt and I will need to discuss this technical decision with @luisangelsm to get his input and OK on it. |
@NetherKing1357 Thanks for all the resources and research, it has been really useful. It still needs some work, but it is looking good so far. |
This issue is an offshoot of the discussion that began in the forum
Please provide support for reading metadata files written by other comic readers such as (but not limited to) ComicRack.
As far as ComicRack is concerned, metadata support would entail reading an .xml file that can be backed up to any location by the user or one stored within the comic file. The first is stored by default in
C:/Users/%user%/AppData/Roaming/cYo/ComicRack/ComicDb.xml
if direct import is to be supported by YAC.Relevant links:
http://comicrack.cyolito.com/software/windows/windows-documentation/7-meta-data-in-comic-files
http://comicrack.cyolito.com/forum/8-help/26757-where-is-the-metadata-stored
The text was updated successfully, but these errors were encountered: