fiddlingfrog: (Default)
[personal profile] fiddlingfrog

Title:
Add a new HTML tag to allow navigation across multiple entries in a single tag

Area:
tags, entries

Summary:
Across the web, multi-part series often have a section of navigation links to enable readers to find their way across multiple pages, articles, etc... First/ last page, prev/ next, list all pages/ articles... there's lots of different ways to make it easier for the reader. What I propose is to add a new HTML tag, like <cut>, that will auto-generate some navigation links when included in an entry.

Description:
This suggestion is based on an idea that I had on LiveJournal last year [ http://suggestions.livejournal.com/1107879.html?thread=17520039#t17520039 ]. The idea is that when an author has written something in several parts, whether that is fanfiction, how to articles, a travelogue, or a guide, the existing tag navigation is often insufficient for a reader to browse the entire series.

Say I've written several different entries about my experiences traveling in Scotland. I could just rely on the reader to click on the "Scotland 2012" tag and find all the entries. If I have more entries in this tag than fit on a single page, the reader might miss some. Alternatively, I could edit every entry in the series whenever I publish a new entry, making sure to link to the next in the series, and maybe the latest, and possibly make sure that each entry in the series links to all the others. But that's a lot of work, and it gives a high likelihood for error.

So what I suggest instead is a custom HTML tag that will auto-generate navigation links. At the end of any entry in my series I could add a tag like <series tag="scotland 2012">. This would be displayed in the entry like so:
scotland 2012
First - Prev - Next - Last
Subject of 1st entry
Subject of 2nd entry
Subject of 3rd entry
* Subject of 4th entry, the one currently being read
Subject of 5th entry

If the series contains more than five entries, the fifth and subsequent entries should be hidden behind a link to save space. In addition, there could be several options. Perhaps you can include a title, so instead of saying "corruption" the navigation link header might read "Bribery in City Hall". Maybe the author would like the articles displayed in reverse-chronological order. Or maybe the author wants to include the date/time stamps along with the entry subject line.

One advantage of this approach is that no new UI is needed. All of the links are included as part of the entry, instead of attached to the entry, so no new buttons are necessary. And since the links are auto-generated, authors only have to remember to add the 'series' tag once, when they first write the entry, instead of having to constantly update every entry in the series.

Poll #14594 Add a new HTML tag to allow navigation across multiple entries in a single tag
Open to: Registered Users, detailed results viewable to: All, participants: 44


This suggestion:

View Answers

Should be implemented as-is.
18 (40.9%)

Should be implemented with changes. (please comment)
11 (25.0%)

Shouldn't be implemented.
8 (18.2%)

(I have no opinion)
7 (15.9%)

(Other: please comment)
0 (0.0%)

fluffymormegil: @ (Default)
[personal profile] fluffymormegil

Title:
Option to disable tag auto-completion

Area:
tags

Summary:
Add an option to disable tag auto-completion.

Description:
The tab auto-completion system interacts poorly with at least older (2.x) Android browsers, because the text entry system on those devices does not support "overtype to erase selected text". It would be useful to have an option to disable tag autocompletion, so that users of such devices can fill in tags without heavy use of backspace.

Poll #14592 Option to disable tag auto-completion
Open to: Registered Users, detailed results viewable to: All, participants: 32


This suggestion:

View Answers

Should be implemented as-is.
12 (37.5%)

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

Shouldn't be implemented.
11 (34.4%)

(I have no opinion)
9 (28.1%)

(Other: please comment)
0 (0.0%)

marahmarie: Sheep go to heaven, goats go to hell (Default)
[personal profile] marahmarie

Title:
Expose Tag Count Tooltip Option to Customize Style User Interface, Make New CSS Class for Tag Count

Area:
tags, styles

Summary:
Based on a thread in the Style System community (http://style-system.dreamwidth.org/102224.html?thread=826448#cmt826448) I'm positing that we expose the sidebar tag count tooltip option to the Customize Style User Interface (basically, to put an option to use it on this page: http://www.dreamwidth.org/customize/options?group=modules) and to make the option a checkbox choice with the label "display tag count only as a tooltip". To be clear, this was originally user ninetydegree's idea, but I was given her permission to post it here if she didn't submit it first herself. :)

Description:
Right now as a DW user you may, for aesthetic or other reasons, not want to expose the tag count to users in your sidebar (a 'tag count' being how a sidebar tag might say, for example, "0 uses" or "20 uses" right after it). Rather than hide it via clumsy CSS ('clumsy' being, um, the only CSS guidance I could offer in that thread, given that there is no specific CSS class for the tag count) the idea is to expose the "display tag count only as a tooltip" in the Customize Style/Modules user interface to give users that option. Right now they can only access it by creating a custom theme layer and coding it in via DW's s2 programming language.

I'd also like to suggest that we have a separate CSS class for sidebar tag counts so we can style them however we want (this is the part of the suggestion I think DW designers will benefit from the most - but exposing the tooltip option also sounds like awesome sauce to me).

Poll #14588 Expose Tag Count Tooltip Option to Customize Style User Interface, Make New CSS Class for Tag Count
Open to: Registered Users, detailed results viewable to: All, participants: 26


This suggestion:

View Answers

Should be implemented as-is.
14 (53.8%)

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

Shouldn't be implemented.
1 (3.8%)

(I have no opinion)
11 (42.3%)

(Other: please comment)
0 (0.0%)

pifour: (Default)
[personal profile] pifour

Update: Good solution from [personal profile] ratcreature  see: http://dw-suggestions.dreamwidth.org/1408695.html?thread=4462775#cmt4462775

Title:


Quick and handy access to entries with multiple tags

 

Area:
tags

Summary:
Quick and handy access to entries with multiple tags

Description:
I suggest new representation of tags in a drop-down menu. When mouse pointer is over tag of the first level (T1), appears a submenu. In the submenu is tags (T11, T12 ...), which are available for entries with the tag T1. When you click on a submenu, as T11, open records that have tags T1 and T11. And so on.

Example:

Entries:

N1 with tags cats, video.
N2 with tags interesting, video.
N3 with tag interesting, pics.
N4 with tag pics.
N5 with tags cats, pics.
N6 with tags pics.
N7 with tags video.
N8 with tags cats, video.

Then tags menu is:

cats.....................opens N1, N5, N8.
.....pics................opens N5 (entries with tags cats and pics).
.....video...... ........opens N1,N8.
interesting..............opens N2, N3.
.....pics................opens N3.
.....video...............opens N2.
pics.....................opens N3, N4, N5, N6.
.....cats................opens N5.
.....interesting... .....opens N3.
video....................opens N1, N2, N7, N8.
.....cats................opens N1, N8.
.....interesting... .....opens N2.

Number levels in menu equals max number tags in entries.

Update: Good solution from [personal profile] ratcreature  see: http://dw-suggestions.dreamwidth.org/1408695.html?thread=4462775#cmt4462775

Poll #12622 Quick and handy access to entries with multiple tags
This poll is closed.
Open to: Registered Users, detailed results viewable to: All, participants: 40


This suggestion:

View Answers

Should be implemented as-is.
2 (5.0%)

Should be implemented with changes. (please comment)
21 (52.5%)

Shouldn't be implemented.
8 (20.0%)

(I have no opinion)
9 (22.5%)

(Other: please comment)
0 (0.0%)

equationhouse: - (Default)
[personal profile] equationhouse

Title:
Having the option of tags appearing at the TOP of entries

Area:
tags

Summary:
Having the option of displaying tags above the actual text portion of an entry would be beneficial in many ways, detailed below.

Description:
As things currently stand, I am under the impression tags appear under the main portion of an entry, and that there is no way to choose otherwise. I remember on LJ there was an option to display many things about an entry above it instead, such as mood, location, etc. I feel that having similar options here on DW, particularly regarding tags, would benefit a great number of people. Particularly, I know that it would help myself and a great deal of my friends who would benefit from having a choice other than completely cutting entries that might be of an upsetting or "triggering" nature.

Tagging entries as triggering is, so far, rather ineffective, since people tend not to see the tags until they have already read at least a good portion of an entry. If these tags were, however, to be placed above an entry, it would be much easier to avoid reading potentially upsetting entries if desired.

Poll #12621 Having the option of tags appearing at the TOP of entries
This poll is closed.
Open to: Registered Users, detailed results viewable to: All, participants: 46


This suggestion:

View Answers

Should be implemented as-is.
26 (56.5%)

Should be implemented with changes. (please comment)
2 (4.3%)

Shouldn't be implemented.
1 (2.2%)

(I have no opinion)
15 (32.6%)

(Other: please comment)
2 (4.3%)

tree: a figure clothed in or emerging from bark (Default)
[personal profile] tree

Title:
Change wording of error message re: exceeding max number of tags

Area:
tags

Summary:
The error you get if you try to add new tags when you've reached the tag limit for your account type doesn't make sense.

Description:
The community het_reccers was just imported from LJ, with its 1800+ tags. Prior to upgrading to a premium paid account, I tried to add new tags (forgetting about the tag number limit for free accounts) and got an error.

Here's a screenshot of the error message: http://i.imgur.com/95L5j.jpg. It reads as follows:

Error
Adding this tag would exceed your maximum of 1000 tags. Please remove at least 814 of the following new tags: [2 tags are listed]

I understand the meaning of the message, but obviously it's not possible to subtract 814 from 2 in this situation. I think a better message would be something like, "Adding this tag would exceed your maximum of n tags. You will not be able to add new tags until you delete n existing tags or upgrade your account." And then have a link to the FAQ about paid accounts and/or the Shop.

This might need to be a new suggestion, but I also thought of the possibility of being able to pay for a la carte tag bundles. Like being able to purchasing 100 extra tags for n points. I can see that being useful for communities like het_reccers. We're not that far from our 2000 limit now. Egads.

Poll #12342 Change wording of error message re: exceeding max number of tags
Open to: Registered Users, detailed results viewable to: All, participants: 52


This suggestion:

View Answers

Should be implemented as-is.
42 (80.8%)

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

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
7 (13.5%)

(Other: please comment)
0 (0.0%)

azurelunatic: A glittery black pin badge with a blue holographic star in the middle. (Default)
[personal profile] azurelunatic

Title:
Retrofit entry tag-only interface?

Area:
entries, tags

Summary:
Retrofit the entry tagging (tag-only) interface to include New Tag Awesomeness, and degrade gracefully to the current interface if the browser doesn't support it.

Description:
I find the autocompleting tag whatsit to be basically the best thing ever, enough that I miss it when using the tag-edit-only interface on entries that need retagging. (Related: I have too many tags.)

Would it be feasible to add the fancy new tag functionality to the entry tagging page?

Some points to consider:

Would it degrade well for devices that just can't cope with the fancy tagging? (If not, it's a non-starter.)
Would it affect the page load significantly on slow connections?

Poll #12200 Retrofit entry tag-only interface?
Open to: Registered Users, detailed results viewable to: All, participants: 52


This suggestion:

View Answers

Should be implemented as-is.
34 (65.4%)

Should be implemented with changes. (please comment)
5 (9.6%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
13 (25.0%)

(Other: please comment)
0 (0.0%)

marahmarie: Sheep go to heaven, goats go to hell (Default)
[personal profile] marahmarie

Title:
Add the ability for logged-in users to visibly sort the Tags Page by access level.

Area:
Styles

Summary:
There is currently a hidden feature on the Visible Tags Page: the ability to show the approximate access-level assigned to each tag. I would like DW to add CSS or a combination of JavaScript and CSS to all our journals to show the hidden feature to everyone who opts-in.

Description:
Currently the Visible Tags page shows all your tags in a single, alphabetically sorted list but does not *visibly* indicate which tags are used on private, access-list-only or public posts. So one day about a year ago I asked myself, "Why not?" and wound up writing CSS that exposed the access-level of all my private and access-list-only posts. This became a fantastic sorting system since I have no other way to tell what I've thrown where without using the Manage Tags page, which can be kind of awkward and time-consuming.

So a week ago I took this a little further and refined the CSS so that 1) only logged-in users see the access-levels alongside each tag and 2) logged-in users see the exact access level used on each tag - public, private, or access-list-only. Here's a screen cap of my current Visible Tags page using my latest CSS for it (logged-in view - logged-out you won't see any of the extra information shown in this screen cap):
http://i287.photobucket.com/albums/ll128/marahstest/expose_access-level_tags_page.jpg

