Changes

Jump to navigation Jump to search
No change in size ,  02:11, 12 August 2017
no edit summary
{{eyecatch|Note|'''The ''udp_api_key'' is not your user password!!! see [[Avdump#Auto-creqing|Auto-creqing]] .}}
 
==Auto-creqing==
[[Image:Autocreq.gif|thumb|Simple diagram of the way auto-creqing with Avdump2 works]]
 
Avdump2 is the AniDB [[auto-creqing]] system. Some more or less important notes:
* To be able to use this feature you’ll need an AniDB account '''and you have to define the ''UDP API Key'' in your [[profile]]'''. All data sent to the server will be logged with IP and uid.
* It is possible to run more than one instance of Avdump2 at once, but not more than ten will work OK. At the moment ''only 10 sessions per ip are allowed by the server'', meaning the eleventh instance will terminate the first.
* There is no direct connection between data sent to AniDB and creqs generated. The data received will just be stored for later processing. There is no way to check the current status for a dump. Usually, it should take ''at least 24 hours'' from the moment you dump a file till the data actually changes. If any irregularities occur, or when there is too much data pending, it will take more time.
* The creqs generated will report the user who sent the data first (for a specific file) as the creqer.
* You may dump files currently not in the database. The data is still stored and will be used later if/after the file has been registered.
* Files creqed by the new system will be locked, meaning some fields will not be possible to change. Notify a moderator if you are '''sure''' that some of the data locked for a specific file is wrong.
 
===Why didn't this file get dumped?===
* The file in AniDB is registered with wrong size and/or ED2K hash.
* The package never reached the server.
* The decryption or decompression failed at server side (rare).
* The dump is not valid XML (rare).
 
===Why isn't this file verified?===
Even if the file is dumped it doesn't mean it will get auto-creqed (and verified). Here are the reasons:
* The file is corrupt/invalid ([http://anidb.net/perl-bin/animedb.pl?show=avmf&do=xml&avid=76226 example]).
* The provided data is considered "incoherent". (Indicates a bug in Avdump.)
* The dump was marked unfit for file verification by an AniDB Moderator.
 
 
===Avdump2 on Linux===
Thanks to Mono, Avdump2 runs natively on Linux as well. However, as most development effort goes into the Windows version and due to the heterogenity of Linux distributions, running Avdump2 on Linux isn’t as straightforward as running it on Windows. All Linux-related usage notes can be found on the [[Avdump2 on Linux]] page.
==Changes From Avdump Classic==
</Exceptions>
</FileExceptions>
 
===Avdump2 on Linux===
Thanks to Mono, Avdump2 runs natively on Linux as well. However, as most development effort goes into the Windows version and due to the heterogenity of Linux distributions, running Avdump2 on Linux isn’t as straightforward as running it on Windows. All Linux-related usage notes can be found on the [[Avdump2 on Linux]] page.
 
 
==Auto-creqing==
[[Image:Autocreq.gif|thumb|Simple diagram of the way auto-creqing with Avdump2 works]]
 
Avdump2 is the AniDB [[auto-creqing]] system. Some more or less important notes:
* To be able to use this feature you’ll need an AniDB account '''and you have to define the ''UDP API Key'' in your [[profile]]'''. All data sent to the server will be logged with IP and uid.
* It is possible to run more than one instance of Avdump2 at once, but not more than ten will work OK. At the moment ''only 10 sessions per ip are allowed by the server'', meaning the eleventh instance will terminate the first.
* There is no direct connection between data sent to AniDB and creqs generated. The data received will just be stored for later processing. There is no way to check the current status for a dump. Usually, it should take ''at least 24 hours'' from the moment you dump a file till the data actually changes. If any irregularities occur, or when there is too much data pending, it will take more time.
* The creqs generated will report the user who sent the data first (for a specific file) as the creqer.
* You may dump files currently not in the database. The data is still stored and will be used later if/after the file has been registered.
* Files creqed by the new system will be locked, meaning some fields will not be possible to change. Notify a moderator if you are '''sure''' that some of the data locked for a specific file is wrong.
 
===Why didn't this file get dumped?===
* The file in AniDB is registered with wrong size and/or ED2K hash.
* The package never reached the server.
* The decryption or decompression failed at server side (rare).
* The dump is not valid XML (rare).
 
===Why isn't this file verified?===
Even if the file is dumped it doesn't mean it will get auto-creqed (and verified). Here are the reasons:
* The file is corrupt/invalid ([http://anidb.net/perl-bin/animedb.pl?show=avmf&do=xml&avid=76226 example]).
* The provided data is considered "incoherent". (Indicates a bug in Avdump.)
* The dump was marked unfit for file verification by an AniDB Moderator.
79

edits

Navigation menu

MediaWiki spam blocked by CleanTalk.