On Thu, Feb 19, 2015 at 4:10 AM, James Hare <james.hare(a)wikidc.org> wrote:
These are media files, not byte-sized edits to
Wikidata.
Magnus' OAuth uploader has been used to upload >600K files to Commons,
nothing to sneeze at (GWT's count is at 375K):
https://tools.wmflabs.org/magnustools/oauth_uploader.php
User:Prolineserver's video conversion tool offers large file uploads
and conversion with 7 day expiry:
https://tools.wmflabs.org/videoconvert/
OAuth-created contributions can be tracked:
https://commons.wikimedia.org/w/index.php?title=Special:RecentChanges&t…
There's nothing that precludes external tools (web-based or not) from
dealing with large sets of files and uploading them via the API. If we
wanted such stashing and use Labs we'd need to clear the storage
requirements with the Labs team, but it's certainly not an automatic
blocker.
There are also examples of tools that are dealing with the kind of
complex metadata issues that GWT is dealing with, such as the Remixing
Archival Metadata Project:
https://tools.wmflabs.org/ramp/
Consider also how easy it is for others to contribute to the GWT. GWT
right now is basically Dan's baby -- and almost necessarily so,
because the intersection of "know how to write a MediaWiki extension"
and "can figure out the complex GLAM metadata problems GWT solves for"
is pretty small. If you can reduce the level of deep MW experience
required for development, you may have a better chance of the project
becoming self-sustaining in the long run, with active participation by
GLAMs in Europeana's network.
Erik
--
Erik Möller
VP of Product & Strategy, Wikimedia Foundation