What I'm humbly hoping for is this system of sorting tags by access-level, as seen in the screen cap, gets adapted site-wide either as the default view on the Visible Tags page (of course, it will be visible to logged-in users by access-level only) or else becomes an opt-in default option (which is where JavaScript would probably come into play; otherwise, this is a pure CSS hack).

There are a few possible issues with adapting this styling: 1) it may take more firepower to serve up the additional CSS (but I'm thinking it would not be enough to crash servers or do anything that dramatic as things stand; it's just hard to calculate how much this might slow things down without knowing how much firepower DW has to spare) and 2) there is currently an issue where if you use a tag at more than one access level (say you use your "cats" tag both publicly and on several access-list-only posts) it will get an HTML tag indicating it's for public use only, which means DW won't be able to style it with the specific CSS to reflect that you used it three times publicly and three times for access list readers. Until that split-usage quirk is fixed, my idea makes for an imprecise-at-best look at how your tags are being used. But I think it's still better than not having any sorting system in place at all; in the meantime you can still use your Manage Tags page to drill down more precisely.

If this were to get adopted, I could see future improvements to it such as sorting tags by access level on the Visible Tags Page instead of sorting them entirely alphabetically as we do now, adding the ability to style each access level separately, and so on.

Poll #11751 Add the ability for logged-in users to visibly sort the Tags Page by access level.
Open to: Registered Users, detailed results viewable to: All, participants: 47


