[Release] MyAnimeList.net Metadata Agent

Fribbtastic · October 21, 2020, 7:09pm

When you download the agent you have already the code. There should also be the github link here somewhere which has the repository.

anonyms · October 21, 2020, 7:12pm

i want the api ? if possible…

the updated version.

Fribbtastic · October 21, 2020, 7:19pm

It is the atarashii API so download it and set it up yourself.

The API is outdated and not maintained anymore. I’m not the developer of it. I just keep it running the best way I can so that the agent works

I’m sorry but this is not the place to get help for your own projects but for help with and only the agent.

shanegetsu · October 24, 2020, 11:49am

Hello! Quick question. Is it possible to only pull the score from MAL using this but keep everything else as the default TVDB? This is what I’m basing my question off:

Perhaps this a better way to word my question: is it possible to have MAL be a contributing agent to the metadata, but not be the primary source. And have the options to toggle which parts of metadata are pulled, like the example I provided. Either way thank you for your time, and this agent is awesome

PS totally unrelated, I think you helped me on a different issue on reddit the other day with flexget haha

Fribbtastic · October 24, 2020, 12:16pm

The MyAnimeList metadata agent does allow that other metadata agent contribute to the metadata. Currently, those agents are local media, opensubtitles and subzero. The TheTVDB Agent would need to accept the metadata from the MyAnimeList Agent for them to work together. Which it doesn’t and I doubt it will.

However, that would then mean that you still have the priority chain for the Metadata, everything that the other metadata agents in that chain provide will not be overwritten by other and following metadata agents. which means that if TheTVDB would accept metadata from my agent but provide the Rating itself, then the MyAnimeList Agent will also not just overwrite it.

That also means that this is not possible.

While I never tested this I think the interaction is also based on the same workflow, searching for the title, getting an ID, retrieving information with the ID. However, since the Names will be different between MyAnimeList and TheTVDB there wouldn’t be a 1:1 match, that is why I created the animeList so that you are able to get all those fancy images and banners. And even that isn’t accurate because even though I search for every. single. title that MAL provides the match might still be wrong.

Another thing that complicates this is that MAL uses a “by release” system while TheTVDB has it combined. So while you can have 4+ releases for High School DxD on MAL, you would still have only 1 with different internal seasons on TheTVDB. Which means that the Ratings wouldn’t represent the actual release on MAL.

I can’t say how HAMA does it, it also uses parts of my agent as a stripped-down version, so maybe that way you could achieve that.

Fribbtastic · November 12, 2020, 10:23am

You might already have seen it but if you haven’t then let me do that.

TheTVDB will rely on a subscription based model for API requests in a few months and legacy access to this API will not work anymore.

What does that mean for the Agent? Well, the MyAnimeList Agent also pulls images like posters from TheTVDB so that we are not limited to the few that exist on MAL. I also use theTVDB to create the mapping between MAL and theTVDB.

That would not work anymore “early next year”.

What options are there? We have a few:

Only rely on MyAnimeList to provide the data
Switch from TheTVDB to TheMovieDB for any additional image data
Use the new API of TheTVDB and make me cover the costs
Use the new API of TheTVDB and give the user the ability to add their own access

A thing to note here, the first point would be the easiest but would also remove those additional posters completely. Switching from TheTVDB to TheMovieDB would be a better option but the mapping would have to be rebuild from scratch.

Keeping to TheTVDB would keep most of the things as they are and only would have to be adjusted to the new API.

But that would mean paying for it. The price is IMO fair for 12 bucks a year but I would then have to cover that cost either on my own for a free project or every user would have to get their own access which I think many would be against.

So, tell me your opinion about this and what you prefer.

Since TheTVDB and TheMovieDB are only used for additional images, maybe a different, more anime specific service, could be an alternative instead. Let me know what you think

Rangulicon · December 28, 2020, 7:08am

I’m fine with whatever works best for you. I honestly think paying $12/year is completely acceptable for me, as I already use the legacy API for some private projects and will need to pay the $12 anyway. That said, I know others will not be ok with paying any amount.

Does the licensing for the API access cover the use of the API for all users of a project?

Fribbtastic · December 28, 2020, 7:44am

It should, it doesn’t seem to be any limit or restrictions with subscription-based TheTVDB API access. Still, it would add another thing I would have to cover on my own. It isn’t much but still.

I think my idea will be that I will offer that people can add their API Key and Pin in the Agents Configuration if they want theTVDB results but not replace it with the TheMovieDB. The reason for that is that I would have to map the IDs again for up to 42000 entries on Myanimelist.

But, for those that don’t want to support TheTVDB I probably will add that the fanart.tv metadata agent can provide metadata which might be enough for most.

anonyms · January 5, 2021, 4:25pm

hi fribb,
can you help me

Fribbtastic · January 5, 2021, 5:42pm

If you tell me what the problem is I can try…

Fribbtastic · April 4, 2021, 6:17pm

