227
edits
Line 402: | Line 402: | ||
| | | | ||
|} | |} | ||
==Auto-creqing== | |||
[[Image:Autocreq.gif|thumb|Simple diagram of the way auto-creqing with Avdump2 works]] | |||
Avdump2 provides metadata for 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. | |||
* 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. | |||
* 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. | |||
* The creqs generated will report the user who sent the data first (for a specific file) as the creqer. | |||
* 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. | |||
* The provided data is considered "incoherent". (Indicates a bug in Avdump.) | |||
* The dump was marked unfit for file verification by an AniDB Moderator. | |||
== Development == | == Development == |
edits