This suggestion:

View Answers

Should be implemented as-is.
15 (31.9%)

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

Shouldn't be implemented.
3 (6.4%)

(I have no opinion)
28 (59.6%)

(Other: please comment)
1 (2.1%)

Freeze Tag

Sep. 2nd, 2012 01:07 pm
azurelunatic: A glittery black pin badge with a blue holographic star in the middle. (Default)
[personal profile] azurelunatic

Title:
Freeze Tag

Area:
tags, community management

Summary:
Freeze any given entry's tags against change by non-owner/non-admin even when general tagging permissions say otherwise (with optional reason why). This might be most useful for community management, but could be useful for personal journals too.

Description:
This case came up in writing another suggestion. Sometimes the tags on a specific entry should not be modified. This might be because a community administrator has set the tags as they should be and no one should mess with them by accident, or perhaps because a situation has started to get out of hand in a particular entry, and the battle has progressed to the tags.

Ordinarily the community's tag permissions are as they ought to be, and it would unfairly penalize the community members to disallow them from their ordinary tagging behavior because of this one special (or egregious) case.

Ideally, the edit tags link should not even be shown on that entry for non-admins, but any attempt to edit the tags from someone who is not a community administrator should result in an error message saying that changing the tags on this entry is not permitted because a community admin set it that way, and optionally with a reason why.

