denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
Denise ([staff profile] denise) wrote in [site community profile] dw_suggestions2010-07-24 11:01 am

Allow comm admins/journal owners to enable strict tag checking

Title:
Allow comm admins/journal owners to enable strict tag checking

Area:
Tagging

Summary:
Allow comm admins/journal owners to enable strict tag checking on their journal/comm, meaning that tags typed into the update page or the Edit Tags page would be checked for correctness instead of automatically creating tags that don't exist.

Description:
When I am tagging suggestions, it is more useful for me to retype the tags rather than choose them from the selecty thing on the Edit Tags page, since often there are many tags widely spread out and a mis-click can lose all my work. I am also not the world's best typist, so sometimes create, by accident, tags like "buzilla: migrated" instead of "bugzilla: migrated", and sometimes I forget what I called the tag, so we wind up with "journal administration" and "journal management".

This all requires a lot of tidying and tag merging. While we can do so now (HOORAY), it might be easier to allow tags in the journal/comm to be 'frozen', so that a typo doesn't create a new tag but instead throws an error.

With strict tag checking in effect, an attempt to use a tag that doesn't exist in the update page or the Edit Tags page would result in a message saying "The specified tag 'foo' doesn't exist in this journal and so was not added. Go to the [link]Manage Tags page[/link] to add it, or the [link]Edit Tags page[/link] for this entry to add a tag that does exist". (or something like that.)

The Manage Tags page would not be subject to strict tag checking, so people could still create tags there.

Poll #3904 Allow comm admins/journal owners to enable strict tag checking
Open to: Registered Users, detailed results viewable to: All, participants: 65


This suggestion:

View Answers

Should be implemented as-is.
46 (70.8%)

Should be implemented with changes. (please comment)
16 (24.6%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
2 (3.1%)

(Other: please comment)
1 (1.5%)