Change Details

**Feature summary** (what you would like to be able to do and where): Users of #openrefine can take a simple list of Wikimedia Commons categories (one or multiple categories). The Structured Data on Commons reconciliation service then takes these categories and retrieves all file names and M-IDs from them. **Benefits** (why should this be implemented?): Regular Wikimedia Commons contributors are quite used to taking Commons categories as input / starting point in various tools. Examples include AC/DC and VisualFileChange. #glam files are usually well organized in categories, e.g. specific to the GLAM (example), to departments (example), to specific media file uploads (example). Making it possible to start with such categories will make it easier for GLAMs to contribute structured data with the help of the SDC reconciliation service and a tool like e.g. #openrefine. If we don't provide this as a functionality in the SDC reconciliation service, end users will first have to turn to another tool (e.g. PetScan) to retrieve lists of file names. This makes their workflow more convoluted (it adds an extra step) and requires them to learn to use yet another tool.

**Feature summary** (what you would like to be able to do and where): Users of #openrefine can take a simple list of Wikimedia Commons categories (one or multiple categories). The Structured Data on Commons reconciliation service then takes these categories and retrieves all file names and M-IDs from them. **Benefits** (why should this be implemented?): Regular Wikimedia Commons contributors are quite used to taking Commons categories as input / starting point in various tools. Examples include [[ https://commons.wikimedia.org/wiki/Help:Gadget-ACDC | AC/DC ]], the [[ https://commons.wikimedia.org/wiki/Commons:ISA_Tool | ISA Tool ]], and [[ https://commons.wikimedia.org/wiki/Help:VisualFileChange.js | VisualFileChange ]]. #glam files are usually well organized in categories, e.g. specific to the GLAM ([[ https://commons.wikimedia.org/wiki/Category:Images_from_Nationaal_Archief | example ]]), to departments ([[ https://commons.wikimedia.org/wiki/Category:Asian_art_in_the_Rijksmuseum_Amsterdam | example ]]), to specific media file uploads ([[ https://commons.wikimedia.org/wiki/Category:Images_from_Nationaal_Museum_van_Wereldculturen_2017_12 | example ]]). Making it possible to start with such categories will make it easier for GLAMs to contribute structured data with the help of the SDC reconciliation service and a tool like e.g. #openrefine. If we don't provide this as a functionality in the SDC reconciliation service, end users will first have to turn to another tool (e.g. PetScan) to retrieve lists of file names. This makes their workflow more convoluted (it adds an extra step) and requires them to learn to use yet another tool.

**Feature summary** (what you would like to be able to do and where): Users of #openrefine can take a simple list of Wikimedia Commons categories (one or multiple categories). The Structured Data on Commons reconciliation service then takes these categories and retrieves all file names and M-IDs from them. **Benefits** (why should this be implemented?): Regular Wikimedia Commons contributors are quite used to taking Commons categories as input / starting point in various tools. Examples include AC/DC and VisualFileChange[[ https://commons.wikimedia.org/wiki/Help:Gadget-ACDC | AC/DC ]], the [[ https://commons.wikimedia.org/wiki/Commons:ISA_Tool | ISA Tool ]], and [[ https://commons.wikimedia.org/wiki/Help:VisualFileChange.js | VisualFileChange ]]. #glam files are usually well organized in categories, e.g. specific to the GLAM ([[ https://commons.wikimedia.org/wiki/Category:Images_from_Nationaal_Archief | example ]]), to departments ([[ https://commons.wikimedia.org/wiki/Category:Asian_art_in_the_Rijksmuseum_Amsterdam | example ]]), to specific media file uploads ([[ https://commons.wikimedia.org/wiki/Category:Images_from_Nationaal_Museum_van_Wereldculturen_2017_12 | example ]]). Making it possible to start with such categories will make it easier for GLAMs to contribute structured data with the help of the SDC reconciliation service and a tool like e.g. #openrefine. If we don't provide this as a functionality in the SDC reconciliation service, end users will first have to turn to another tool (e.g. PetScan) to retrieve lists of file names. This makes their workflow more convoluted (it adds an extra step) and requires them to learn to use yet another tool.