Admins should be able to unfreeze the tags on the entry.

If an entry has frozen tags, should the admin be able to change them without first unfreezing them? On the one hand, an admin, like a honey badger, should be able to do what they want. On the other hand, perhaps the tags are frozen also against admin carelessness or so a different community administrator doesn't accidentally mess up something the first admin set up. I suppose a "The tags on this entry are frozen [because reasons]. Ticky this box if you want to change them, and also ticky that box if you want to leave them unfrozen" message would protect against accidental changing while allowing the admins to keep doing their thing without going too far out of their way.

I see this as mostly useful in communities, but don't see a reason to keep personal journals from using it.

Poll #11691 Freeze Tag
Open to: Registered Users, detailed results viewable to: All, participants: 54


This suggestion:

View Answers

Should be implemented as-is.
37 (68.5%)

Should be implemented with changes. (please comment)
2 (3.7%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
14 (25.9%)

(Other: please comment)
1 (1.9%)

azurelunatic: A glittery black pin badge with a blue holographic star in the middle. (Default)
[personal profile] azurelunatic

Title:
Special "admin/owner only" add/remove setting for certain tags or maybe overhaul tagging permissions

Area:
tags, permissions

Summary:
Allow journal owners or community administrators to designate tagging permissions by tag. Tags as they are actually used contain both general topic labels and other things that are suitable for use by a larger group, and administrative tags that ought only to be used by people with permission to act administratively.

Description:
Currently, tag permissions are:

Who may see the tag (determined by security level of the entries to which the tag is attached)
Who may add any existing tag to an entry
Who may remove a tag from an entry & who may create new tags to apply to an entry

Adding, removing, and creating tag permissions can be based on community membership or community adminship, or personal journal general access/access group membership.

This is useful as far as it goes. However, tags as they are actually used have developed some other interesting differences.

In some communities, there are often special tags that are reserved for marking administrative actions. Using dw_suggestions as an example, there are several. http://dw-suggestions.dreamwidth.org/tag/

"admin" and "admin: opinion post" are clearly administrative. All of the "bugzilla:" tags are also administrative, and are used one at a time by [staff profile] denise at various points in the suggestions process for very specific purposes. The rest of the tags are descriptive of the content of the suggestion, and can be usefully applied by any interested layperson with attention to detail.

Other communities do similar things with tags, and make things work by either restricting the application of tags to administrators, or trusting the sensibility and goodwill of the community to not apply tags that are clearly designated as administrative with reckless abandon.

To fit this need roughly and based on the use model I described above, tags could be divided into two baskets, one reserved for admins/journal owners, and one that uses the existing settings. However, that doesn't quite satisfy me.

What if it were possible to:

* Set default permissions for newly created tags (tags that already existed at the time of swapover would go with the current account settings for global tag permissions)
* (unchanged) Set permissions for who may create new tags
* Set permissions for who may apply this particular tag to any entry
* Set permissions for who may remove this particular tag from any entry

It should be possible to modify individual tag permissions either singly or in multiple selected groups, and should be possible to sort the tag listing based on permissions.

I defer to people with better UI experience than I have on how that should be accomplished, because it would add an extra layer of WTFery on top of an already complex interface.

When applying tags to an entry, a user should only have the tags that they are allowed to apply be in a list that can be selected from. This would add possibly significant processing overhead to every load of a tagging page, and could be a reason to restrict some of the fancy stuff to paid accounts/accounts that have under the legal limit of tags. (This would prevent me in particular from using this until I got my tags pared down, which I think is only fair.)

I can see arguments for and against displaying a second list of tags that exist and are visible to the current user, but cannot be applied by them.

For: they exist, it makes sense to show them so they know that the problem is not that the tag does not exist; the refrain of "Mods, can you [tag request]?" is familiar in communities with restricted tagging. Having the list on the page to modify an entry's tags saves a click.
Against: why show you something you can't use? Link the full tag list if need be.

The ability to specifically designate a tag as "can be applied by [more permissive group than community admins]" might also solve the problem where admins create tags but don't attach them to an entry, so the tags remain admin-viewable-only until they're used.

Poll #11690 Special "admin/owner only" add/remove setting for certain tags or maybe overhaul tagging permissions
Open to: Registered Users, detailed results viewable to: All, participants: 43


This suggestion:

View Answers

Should be implemented as-is.
23 (53.5%)

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

Shouldn't be implemented.
4 (9.3%)

(I have no opinion)
13 (30.2%)

(Other: please comment)
0 (0.0%)

kaberett: Overlaid Mars & Venus symbols, with Swiss Army knife tools at other positions around the central circle. (Default)
[personal profile] kaberett

Title:
Include poster's username on "edit tags on an entry" page

Area:
tagging, community features

Summary:
Provide more information - specifically, the original poster's username - on the "Edit Tags on an Entry" page.

Description:
The "Edit Tags on an Entry" page currently has the fields:

* subject
* current tags
* [journal]'s tags
* entry text

This is fine if you're tagging within your own journal. However, when I'm tagging in a community, and especially tagging dw_suggestion's posts, I sometimes get curious about Who Submitted This, & it would be lovely to be able to see that information at the same time as tagging, rather than having to click about (which disrupts my concentration).

I can also see this being useful for batch-tagging in communities where posts are routinely tagged with the name of the poster.

Possible solutions include:

(1) always showing the username of the poster on the Edit Tags on an Entry page
(2) show the username of the poster only when editing tags on an entry posted to a community

Downsides: you end up with one extra uneditable line on the Edit Tags on an Entry page. Personally I can't get too worked up about that. ;)

Poll #11569 Include poster's username on "edit tags on an entry" page
Open to: Registered Users, detailed results viewable to: All, participants: 47


This suggestion:

View Answers

Should be implemented as-is.
31 (66.0%)

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

Shouldn't be implemented.
1 (2.1%)

(I have no opinion)
14 (29.8%)

(Other: please comment)
1 (2.1%)

syderia: lotus Syderia (Default)
[personal profile] syderia

Title:
Default security settings for tags

Area:
security settings

Summary:
Journals would still have a global default access setting, but it would be possible to set other access settings for specif tags - those settings would then override the default when chosen on an entry.

Description:
In case two tags were chosen with different settings, the more restrictive one would be picked.
The possibility to manually set the access level for the entry would stay there and would override any tag-specific level.

This might be a nice paid feature. The number of tags that could be associated to another access setting could be limited (and scaled depending on the type of account).

Poll #11555 Default security settings for tags
Open to: Registered Users, detailed results viewable to: All, participants: 45


This suggestion:

View Answers

Should be implemented as-is.
11 (24.4%)

Should be implemented with changes. (please comment)
2 (4.4%)

Shouldn't be implemented.
15 (33.3%)

(I have no opinion)
16 (35.6%)

(Other: please comment)
1 (2.2%)

[personal profile] swaldman

Title:
List box on the Manage Tags page should remember position

Area:
Manage Tags page

Summary:
The list box on the Manage Tags page should remember your position when the page is reloaded.

Description:
http://www.dreamwidth.org/manage/tags has a list box with a huge great list of all the tags in my journal. Sometimes I go through merging or renaming to catch spelling errors. (OK, I have done this once. I like to imagine I am more organised). When doing this, when I click Rename, Merge, or whatever, it does the requested operation and then reloads the page with the list of tags back at the top. When the list is long, this is annoying.

I don't care about long-term , but it would be good if it could remember my position in the list within a single session.

Poll #11119 List box on the Manage Tabs page should remember position
Open to: Registered Users, detailed results viewable to: All, participants: 53


This suggestion:

View Answers

Should be implemented as-is.
38 (71.7%)

Should be implemented with changes. (please comment)
1 (1.9%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
14 (26.4%)

(Other: please comment)
0 (0.0%)

kaberett: Overlaid Mars & Venus symbols, with Swiss Army knife tools at other positions around the central circle. (Default)
[personal profile] kaberett

Title:
Clearly flag tagging permissions for posts to communities

Area:
tagging, community administration, posting, error messages

Summary:
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.

Description:
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 LJ 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 with a useful legend. One way I envisage this working:

* 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.

Poll #10449 Clearly flag tagging permissions for posts to communities
Open to: Registered Users, detailed results viewable to: All, participants: 68


This suggestion:

View Answers

Should be implemented as-is.
63 (92.6%)

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

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
5 (7.4%)

(Other: please comment)
0 (0.0%)

azurelunatic: A glittery black pin badge with a blue holographic star in the middle. (Default)
[personal profile] azurelunatic

Title:
Useful control links on search page

Area:
search, entries

Summary:
When searching your own entries, get additional useful links, such as edit entry, edit tags. This could possibly also include control links for entries not in your own journal, if you have permission to retag in that journal, or for communities where you are an administrator.

Description:
Sometimes, when you're searching entries, you're searching for the purpose of editing the entry or its tags. In those cases, you have to first open the entry, then go to edit the tags or the entry.

It could be helpful to offer links to edit the entry or tags.

User interface-wise, the links could possibly be fit in without disrupting the flow too much or making it take up any more lines:


Current:

[personal profile] azurelunatic: 53 tweets for 2011-2-7
... , and jdn. Monday, 2015: @mishacollins Who's having problems with their polypodes? Monday, 2017: Pie doesn't have tentacles, but cupcakes do. http://www.etsy.com/listing/61287471/cupcaketapus Monday, 2018: HEAVENS ABOVE, SEX WITHOUT LOVE Monday, 2024: @ ...
Tags: twitter
Posted: 2011-02-07 23:55:00


Proposed:

[personal profile] azurelunatic: 53 tweets for 2011-2-7 (edit)
... , and jdn. Monday, 2015: @mishacollins Who's having problems with their polypodes? Monday, 2017: Pie doesn't have tentacles, but cupcakes do. http://www.etsy.com/listing/61287471/cupcaketapus Monday, 2018: HEAVENS ABOVE, SEX WITHOUT LOVE Monday, 2024: @ ...
Tags: twitter (edit)
Posted: 2011-02-07 23:55:00

Poll #9058 Useful control links on search page
Open to: Registered Users, detailed results viewable to: All, participants: 52


This suggestion:

View Answers

Should be implemented as-is.
31 (59.6%)

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

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
21 (40.4%)

(Other: please comment)
0 (0.0%)

thnidu: my familiar. "Beanie Baby" -type dragon, red with white wings (Default)
[personal profile] thnidu

Title:
Make the tag "security" label useful, or remove, or at least explain it

Area:
tags

Summary:
The "security" label on the tag management page is (1) redundant and (2) misleading. (1) It is simply the lowest level (highest line on the chart right above it) that applies to any post tagged with it. (2) By being there at all, it suggests that it is useful, e.g., a settable value for "who can see this tag".

Description:
See Request #12096, under "Site Interface". I asked about the tag, and was told
"Tag security is tied to entry security. If the posts used for those tags are public, then the tags will also be public."

My reply:

So, if I use a tag only for filtered posts, the page for that tag will say "Security: filtered". But the first time I use it for a public post, the "security" level will change to "public". In other words, it's exactly equal to the label on the lowest security level (highest line on the list just above it) with a non-zero count.

The screen is deceptive. Giving a "security" level for the tag strongly implies that there is a security level ASSOCIATED SPECIFICALLY with the tag, and that it can be set somehow. I've been assuming I can set security for any post independent of any other post and any other setting. This "security" field is not only useless -- totally redundant with the list above it -- but misleading as well. Either

1. make it meaningful -- e.g., by letting the user set "who can see this tag" (I may not WANT everyone to know that I've tagged a particular post as "love life", or that I have such a tag!)
2. or rename it, e.g., "lowest security level of posts with this tag", or something shorter that says the same thing, if you can think of a wording
3. or remove it entirely.

Is the meaning of this field described anywhere online? Unless you follow option 3, there should at least be a link on the "security" label to explain it.

My preference is #1. I know that would take more work than #2 (+ the info link), but that would be adding something useful.

Poll #9006 Make the tag "security" label useful, or remove, or at least explain it
Open to: Registered Users, detailed results viewable to: All, participants: 65


This suggestion:

View Answers

Should be implemented as-is.
28 (43.1%)

Should be implemented with changes. (please comment)
8 (12.3%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
28 (43.1%)

(Other: please comment)
1 (1.5%)

amber: ⌠ ART ⊹ Panda&Girl ⌡ (Default)
[personal profile] amber

Title:
the ability to select multiple tags when tracking users and communities

Area:
tracking communities and journals

Summary:
Being able to select multiple tags at once on the tracking page for users and communities.

Referring to this page:

http://www.dreamwidth.org/manage/tracking/user?journal=dw_news

(using dw_news as an example)

Description:
When adding or removing tags from the tag page or an entry, users can type tags or select from the drop-down menu, and when editing tags the ability to select or delesect multiple with shift or ctrl clicking is incredibly useful.

I was wondering if something like this could be implemented when selecting tags to track for a community or journal? As the current system stands, if I wish to receive notifications a community with tags for, say, multiple pairings, and I want to track at least fifteen of those tags, I have to select one from the dropdown menu, track it, select another, track it, etc. It isn't a major inconvenience but <i>especially</I> now that I am retracking a lot of communities and users that have imported from LiveJournal, I would prefer to be able to mass-select a whole bunch of tags. I feel like maybe this is a feature that would also be appreciated by the LiveJournal rpers who have recently crossed over.

The reason I mention shift/ctrl clicking is because I feel like it is intuitive and requires very little explanation on the page, and it is a system already in place when it comes to tagging entries. I think being able to type something and see the options that appear (i.e. typing "character" and getting all tags that include the word character) would be incredibly helpful for communities or users with many, many tags especially if they are making use of the tiered tag system.

The potential drawbacks that I can see...

I don't know enough about code to be able to say if this is a large recode job, but it feels like the code used for selecting tags in the "edit tags on this entry" pages is different to the "track this community" pages.

Clutter: a small dropdown box is simple and takes little room. This idea may require more space on the page to be able to enter or select tags.

Users may accidentally select more or incorrect tags to track and because it is a more "intrusive" feature than simply tagging an entry (because it send the updates to your email or inbox) this could annoy or upset people.

Poll #9003 the ability to select multiple tags when tracking users and communities
Open to: Registered Users, detailed results viewable to: All, participants: 62


This suggestion:

View Answers

Should be implemented as-is.
36 (58.1%)

Should be implemented with changes. (please comment)
2 (3.2%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
23 (37.1%)

(Other: please comment)
1 (1.6%)

aidadesigns: Ginger tabby painted in watercolor, head closeup (Default)
[personal profile] aidadesigns

Title:
Adding option to move tags before entry text

Area:
tags

Summary:
Adding an option under Customization > Additional options that enables a user to place tags before entries instead of having them appear after entries, as is currently the case.

Description:
There's already an option under Customization > Additional options that enables a user to move metadata before entry text, and I believe having the same option for tags would be useful in many cases.

For example, people could tag their posts discussing sensitive issues with general or trigger specific warning tags, making those warnings easy to spot at the top of the post. Readers could then decide to continue reading that post, search for all posts containing those warnings, or skip the post entirely. (Fan)writers could tag their fiction as original or fan fiction, then tagging it further according to fandom, pairing, genre, etc., making it easy to see and search according to the reader's preferences. The same could apply to (fan)artists and the various arts they post on Dreamwidth.

I don't foresee any problems and drawbacks to this suggestion, and I don't have any knowledge of S2 or other languages to be able to suggest any other ways to accomplish this move.

Thank you in advance.

Poll #8898 Adding option to move tags before entry text
Open to: Registered Users, detailed results viewable to: All, participants: 75


This suggestion:

View Answers

Should be implemented as-is.
45 (60.0%)

Should be implemented with changes. (please comment)
6 (8.0%)

Shouldn't be implemented.
3 (4.0%)

(I have no opinion)
20 (26.7%)

(Other: please comment)
1 (1.3%)

ciaan: revolution (Default)
[personal profile] ciaan

Title:
List memory tag on jump page after adding a memory

Area:
memories

Summary:
After I add something to my memories, I frequently want to go look at all the things I have memoried under the tag I just used. It would be helpful if that link were on the jump page.

Description:
After adding a post to your memories you are taken to a page with the following options:
Go back to the entry
View all your memorable entries
Go to your Reading Page
Continue reading [the journal you just memoried a post from]

Frequently what I want to do next is go to the section of my memories that uses the tag I just added the entry under, and I would like to be able to do that directly instead of having to click to all memories, scroll down to that tag in the list, and then click it again. One of the most common things I do with my memories is add posts to them that I might want to include in a newsletter I work for, and that's especially when this would come in handy for me. Also, honestly, having the same option to go back to the specific memories section after deleting an entry from my memories would be useful for me, too. Then when I was deleting things I had already added to the newsletter or had decided not to use I wouldn't necessarily have to open all of them in separate tabs. But that is less of a hardship.

Poll #8849 List memory tag on jump page after adding a memory
Open to: Registered Users, detailed results viewable to: All, participants: 53


This suggestion:

View Answers

Should be implemented as-is.
30 (56.6%)

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

Shouldn't be implemented.
1 (1.9%)

(I have no opinion)
22 (41.5%)

(Other: please comment)
0 (0.0%)

msilverstar: (Default)
[personal profile] msilverstar

Title:
Request Tag function for modded communities

Area:
tags, communities

Summary:
Would be good to show whether the community allows member-generated tags, and if not, allow them to request new tags from the mods.

Description:
I just posted to a community and there was no tag for what I wanted. I typed it in (Beta Post interface) but when I posted, there was a message that only mods can create tags. That's better than blocking the post, but I had to edit the post and write a note to the mods, and there should be a smoother interaction.

1) let the poster know whether they can freely create tags

2) if not, provide an automated way to request tags

3) identify those requests so that mods can filter them in their Inbox / mail client

4) if necessary, include anti-spam logic to avoid hundreds of requests at once (I assume you have such for community posts)

Poll #8840 Request Tag function for modded communities
Open to: Registered Users, detailed results viewable to: All, participants: 81


This suggestion:

View Answers

Should be implemented as-is.
57 (70.4%)

Should be implemented with changes. (please comment)
13 (16.0%)

Shouldn't be implemented.
3 (3.7%)

(I have no opinion)
7 (8.6%)

(Other: please comment)
1 (1.2%)

Profile

Dreamwidth Suggestions

April 2017

S M T W T F S
      1
23456 7 8
9 101112131415
16171819202122
23242526272829
30      

Style Credit

Expand Cut Tags

No cut tags

Syndicate

RSS Atom