Modelling/Content uploads: Difference between revisions

From MetaBase
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
{{Modelling navigation}}
{{Modelling navigation}}
==SPARQL==
All content uploads:


<SPARQL tryit="1">
PREFIX wb: <https://metabase.wikibase.cloud/entity/>
PREFIX wbt: <https://metabase.wikibase.cloud/prop/direct/>
SELECT ?item ?itemLabel
WHERE
{
?item wbt:P5 wb:Q22186 .
SERVICE wikibase:label { bd:serviceParam wikibase:language "en,sv,[AUTO_LANGUAGE]". }
}
</SPARQL>





Revision as of 12:13, 19 January 2024


SPARQL

All content uploads:

PREFIX wb: <https://metabase.wikibase.cloud/entity/>
PREFIX wbt: <https://metabase.wikibase.cloud/prop/direct/>

SELECT ?item ?itemLabel
WHERE
{
?item wbt:P5 wb:Q22186 .
SERVICE wikibase:label { bd:serviceParam wikibase:language "en,sv,[AUTO_LANGUAGE]". }
}

Try it!


Content uploads are specific activities aimed at enriching the Wikimedia projects with material shared with content partners, such as GLAMs. They take place in a specific time frame, have a certain subject matter and target one or more Wikimedia projects.

Number and type of contributions

➡️ Guide to resource types

Look at the following example, an upload of content from a museum, to see how we model the number and type of contributions:

**Q22194**

The reason why we use both namespace (P56) and resource type (P57) is that the File namespace on Wikimedia Commons can host different types of files: audio recordings, photos, videos, etc. Sometimes it’s useful to know the breakdown, not only how many files were uploaded, but also what kinds.

Multiple Wikimedia platforms affected

It is possible for a content upload to target multiple Wikimedia projects.

For example: You create Wikidata items for a set of museum objects and upload their photos to Wikimedia Commons.

In this case, the property number of affected content pages (P53) will have two statements, one for Wikidata and one for Wikimedia Commons.