![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
matgb) wrote in ![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png){kind=small}
dw_suggestions2009-12-05 07:56 pm
Allow an icon keyword to be assigned as primary keyword for selection, etc
Title:
Allow an icon keyword to be assigned as primary keyword for selection, etc
Area:
icons
Summary:
For icons that have multiple keywords, make it possible to have one only that appears on the drop down menu for posting and commenting.
Description:
Many of my icons have aquired more than one keyword over the years, some because they may have multiple usage contexts, others because I've given them the keyword of an old, deleted icon.
While I might like to merge the keywords together, in some cases I would like to keep both keywords extant, in order that I may change icons again in the future.
Example: I have an icon tagged both ORLY and YARLY. At one point, I had a different owl for both, but currently I have Daleks and Cybermen conversing--I may in the future want to split them up, but currently both keywords appear in every drop down menu, cluttering up my already long dropdown (and, presumably, mildly increasing server load, etc each time).
If the first listed keyword for each icon was allowed as an option to be the primary keyword, others could be retained but my selection menues would be a lot easier to navigate and less annoying.
If this isn't possible, a way of listing old keywords that have been renamed would be useful, as they can still then be resurrected.
(NB this would also help those crossposting who have more icons on one or other site, they can use the full keyword set on both sites but still have manageable selection menues)
Edit: To clarify, my suggestion is to allow people to choose, if they wish, a primary keyword, not to force all icons to only have one primary keyword, I want to supplement and improve current behaviour, not replace it.
This suggestion:
Should be implemented as-is.
9 (36.0%)
Should be implemented with changes. (please comment)
2 (8.0%)
Shouldn't be implemented.
5 (20.0%)
(I have no opinion)
8 (32.0%)
(Other: please comment)
1 (4.0%)
no subject
From what I read of Allen's code (and I'm not that good with Perl), this specifically merges keywords together and from then on you can only use the one.
I'm specifically thinking of people that have, say, 100 pics on LJ, but only have a free account here (or vice versa if LJ pics this up)--they can assign multiple keywords to a small number of icons here, but have a lot more icons on t'other site.
Then there's the good chance I'll lapse to free soon (not much work on currently)--I'd rather have all my keywords still in use, but be able to re-upload later.
Which makes me think of another suggestion to make, the UI for removing excess pics is incredibly annoying, won't even let you copy/paste keywords out of an inactive pic, let alone anything else. But that might be best linked to my other suggestion, where deleted icons get their keywords assigned.
Also, from what I read, if I decide to split up a merged keyword (like go back to having YARLY and ORLY instead of this) then Allen's code seems to block this--I'm not certain of this.
EDIT: If referring to a specific icon in a comment, use the damned icon. D'oh!
no subject
Hmm, I am not sure where you are getting that from. The source code is here: http://changelog.dreamwidth.org/479221.html and in the comments, it says:
+# the new keywords must be the same number as the old keywords; that is,
+# if the userpic has three keywords and you want to rename them, you must
+# rename them to three keywords (some can match). otherwise there would be
+# some ambiguity about which old keywords should match up with the new
+# keywords. if the number of keywords don't match, then an error is thrown
+# and no changes are made to the keywords for this userpic.
I am trying a few things now and when trying to merge keyword I get this:
Error renaming 'key2, key5, key6' to 'key2': must rename to the same number of keywords.
no subject
no subject
no subject
I think you're pretty much right that the the keyword renaming isn't necessarily going to solve the problem that you're talking about here. You want to have, say, 150 keywords for 50 icons, and like it that way, but generally when you select your icons, you just want to see 50 of those keywords. Sort of a shortened favorites list of keywords, probably with an option to display the full list if you wanted?
If you really wanted to combine your various keywords so that you only had one keyword per icon, while keeping your posts using the old keywords on the same icon, then renaming would help. But for this? Not so much.
no subject
Ooh, that's a good idea--yes, that's pretty much exactly what I'd like. Admittedly, until Mark finished the code push tonight I don't know how many keywords I want to keep, but several others deliberately have several.
I actually partially thought of this while reading through your discussion on your patch in bugzilla, but I couldn't clear in my head what I actually wanted, and it looked like you were close to a solution. But this is a different problem, and while I'm not sure how big it is, it can't just be me.
Curiosity--if I did rename ORLY and YARLY into just ORLY, would I later on be able to upload a new YARLY? If so, what would happen to really old posts that initially used that icon, display ORLY or YARLY?
no subject
Renaming does a full brute-force overwrite of the old keyword associations. So if you rename YARLY to ORLY, it would make it as if you'd never posted anything using the YARLY keyword. So you could afterwards put the YARLY keyword on a new icon, and any new posts you made with that keyword would use the new icon. But the old posts would act as if they'd always been posted with ORLY.