jeblad created this task. jeblad added a subscriber: jeblad. jeblad added a project: Wikidata-Quality. Restricted Application added a subscriber: Aklapper. Restricted Application added a project: Wikidata.
TASK DESCRIPTION The name of the extension seems to convey an underlying intention, but it is not what the extension actually do. It is much of the same problem as AbuseFilter which is now used for edit filtering in general and not for blocking abuse. I'm not quite sure, but it seems to me that this extension supports //soft interactive edit constraints// in the context of Wikibase. It has one extension for //internal constraints// and one for //external constraints//. The one for external constraints are also somewhat special, it only use a database access. In comparison the AbuseFilter has mostly non-interactive hard edit constraints, and all of them are internal constraints. (Note that the constraints are editable for users with the correct rights even if the effect the user editing an article experience is not.) Checking the code I would perhaps go for the name used by the special page - //Validate//. This would be fairly close to what it actually does, it validates entries provided by the user. That name says nothing about the quality of the entries, it just says it is validated somehow. Still I wonder if what it really does are providing //Constraints// that the entries should be within. It is a big difference in saying that something is within some constraints and saying that the entry is valid. I would assume that a //quality// extension has means to measure the quality, that is it is not just intentional it is actual. An example would be an extension that tried to verify some factors from the entity (descriptive factors) against a model (normative factors) and give a measure (a quantity). We could argue that some report pages are sufficient to justify the name, but report pages are nothing more than maintenance pages, so I'm not sure this is a good argument. An other way to describe the problem is to ask which mental model this extension tries to support. Is it one of quality measure and/or improvement or is it one of constraining some kind of unwanted behaviour? I think it is the later, but others might think about this in other terms. Add to this that we can call anything whatever we want as long as we are consistent... And it will probably take some work to change the name. And this is probably nothing more than </rant> anyhow. TASK DETAIL https://phabricator.wikimedia.org/T101621 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: jeblad Cc: jeblad, Aklapper, Wikidata-bugs, aude _______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
