I'm creating a social site for teachers (non-programmers) on which teachers can add events, links, exercises, tips, lesson plans, books, etc.
我正在为教师(非程序员)创建一个社交网站,教师可以在其上添加活动,链接,练习,提示,课程计划,书籍等。
Each of these items I want them to be able to add tags to as we do at *.
我希望它们中的每一项都能够像在*中一样添加标签。
However, because they are non-programming users, I thought that space-separated, nonspace tags and camelCase tags would lead to too much confusion, e.g.:
但是,因为它们是非编程用户,我认为空格分隔的非空间标签和camelCase标签会导致太多的混淆,例如:
grammar teachingtips universityOfMinnesota phrasalverbs
and indeed on this similar * question most of the answers suggested commas like this:
确实在这个类似的*问题上,大多数答案建议使用这样的逗号:
grammar, teaching tips, university of minnesota, phrasal verbs
but then I just signed up for a delicious.com account (which I don't think has a very programmer-centric audience) and saw that they use spaces as well:
但后来我刚刚注册了一个Delicious.com帐户(我不认为有一个非常以程序员为中心的观众)并看到他们也使用空格:
separate tags with spaces: e.g. hotels bargains newyork (not new york)
What has been your experience on this point in terms of the current UX trend for tags? Is the average Internet user accostumed to space-separated tags by now? I have to admit, I have never seen comma-separated tags on any major site I have used. Have you come upon a good way to combine them so it doesn't even matter, e.g.:
就标签的当前用户体验趋势而言,您在此方面的经验是什么?现在,普通的互联网用户是否被认为是以空格分隔的标签?我不得不承认,我从未在我使用的任何主要网站上看过以逗号分隔的标签。你有没有找到一个很好的方法来组合它们,所以它甚至不重要,例如:
grammar book reviews teaching tips
and e.g. have a quick algorithm which checks the number of current tags for:
例如有一个快速算法,检查当前标签的数量:
grammar
grammar book
grammar book reviews
book
book reviews
book reviews teaching
...
10 个解决方案
#1
I'd go comma separated personally. You'll note that * doesn't but the tags are clearly delineated into their own boxes. Plus hyphens are often used for "spacing". I'd say spaces are more natural to non-programmers than hyphens are however.
我个人用逗号分开了。你会注意到*没有,但标签清楚地描绘成他们自己的盒子。加上连字符通常用于“间距”。我会说非空间对于非程序员来说比连字符更自然。
#2
Comma separated seems the most natural - it's what English uses to punctuate lists. It also allows you to have spaces in tags if you want. People will try to enter
逗号分隔似乎是最自然的 - 这是英语用于标点列表的内容。如果需要,它还允许您在标签中包含空格。人们会尝试进入
this, that, the other
and expect it to work.
期待它的运作。
I can't think of a good reason to use spaces.
我想不出使用空格的好理由。
#3
Notice that delicious has to give an example to demonstrate how to do it their way. That's not a good sign.
请注意,美味必须举例说明如何按照自己的方式去做。这不是一个好兆头。
If you do go with commas, take care to see how easy it is for a "space user" to see that they made a mistake, and to fix it.
如果你选择逗号,请注意看看“太空用户”看到他们犯了错误并修复它是多么容易。
#4
I would go with comma separated tags, if only to save your users the pain of having to use quotes to indicate a tag has a space in it, ie website "stack overflow" tips, or website, stack overflow, tips. I know which I'd prefer.
我会用逗号分隔标签,如果只是为了保存你的用户必须使用引号来表明标签中有空格,即网站“堆栈溢出”提示,或网站,堆栈溢出,提示。我知道我更喜欢哪个。
#5
Comma-separated is the way to go for your educational audience. It's simply intuitive.
逗号分隔是您的教育受众的方式。它非常直观。
Most teachers should have no trouble understanding a system where tags are comma separated, and there is no need to come up with an awkward workaround for phrases.
大多数教师应该毫不费力地理解标记以逗号分隔的系统,并且不需要为短语提出尴尬的解决方法。
#6
It depends a little on how the tags are entered. If the user gets suggestions for tags as they type like SO provides (shades of intellisense), space separated is probably fine. However, if you are going to force the user to enter each tag without a reference list it may be easier to accept case-insensitive comma (or semicolon) delimited tags.
这取决于标签的输入方式。如果用户获得像SO提供的那样的标签建议(intellisense的阴影),则空格分离可能很好。但是,如果您要强制用户输入没有引用列表的每个标记,则可能更容易接受不区分大小写的逗号(或分号)分隔标记。
#7
You don't want to check all those possibilities unless you are going to severely limit the number of possible tags - that's an O(n!) algorithm, and you most likely don't want to have that extra load on your server.
Your best bet is probably just to stick with one option - the users will (should!) get used to it fairly quickly. Spaces as separators are probably the most common, so I would go with that, since it is the one the users are most likely to have had prior exposure to.
你不想检查所有这些可能性,除非你要严格限制可能的标签数量 - 这是一个O(n!)算法,你很可能不希望在你的服务器上有额外的负载。你最好的选择可能只是坚持一个选项 - 用户将(应该!)相当快地适应它。作为分隔符的空格可能是最常见的,所以我会选择它,因为它是用户最有可能事先接触的那个。
#8
As long as what the software accepts/demands is clear, I think users will be happy with either. Confusion comes when they don't know whether to use commas, semicolons, spaces or...
只要软件接受/要求的内容很明确,我认为用户会很满意。当他们不知道是否使用逗号,分号,空格或......时会出现混乱。
If you use a number of e-mail clients you'll know how useful a simple tool-tip reminder of whether it's commas or spaces would be when entering multiple recipients.
如果您使用多个电子邮件客户端,您将会知道一个简单的工具提示提示,当输入多个收件人时,它是逗号还是空格。
#9
When tagging, how you set it up depends on what kinds of things you will tag. Media that is hard to index, like pictures, audio, or video, should encourage many and varied tags, because the tags are how you will search the content.
标记时,如何设置它取决于您要标记的内容类型。难以索引的媒体(如图片,音频或视频)应该鼓励使用多种不同的标签,因为标签是您搜索内容的方式。
Easily indexed content (text!) should use a very rigid tagging structure, because you don't need to rely on tags for search indexing. Instead, the purpose of tags is sort the content into well-defined categories. Tags should be more like labels or folders.
容易索引的内容(文本!)应该使用非常严格的标记结构,因为您不需要依赖标记进行搜索索引。相反,标签的目的是将内容分类为明确定义的类别。标签应该更像标签或文件夹。
I'm gonna take a guess here that this content will be mostly text-based, with the occasional picture or video file thrown in. So you don't want either comma or space separated tag entry, but rather some mechanism that forces users to pick from an existing set of tags.
我将在这里猜测,这个内容将主要基于文本,偶尔会出现图片或视频文件。所以你不想要逗号或空格分隔的标签条目,而是强制用户使用的一些机制从现有的一组标签中挑选。
#10
I would assume space separated tags unless there are one or more commas, in which case you should split on commas instead. In other words, support both but in a limited way. You can probably guess right 90+ percent of the time.
除非有一个或多个逗号,否则我会假设空格分隔的标签,在这种情况下,您应该用逗号分隔。换句话说,以有限的方式支持两者。你可以猜测90%以上的时间。
#1
I'd go comma separated personally. You'll note that * doesn't but the tags are clearly delineated into their own boxes. Plus hyphens are often used for "spacing". I'd say spaces are more natural to non-programmers than hyphens are however.
我个人用逗号分开了。你会注意到*没有,但标签清楚地描绘成他们自己的盒子。加上连字符通常用于“间距”。我会说非空间对于非程序员来说比连字符更自然。
#2
Comma separated seems the most natural - it's what English uses to punctuate lists. It also allows you to have spaces in tags if you want. People will try to enter
逗号分隔似乎是最自然的 - 这是英语用于标点列表的内容。如果需要,它还允许您在标签中包含空格。人们会尝试进入
this, that, the other
and expect it to work.
期待它的运作。
I can't think of a good reason to use spaces.
我想不出使用空格的好理由。
#3
Notice that delicious has to give an example to demonstrate how to do it their way. That's not a good sign.
请注意,美味必须举例说明如何按照自己的方式去做。这不是一个好兆头。
If you do go with commas, take care to see how easy it is for a "space user" to see that they made a mistake, and to fix it.
如果你选择逗号,请注意看看“太空用户”看到他们犯了错误并修复它是多么容易。
#4
I would go with comma separated tags, if only to save your users the pain of having to use quotes to indicate a tag has a space in it, ie website "stack overflow" tips, or website, stack overflow, tips. I know which I'd prefer.
我会用逗号分隔标签,如果只是为了保存你的用户必须使用引号来表明标签中有空格,即网站“堆栈溢出”提示,或网站,堆栈溢出,提示。我知道我更喜欢哪个。
#5
Comma-separated is the way to go for your educational audience. It's simply intuitive.
逗号分隔是您的教育受众的方式。它非常直观。
Most teachers should have no trouble understanding a system where tags are comma separated, and there is no need to come up with an awkward workaround for phrases.
大多数教师应该毫不费力地理解标记以逗号分隔的系统,并且不需要为短语提出尴尬的解决方法。
#6
It depends a little on how the tags are entered. If the user gets suggestions for tags as they type like SO provides (shades of intellisense), space separated is probably fine. However, if you are going to force the user to enter each tag without a reference list it may be easier to accept case-insensitive comma (or semicolon) delimited tags.
这取决于标签的输入方式。如果用户获得像SO提供的那样的标签建议(intellisense的阴影),则空格分离可能很好。但是,如果您要强制用户输入没有引用列表的每个标记,则可能更容易接受不区分大小写的逗号(或分号)分隔标记。
#7
You don't want to check all those possibilities unless you are going to severely limit the number of possible tags - that's an O(n!) algorithm, and you most likely don't want to have that extra load on your server.
Your best bet is probably just to stick with one option - the users will (should!) get used to it fairly quickly. Spaces as separators are probably the most common, so I would go with that, since it is the one the users are most likely to have had prior exposure to.
你不想检查所有这些可能性,除非你要严格限制可能的标签数量 - 这是一个O(n!)算法,你很可能不希望在你的服务器上有额外的负载。你最好的选择可能只是坚持一个选项 - 用户将(应该!)相当快地适应它。作为分隔符的空格可能是最常见的,所以我会选择它,因为它是用户最有可能事先接触的那个。
#8
As long as what the software accepts/demands is clear, I think users will be happy with either. Confusion comes when they don't know whether to use commas, semicolons, spaces or...
只要软件接受/要求的内容很明确,我认为用户会很满意。当他们不知道是否使用逗号,分号,空格或......时会出现混乱。
If you use a number of e-mail clients you'll know how useful a simple tool-tip reminder of whether it's commas or spaces would be when entering multiple recipients.
如果您使用多个电子邮件客户端,您将会知道一个简单的工具提示提示,当输入多个收件人时,它是逗号还是空格。
#9
When tagging, how you set it up depends on what kinds of things you will tag. Media that is hard to index, like pictures, audio, or video, should encourage many and varied tags, because the tags are how you will search the content.
标记时,如何设置它取决于您要标记的内容类型。难以索引的媒体(如图片,音频或视频)应该鼓励使用多种不同的标签,因为标签是您搜索内容的方式。
Easily indexed content (text!) should use a very rigid tagging structure, because you don't need to rely on tags for search indexing. Instead, the purpose of tags is sort the content into well-defined categories. Tags should be more like labels or folders.
容易索引的内容(文本!)应该使用非常严格的标记结构,因为您不需要依赖标记进行搜索索引。相反,标签的目的是将内容分类为明确定义的类别。标签应该更像标签或文件夹。
I'm gonna take a guess here that this content will be mostly text-based, with the occasional picture or video file thrown in. So you don't want either comma or space separated tag entry, but rather some mechanism that forces users to pick from an existing set of tags.
我将在这里猜测,这个内容将主要基于文本,偶尔会出现图片或视频文件。所以你不想要逗号或空格分隔的标签条目,而是强制用户使用的一些机制从现有的一组标签中挑选。
#10
I would assume space separated tags unless there are one or more commas, in which case you should split on commas instead. In other words, support both but in a limited way. You can probably guess right 90+ percent of the time.
除非有一个或多个逗号,否则我会假设空格分隔的标签,在这种情况下,您应该用逗号分隔。换句话说,以有限的方式支持两者。你可以猜测90%以上的时间。