Bug ID: 61994
           Summary: Babel AutoCreate should check for duplicate categories
           Product: MediaWiki extensions
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: Unprioritized
         Component: Babel
       Web browser: ---
   Mobile Platform: ---

On enwiki, [[User:Babel AutoCreate]] has been creating several duplicate
categories. The categories differ only in capitalisation, for example:

which is a duplicate of

This seems to depend on what capitalisation users use in their #babel
invocations. (More on this specific point at bug 61993.)

I have blocked the Babel AutoCreate account on enwiki because of this issue,
but if there is a way round it I would be happy to unblock.

As well as the fix I suggested in bug 61993, I think Babel should check for
possible duplicate categories at different capitalisations, and avoid
automatically creating categories for which it finds a match.

Let's say a user uses a Babel invocation of {{#babel: Xyz}}. Before creating
the category "User Xyz", Babel should check for the existing categories "User
xyz" and "User XYZ". Checking things like "xYz" probably wouldn't be necessary.
However, it would be worth checking regional variations like "xyz-ab" versus
"xyz-AB". This has been an issue with enwiki's [[Category:User en-gb]] and
[[Category:User en-GB]].

If duplication checking is implemented, I would suggest getting Babel
AutoCreate to log possible duplicates to its user page or a user subpage so
that they can be checked by a human and created manually if necessary.

This bug might be fixed by fixing bug 61993, but the code would be more robust
if there was an explicit check for duplicate categories as well. An explicit
check would avoid the same problem happening in the future if category code
capitalisation was made configurable, for example.

You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
Wikibugs-l mailing list

Reply via email to