Feature request: simple image upload from one or multiple Flickr URL(s) about commonsextension HOT 2 OPEN

I have dug a bit in the meanwhile, trying to upload images from Flickr using its API. It's doable for power users like me, but I do think a separate feature with friendly UI would make a lot of sense for less experienced users.

Here's some input that can also help inform future development if we will work on this feature:

• I created OpenRefine projects from URL by using https://www.flickr.com/services/api/flickr.photosets.getPhotos.html (to retrieve files from one photoset or album; similar API calls can be done for files from one user, etc.)
• Licenses have a numeric code, documented and retrievable via https://www.flickr.com/services/api/flickr.photos.licenses.getInfo.html. We can (and should probably) build in a filter that will only allow uploads of files with Wikimedia-compatible licenses.
• Inside the project I then retrieve more metadata for each photo via https://www.flickr.com/services/api/flickr.photos.getInfo.html and parse it. Photo description and tags are very useful to (as a default) retrieve separately.

from commonsextension.

While discussing #90 , I realized (from conversations with cultural institutions) that generic Flickr dataset import in OpenRefine (not necessarily focused on Commons upload) is also an expressed use case.

Many cultural institutions have, in the past, uploaded many files from their collections to Flickr / Flickr Commons. Typically, over time, these files have been improved by volunteers (e.g. tags have been added). I've heard the request that institutions would like to access and retrieve these additions to process them further for cleaning and import in their own collections databases.

One example is the Biodiversity Heritage Library, which hosts over 300,000 files on Flickr, for which they would like to harvest data back (without uploading to Commons, as the images are also available there), and make that data more useful/linked as part of their LOD offerings/strategy. I've recently been in conversations with them and can ask further if this is indeed a correct use case.

from commonsextension.