DrTrigon added a comment.
So first thanks for the effort to all of you! Special thanks to AbdealiJK! I decided that I would like to get more involved into this so it's fine to put me in - wherever you want. :) About the proposal: 1.) I like the idea to think about including r-cnn, SPP-net, LCKSVD, VLFeat - do they have python bindings? 2.) As a name I would like to propose "metadata". Since thats excatly what all the code is about, finding, reading and generating context depending metadata. What do you think? Is there already another software package of that name out there? 3.) Personally I would vote fore this: > - A script is created in pywikibot-core which uses the pypi-catimages and handles the args required for the script to be used with mediawiki. since I am most used to this from the past. As I understand it's more straight forward with respect to deps and a stand-alone (qt) package 4.) A very nice idea but be to either define a subset of wiki commons files as a dataset (involves a lot of work - more a future project) or to upload used VOC datasets to commons. 5.) You mention some things that can be implemented like: > Prompt the user for what category should be used > if the bot finds that it is not sure of the category. > i.e. No category has a considerably higher > probability than the rest. You should not weight categories against each other. Either the score/indicators are high/strong enough to put it into a cetegory or not. This is more a question for a stand-alone app, which would just put it into a category like "uncategorized" or "needs manual intervention" based on the fact that the library does return no result. > Logging results appropriately for corner cases in > case the user wants to check results after a bulk > run and then see all the results later for > verification. This is implemented to some part already have a look at my common pages. But need generalization and improvement for sure. > Allow user to give some hints on the category > (Maybe a list of probably categories) and ignore > other categories even if they rank higher than this > one. Having kind of filter or ruleset configuration that can be modified by the end user in a config file would be nice. Parts of such a structure is actually given by how the code is organized already. This could be moved to a separate config python script thats gets loaded and included in the beginning. 6.) Unitests: +100 ;)) 7.) Kind of a personal wish but I think it could be useful for the future (e.g. your blog) as well: Could you write a short/quick step-by-step install and test howto? That would help me giving you support enormously. I think it would help to get more feedback as well. And it and essential part of the docu for later anyways. Thanks and Greetings TASK DETAIL https://phabricator.wikimedia.org/T129611 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: DrTrigon Cc: Aklapper, pywikibot-bugs-list, AbdealiJK, jayvdb, DrTrigon, tahteche, Lethexie, droid, Jay8g _______________________________________________ pywikibot-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/pywikibot-bugs