Just FYI, I create a Discord server that you can join if you are interested.

Fribbtastic · May 1, 2021, 10:54am

Just a heads up: I just noticed that the atarashii API has some issues, again.

The API is throwing an error

AH01071: Got error ‘PHP message: PHP Warning: strpos() expects parameter 1 to be string, object given in /var/www/vhosts/fribbtastic.net/atarashii.fribbtastic.net/src/Atarashii/APIBundle/Controller/SearchController.php on line 166\n’

Since I didn’t do anything PHP related for more than 10 years and don’t know much about what the Atarashii API uses or how it actually works I can’t figure out what the issue is.

Somehow the Search is trying to do a String operation with an object and fails because of it or rather will always return a “not found” for any search request.

If someone is more experience with PHP than I am here is the line that the error references.

With that being said, I have deactivated the API for now and any search requests will return a 503 Error. Unless someone can help to fix this issue it seems that this is the last nail in the coffin of the atarashii API and it is completely dead now.

I already started working on the v7.0.0 but am very early in development and have very little time to actually spend on it.

Until further notice, the Agent will be not functional.

ZeroQI · May 2, 2021, 1:07pm

Errors implies $content is not a string therefore probably had an issue fetching line 153:

github.com

AnimeNeko/atarashii-mal-api/blob/develop/src/Atarashii/APIBundle/Controller/SearchController.php#L153


// http://myanimelist.net/anime.php?c[]=a&c[]=b&c[]=c&c[]=d&c[]=e&c[]=f&c[]=g&q=#{name}&show=#{page}
// http://myanimelist.net/manga.php?c[]=a&c[]=b&c[]=c&c[]=d&c[]=e&c[]=f&c[]=g&q=#{name}&show=#{page}


if ($page <= 0) {
    $page = 1;
}


$downloader = $this->get('atarashii_api.communicator');


try {
    $content = $downloader->fetch('/'.$type.'.php?c[]=a&c[]=b&c[]=c&c[]=d&c[]=e&c[]=f&c[]=g&q='.$query.'&show='.(($page * 50) - 50));
} catch (Exception\ServerException $e) {
    return $this->view(array('error' => 'network-error'), 500);
} catch (Exception\ClientException $e) {
    //MAL now returns 404 on searches without results.
    //We still need the content for logic purposes.
    $content = $e->getResponse();
}


$response = new Response();
$serializationContext = new Context();

Fribbtastic · May 2, 2021, 1:30pm

Yes, that is correct and the Error message says that it is an “Object”, the URL parameters seem to work as well as far as I can tell. Anything else seems to work since there is no exception being thrown which would suggest a Server Error or a 404 by MyAnimeList. I just couldn’t get to output $content to actually what might be in it or what it is.

ZeroQI · May 2, 2021, 3:33pm

apart from dumping the filename and content in a log, one file per animeid for troubleshooting, i don’t see any alternative

Fribbtastic · May 5, 2021, 6:01am

I reactivated the API and it is back up again, don’t know what the issue was but somehow it fixed itself so the Agent is working again.

BlackAnimeKing · May 6, 2021, 12:11am

question what is a fix for anime that have multiple seasons but myanimelist only can find one season. Example: Date A Live, it found the first season but for seasons 2-4 have dates for titles instead of names is there a fix?

Fribbtastic · May 6, 2021, 4:22am

That is not surprising because MyAnimeList does not work this way. Look at the list below, MyAnimeList organizes the shows in individual releases even if they are a 2nd/3rd Seasons

Date a Live: Date A Live - MyAnimeList.net
Date a Live 2: Date A Live II - MyAnimeList.net
Date a Live 3: Date A Live III - MyAnimeList.net

Each of those has their own ID and are therefore treated as their own release.

The Agent expects you to have your Library in that format because it won’t do some crazy gymnastics between the main show and different seasons.

Therefore, to “fix” it, is to:

split up your show into multiple releases
keep it as it is but tolerate that you won’t get any episode metadata for anything beyond Season 1
Use a different Agent like TheTVDB, HAMA or anything else that better fit your Library organization. You, most likely, won’t be able to get MyAnimeList metadata with that though.

system · August 4, 2021, 4:22am

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
MyAnimeList.net Metadata Agent Dev/API Corner scanner-agent-dev	101	1457	December 20, 2019
[Release] [Alpha] [v0.1.3][v0.1.4 demo-7] Plex Anime Multi Source Agent (AMSA) Dev/API Corner scanner-agent-dev	54	3280	January 8, 2020
[Release] HTTP Anidb Metadata Agent (HAMA) Dev/API Corner scanner-agent-dev	63	2049	December 20, 2019
AniDB metadata agent Dev/API Corner scanner-agent-dev	321	19933	February 6, 2020
How do I install a new Metadata Agent? Dev/API Corner scanner-agent-dev	28	25998	December 20, 2019

[Release] MyAnimeList.net Metadata Agent

Related topics