Title Clearly flag tagging permissions for posts to communities
Short, concise description of the idea For many communities, creation of tags is limited to administrators-only, to prevent an ever-growing list of subcategories, misspellings, etc. For some communities, it's also the case that only administrators are able to apply tags to posts. It should be clear on the Post an Entry page whether either of these settings is in force for any given community.
Full description of the idea When managing tag settings as a community, there are the options:
Who can create new tags and add or remove tags from entries? Anyone/Members only/Administrators only
Who can add existing tags to entries? Anyone/Members only/Administrators only/Entry author and administrators
On the Post An Entry page, it is not [as far as I know!] made clear which of these settings have been chosen for any given community, which can lead to confusion when e.g. someone is trying to be helpful by tagging their entry but adding tags to entries is restricted to administrators only. (The major use-case I've seen of this is in the community vaginapagina, where administrators choose entries that are particularly well-framed and have particularly useful discussions in comments to tag, in order to build up a "resource library" of past posts, which would be less information-dense and useful if all entries relating to a topic were tagged.)
Suggested solution: when somebody selects a community from the "post to..." drop-down, or clicks "post to [community]" in the navstrip, the "tags" area of the Post An Entry page should automatically update. One possible way this could work:
* if only administrators can /tag/ entries, the tag box should be greyed out with a brief legend to the tune of "only administrators can tag entries in this community". The full list of tags could perfectly well remain accessible, with a similar legend top & bottom and all the tick-boxes greyed out.
* if only administrators can /create/ tags, the tag box should have a brief explanation along the lines of "please choose from existing tags", and typing into the box should result in searching the community's current list of tags.
An ordered list of benefits
makes system more transparent, reducing confusion for users
An ordered list of problems/issues involved
potentially processing-power-hungry
requires dynamic updates of the "post an entry" page
Short, concise description of the idea Community maintainers should have the option of giving community moderators the ability to create new tags.
Full description of the idea Managing a large community that has an extensive archiving system dependent on tags can be overwhelming, especially when new tags need to be created or removed almost every day. Moderators have the ability to approve and reject posts, but not create tags.
If you wanted to get some volunteers to help keep up with tagging in your community, you would have to set them up as maintainers.
When you view your "manage tags" section for a community, you have three options for who can create new tags: "any user," "members only," and "only maintainers." An ideal fourth option would be "only moderators and maintainers."
An ordered list of benefits
Give moderators the ability to assist the maintainer.
Relieves the pressure of having to screen for new maintainers when all you need your volunteers to do is create and manage tags.
Only adds to the options maintainers have concerning tags; doesn't take away any features we currently have.
Ooh, this has been implemented! Not exactly as I described, but actually better, so I am very happy :D
Title Add tags while approving posts to a community
Short, concise description of the idea While accepting posts to a community, you should be able to tag them, or at least be given a link to do so in the normal tagging page
Full description of the idea At the moment when approving posts you:
Start off at the Community Moderation screen which lists the posts
Click on a title to read the post (and view what tags it's been submitted with)
If you hit 'accept' you are taken to a confirmation screen
If you hit 'accept' again, you are taken back to the list of posts, with a header saying 'Success The entry has been successfully posted.'
At no point do you get the option to tag the entry you are (effectively) posting, or a link to the page from which you can do so, or even a link to the post you just approved.
I suggest that on the 'Are you sure you want to approve this entry?' page, under the checkbox saying 'Also, add user exampleusername to the list of pre-approved users for this community' that there's a line saying 'Also, tag this post with...', and a textbox with the list of tags below it, just like on the normal tagging page. The box should be pre-filled with the tags already attached to the post by the OP, again just as it works on the normal tagging page.
Alternatively (or additionally), in the next page when you're returned to the list of posts headed by 'Success The entry has been successfully posted.', that sentence should continue with the links go to the entry, tag the entry, similar to the options you get when you post to a journal or community directly.
An ordered list of benefits
Streamlines the process of adding and tagging posts in moderated communities.
Easier and quicker to check up on how a post you just approved came out, leave a comment, etc.
An ordered list of problems/issues involved
I can't imagine any other than the usual time and effort to implement. If that's a failure of my imagination let me know!
Full description of the idea Currently, community maintainers can allow entry tag editing by maintainers only, members only, all LJ users, a custom friends group (all members of that group can change tags), and (this is new - see latest news post), the entry's poster and the community maintainers. However, they can't allow tagging by the entry poster and a custom friends group, so there's no way to allow the entry poster to edit the tags when the group of trusted users is larger than maintainers (eg, maintainers and moderators, or maintainers and trusted users). This would fill in that gap.
An ordered list of benefits
More flexibility.
An ordered list of problems/issues involved
(Possibly) more complexity. (In a comment on the suggestion linked above, burr86 said the code changes required were complex, but I'm not sure whether that was a one-shot thing, or if all "entry poster + some list of people" options will be equally complex to implement.)
Short, concise description of the idea Allow community maintainers to specify one or more tags to be applied automatically to all new entries, much in the same way as default/minimum entry security currently works.
Full description of the idea Some communities are dedicated (either exclusively or as mostly) to answering questions, performing tasks, or otherwise providing services to community members or LiveJournal users at large. Others may require (or be able to use) triaging of new entries after they're posted. Setting default tags would help automate both processes.
An ordered list of benefits
Less tedious manual drudgework
Lower chance of entries falling through the cracks
An ordered list of problems/issues involved
Some maintainers may object to it for reason rooted in community politics.
May cause problems with some of the tag limits currently in force.
Short, concise description of the idea Showing the user name of the poster when editing tags on said post.
Full description of the idea As a co-maintainer of a large community, editing tags on each post can be difficult when you forget the exact user name of who posted. For example, in the community I maintain, we add tags for each member's post as "member - (usernamehere)" However, whenever we go to edit the tags, we can not see who is posting. It'd be great if the user name of the poster was still shown in the "edit tag" page.
An ordered list of benefits
Easy-access
You don't have to hit the "back" button when you forget a user name, because it's right there
An ordered list of problems/issues involved
You would probably have to alter the "edit tag" form.
Short, concise description of the idea Community Maintainers should be able to see the number of tags their communities currently use.
Full description of the idea Now that we have a maximum of 1000 tags for communities, maintainers (and community members too if possible) should be able to see the current number of tags in use in a community. Once the number goes above a few hundred, it's unreasonable to expect maintainers to count each tag one by one.
An ordered list of benefits
Better control of tags in a community.
Warning when tags get close to the 1000 limit so as to avoid error messages when posting with a new tag.
An ordered list of problems/issues involved
No Problems. No issues.
I see no problem in allowing community maintainers to see how many tags are currently in use in their community.
Short, concise description of the idea Separate options for "Who can create new tags and add/remove tags from entries?" under Tag Settings in the Community Management Page.
Full description of the idea Currently the text reads: "Who can create new tags and add/remove tags from entries?" Your choices are "Any User" "Members Only" and "Only Maintainers."
I would like the people who can Create tags to be different from those who can Add and Remove tags from entries.
For example. I would like the "Maintainer" to be the only one who can create new tags. However, I'd like "Members Only" to have the ability to "Add and Remove" tags from community posts. Currently this is not an option.
An ordered list of benefits
Better community tag management.
More options for community maintainers.
An ordered list of problems/issues involved
I see no problems in ungrouping the current options to allow for more flexibility.
Short, concise description of the idea It would be nice to have functionality available to filter or sort community posts by user.
Full description of the idea I am a member of the Embodiment community, which has nearly 4,000 members. There is interest in this community, and I imagine, in other large, active communities to have the ability to locate a user's posts quickly. This could also aid in moderation efforts, especially with problem posters.
In this community, there was a practice of tagging by user, but the available tags were quickly used up and there weren't enough tags available for all members to have their own unique tag.
Community moderators have the ability to maintain the memories function, however, with the number of members in this group, it would be too tedious to maintain.
I picture the functionality working similarly to how the tags work, loading a feed of all the individual member's posts together on one page. If the toolbar is enabled, perhaps there could be "Find Posts By User" selection box with a pull-down menu that loads with the community member's usernames.
With this functionality, members could opt-in as part of their preferences when joining a community. This way, if the member does not wish to have their posts "searchable," they don't need to. The opt-in/opt-out functionality could be added in the manage communities area, so that users could add the functionality to communities where they are already members.
Community maintainers could opt-out of the functionality at the community maintenance level, as well, if they do not wish their community's posts to be searchable.
An ordered list of benefits
Members and moderators can locate their own and others' posts quickly and easily.
Tags will be freed up for use with other categorizing of content within the community.
Little to no action needed on the part of the community members or maintainers.
Availability to opt-out will ensure privacy.
An ordered list of problems/issues involved
Mainly privacy-related issues, however, this could be remedied by an opt-in/opt-out option.
Title Always allow posters to access their own friends-only community posts
Short, concise description of the idea Allow users with community posting access to view their own members-only posts to communities they're not members of and comment on those posts.
Full description of the idea Currently, a LiveJournal user can have posting access to a community without being a member of it (usually for a closed/moderated membership community). When posting members-only to that community (either by choice or because the community was set to members-only default posting), the user will not be able to see or edit their own post, comment on it, reply to comments, etc. This makes less sense now than it may have made in the past, since the user can now be notified of comments by email, with the original post included in comment notifications. The suggested change would give posters full access to their own posts, thus letting them edit, delete, or tag them (if allowed to tag by community settings), comment on them, reply to comments, manage comment threads, etc...
This could be done either for the current "can post, can't join" access, or through a new "can post and manage own posts, can't join" access level.
An ordered list of benefits
Would give authorized posters the same access to their members-only posts that they have to their public posts (assuming public posting is allowed).
Would remove the irritation factor of not being able to correct typos, reword for clarity, or reply to comments that you're notified of.
An ordered list of problems/issues involved
Giving posters full access to their own members-only posts could prevent or hinder current uses of that feature. That could be remedied by using the new access level mentioned in the detailed description above.
