Allow comm admins/journal owners to enable strict tag checking

[denise]

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

View Respondents

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%)

Tags permissions: separate create new, add existing and remove

[ninetydegrees]

Title:
Tags permissions: separate create new, add existing and remove

Area:
tagging

Summary:
A slight variation on http://dw-suggestions.dreamwidth.org/327644.html. I would like the three tagging abilities to be completely separated and to have the same options.

Description:
For communities:

-- Create new tags: admins only, entry author and admins, members only, anyone.

-- Add existing tags: admins only, entry author and admins, members only, anyone.

-- Remove tags: admins only, entry author and admins, members only, anyone.


For personal journals:

-- Create new tags: only you, access only, friends*, anyone.

-- Add existing tags: only you, access only, friends*, anyone.

-- Remove tags: only you, access only, friends*, anyone.


* Which I think should be Circle BTW.

Poll #3931 Tags permissions: separate create new, add existing and remove

Open to: Registered Users, detailed results viewable to: All, participants: 31

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
22 (71.0%)

Should be implemented with changes. (please comment)
3 (9.7%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
6 (19.4%)

(Other: please comment)
0 (0.0%)

Update success page: change message for communities

[ninetydegrees]

Title:
Update success page: change message for communities

Area:
usability

Summary:
When you post to a community, have the success message for communities mimics the one you get when you post to your personal journal in order to make the link to the community journal you've just posted to longer and more visible.

Description:
Here's what it says for personal journals and where the link to the journal you've posted to starts and ends:

Your update was successful. [link]View your updated journal[/link].

Now for communities:

Update successful. You can view the updated community [link]here[/link].


I suggest changing that to:

Your update was successful. [link]View the updated community[/link].


Long links are one of the details I appreciate most on Dreamwidth so this one makes me sad. ;)

Poll #3932 Update success page: change message for communities

Open to: Registered Users, detailed results viewable to: All, participants: 29

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
27 (93.1%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
2 (6.9%)

(Other: please comment)
0 (0.0%)