Discussions from Wikipedia

Open data API in a single place

Provided by Nasjonalbiblioteket

Get early access to Discussions from Wikipedia API!

Let us know and we will figure it out for you.

Dataset information

Catalog

Nasjonalbiblioteket catalog

Country of origin

Norway

Updated

2019.12.11 00:00

Created

Available languages

English

Keywords

språkbanken, korpus, tekst, språkteknologi, språkforskning

Datasource

Official portal for European data link

Quality scoring

Dataset description

This corpus is a dump of discussion threads from the Norwegian Wikipedia, where authors discuss various issues regarding the publication of specific Wikipedia articles. The material is split into two files, one each for Norwegian Bokmål (nb.wikipedia.json) and Nynorsk (nn.wikipedia.json). Each file is a structured JSON array. One discussion corresponds to one element, with one level containing text and metadata. There are eight key/value pairs per discussion: - title: title of article under discussion - pageid: text identifier - revid: audit information - wikidata: other data - contentcategories: metadata - hiddencategories: metadata - text: discussion text - bytelength: length of text in number of bytes An example of this can be found in the pdf file (2019_wikidisc.pdf).

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

countries and EU institutions

2019

API-first since

Free API quota

for evaluation and prototypes

SLA

history and push on production APIs

FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.

Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.

Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.

Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.

Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

api.store Built by Apitalks

European data discovery with free evaluation access and production-grade API options.

About api.storePrivacy Terms of Service