79
edits
User:YukinoAi/Tutorial Scratchpad: Difference between revisions
Jump to navigation
Jump to search
User:YukinoAi/Tutorial Scratchpad (view source)
Revision as of 00:08, 16 August 2017
, 16 August 2017no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
[//anidb.net Anime DataBase (AniDB)] is a website that provides information about Anime. | |||
=== | It keeps track of [[/anidb.net/perl-bin/animedb.pl?show=anime&aid=109|show information]] and fansub releases for them. It has some [[/anidb.net/perl-bin/animedb.pl?show=forum|social aspects]] as well. [[/wiki.anidb.net/w/AniDB:About|More info]]. Databases are only useful if they are updated frequently, so this tutorial is about keeping fansub releases on AniDB up to date. | ||
[/ | For a more concise guide, please consider this alternative:[[/wiki.anidb.net/w/Tutorial:How_to_Add_Files_for_Dummies!|Tutorial:How to Add Files for Dummies!]]. | ||
==Introduction== | |||
AniDB needs to know 3 things to create a full entry for a release: | AniDB needs to know 3 things to create a full entry for a release: | ||
| Line 31: | Line 29: | ||
https://wiki.anidb.net/w/Avdump2 | https://wiki.anidb.net/w/Avdump2 | ||
== Prerequisites: == | |||
# Obtain a file to add to AniDB. | # Obtain a file to add to AniDB. | ||
| Line 40: | Line 38: | ||
# [[/anidb.net/perl-bin/animedb.pl?show=login|Login]] and verify that account. | # [[/anidb.net/perl-bin/animedb.pl?show=login|Login]] and verify that account. | ||
== Part A) Creating an API Key == | |||
Theory: At some point, meta-information for files should be submited using Avdump2. That meta-information is initially associated with the user account that made the submission. While users normally enter usernames/passwords for authentication, Avdump2 needs a unique string of characters to update meta-data. In this context, the string of characters that authenticates a user utilizing Avdump2 is known as an <code>API Key</code> or a <code>UDP API Key.</code> | Theory: At some point, meta-information for files should be submited using Avdump2. That meta-information is initially associated with the user account that made the submission. While users normally enter usernames/passwords for authentication, Avdump2 needs a unique string of characters to update meta-data. In this context, the string of characters that authenticates a user utilizing Avdump2 is known as an <code>API Key</code> or a <code>UDP API Key.</code> | ||
| Line 49: | Line 47: | ||
On the left navigation pane, at the bottom is a section labeled <code>Account</code>. Click on <code>Settings</code>. | On the left navigation pane, at the bottom is a section labeled <code>Account</code>. Click on <code>Settings</code>. | ||
[[File:https://i.imgur.com/fEqwtnZ.png | [[File:anidb_account_settings_highlight.guide.png]] | ||
https://i.imgur.com/fEqwtnZ.png | |||
Under profile, in the main navigation window, there are tabs. Click on the one that says <code>Account</code>. | Under profile, in the main navigation window, there are tabs. Click on the one that says <code>Account</code>. | ||
[[ | [[Media:https://i.imgur.com/maGR6jL.png|anidb_accountSettings_AccountTab_highlight.png]] | ||
There should be a section called <code>UDP API Key</code> with two fields, one with a label and another empty one. | There should be a section called <code>UDP API Key</code> with two fields, one with a label and another empty one. | ||
| Line 104: | Line 104: | ||
The Avdump2 GUI will simply not respond when authentication fails. More on this later. | The Avdump2 GUI will simply not respond when authentication fails. More on this later. | ||
== Part B) Dealing With Groups == | |||
Every file entry should be associated with a release group. The group name or tag is usually in the file name, usually in brackets <code>[ ]</code>. It is important to identify the release group and to verify the group already exists in AniDB. | Every file entry should be associated with a release group. The group name or tag is usually in the file name, usually in brackets <code>[ ]</code>. It is important to identify the release group and to verify the group already exists in AniDB. | ||
| Line 170: | Line 170: | ||
For the purposes of this tutorial, it will be assumed the group name already exists. | For the purposes of this tutorial, it will be assumed the group name already exists. | ||
== Part C) On Using Avdump2 == | |||
'''Theory''': | '''Theory''': | ||
| Line 618: | Line 618: | ||
The ed2k links in the export window can now be submitted to AniDB. Detailed instructions for this are provided above. | The ed2k links in the export window can now be submitted to AniDB. Detailed instructions for this are provided above. | ||
== Part D) Understanding AniDB Change Requests (creq) == | |||
AniDB is a user-driven database. A normal way to contribute is to issue change requests (creqs for short), which means that a moderator has to approve suggested changes before they are published. Request links can usually be found on every page that has editable content for logged in users. | AniDB is a user-driven database. A normal way to contribute is to issue change requests (creqs for short), which means that a moderator has to approve suggested changes before they are published. Request links can usually be found on every page that has editable content for logged in users. | ||