Change Details

Redirects (alias IDs) should be part of the JSON dumps. Redirects should be represented by separate JSON structures on the same level as entities. The dumpJson.php script should get an option that controls whether redirects should be included, excluded, or exclusive (redirects only). NOTE: this breaks the assumption of "one line, one entitiy". This would be come "one line, one entity or redirect". NOTE: A decision is needed whether we want to include redirects in the canonical JSON dump of wikidata.org, or whether we want to offer a separate dump for the redirects.

There should be a JSON dump that contains all redirects, one redirect per line (similar to the entity dumps). Such a line would probably look like `{"from":"Q123","to":"Q456"}`. This gives us the ability to later on add additional (meta) information to such redirects (by adding new keys), without breaking the dump format.

Redirects (alias IDs) should be part of the JSON dumps.There should be a JSON dump that contains all redirects, Redirects should bone represented by separate JSON structures on the same level as entitiesdirect per line (similar to the entity dumps). The dumpJson.php script should get an option that controls whether redirects should be included, excluded, or exclusive (redirects only). NOTE: this breaks the assumption of "one line, one entitiy". This would be come "one line, one entity or redirect"Such a line would probably look like `{"from":"Q123","to":"Q456"}`. NOTE: A decision is needed whether we want to include redirects in the canonical JSON dump of wikidata.orgThis gives us the ability to later on add additional (meta) information to such redirects (by adding new keys), or whether we want to offer a separatwithout breaking the dump for the redirectsrmat.