By user-level abstraction I mean what should I call them and what kind of icon should I use to represent it in the UI? The concept of tags should be familiar to most users right now, but I'm not so sure hierarchical tags are, nor does the abstraction of tags completely fit.
通过用户级抽象我的意思是我应该将它们称为什么以及我应该使用什么样的图标来在UI中表示它?大多数用户现在应该熟悉标签的概念,但我不太确定分层标签,标签的抽象也不完全适合。
What I have is actually something between folders and tags, in that each subtag is a proper subset of its parents. To get the contents of a folder-tag-thing you take its contents plus the contents of its sub-folder-tag-things and do that recursively. In a way they're like (and here's where I just partially answered my own question in the process of asking it) categories. What do you guys think of calling them categories? What kind of icon would you give it, since a category is an abstract concept rather than a physical object that can take a shape?
我所拥有的实际上是文件夹和标签之间的东西,因为每个子标签都是其父项的适当子集。要获取文件夹标记内容,您可以获取其内容以及其子文件夹标记内容,并以递归方式执行此操作。在某种程度上,他们就像(在这里,我只是在提出问题的过程中部分回答了我自己的问题)类别。你们怎么看待他们的类别?你会给它一个什么样的图标,因为一个类别是一个抽象概念而不是一个可以塑造形状的物理对象?
(Can wiki if requested)
(如果要求可以维基)
Edit: For clarification, what I'm looking for is an abstraction for an end-user like Aunt Sally that easily grasp the concept. Ideally there is also a graphical representation (an icon) that can be easily associated with that concept.
编辑:为了澄清,我正在寻找的是像萨莉阿姨这样的最终用户的抽象,可以轻松掌握这个概念。理想情况下,还有一个图形表示(图标),可以很容易地与该概念相关联。
Edit2: One thing I did forget to mention is that an item can exist in more than on category (much like how Google Doc allows you to add an document to multiple folders). I guess I've kind sold myself on calling them categories. It just fits everything you can do with them. Something can belong to a more than one category, subcategories make sense, most subcategories people normally create lend themselves to an is-a relationship (for example, a Windows user might have say a folder called resumes in their My Documents folder, because a resume is a document, it would make sense that it's in My Documents as well if you think of the folders as categories)
Edit2:我忘了提到的一件事是,一个项目可以存在于多个类别中(就像Google Doc允许您将文档添加到多个文件夹一样)。我想我已经把自己称为类别了。它只适合你可以用它们做的一切。某些东西可以属于多个类别,子类别是有意义的,人们通常创建的大多数子类别都适用于is-a关系(例如,Windows用户可能会在其“我的文档”文件夹中说一个名为“简历”的文件夹,因为简历是一个文档,如果您将文件夹视为类别,那么它在我的文档中也是有意义的)
What I still haven't figured out is the icon (I'm 99% sure I'm going to be using some kind of TreeView to display them in) I could just use a folder icon I suppose, maybe a custom folder-like icon unless anyone else has a better idea. Google calls them folders, so I guess it can't be too bad right?
我还没想到的是图标(我99%肯定我将使用某种TreeView来显示它们)我可以使用我想的文件夹图标,也许是自定义文件夹图标,除非其他人有更好的主意。谷歌称他们为文件夹,所以我猜它不会太糟糕吧?
To clarify further, my target audience will be people technical enough to know how to download and install the app, but that's about it.
为了进一步澄清,我的目标受众将是技术人员,知道如何下载和安装应用程序,但这就是它。
5 个解决方案
#1
If your target audience is technical then TreeViews and/or Folders are common ways of abstracting hierarchical data. They're all variants of the Composite pattern.
如果您的目标受众是技术人员,则TreeViews和/或文件夹是抽象层次数据的常用方法。它们都是Composite模式的所有变体。
In the post-google era though, I've tended to consider hierarchical categorization less important than a flat tag/label space combined with a very fast search. IMHO if the size of the dataset is large (e.g., > 1000 documents/elements) then the overhead of hierarchical categorization overwhelms the nominal benefit of having documents placed into nice neat categories.
然而,在后谷歌时代,我倾向于认为分层分类不如平面标签/标签空间与非常快速的搜索相结合。恕我直言,如果数据集的大小很大(例如,> 1000个文档/元素),则分层分类的开销超过了将文档置于漂亮的整齐类别中的名义好处。
If your target audience is non-technical then it's been my experience that non-technical users do not get hierarchies and won't take the time to to figure out more than a single level of categorization.
如果您的目标受众是非技术性的,那么根据我的经验,非技术用户不会获得层次结构,也不会花时间来计算出超过一个级别的分类。
#2
For me, the answer comes from the Opera Desktop Team blog (as well as Dotclear’s blog, which used the same convention and thanks to whom I discovered it too):
对我来说,答案来自Opera桌面团队博客(以及Dotclear的博客,该博客使用相同的约定,也感谢我发现它的人):
tag:subtag - CSS:font
tag:subtag - CSS:font
When you click on the CSS:font, you know it is part of a larger CSS tag. The tag page should have a text indicating that a parent tag is available (or you can find it by yourself, much on Wikipedia with direct URL manipulation).
当您单击CSS:字体时,您知道它是更大的CSS标记的一部分。标签页应该有一个文本,表明父标签是可用的(或者你可以自己找到它,很多都是在*上通过直接URL操作)。
I have a discussion running on WordPress.
我在WordPress上进行了讨论。
#3
You could use "bundles" (as del.ico.us does). I am not sure if more than one level is meaningful for tags though.
您可以使用“bundles”(如del.ico.us所做)。我不确定是否有多个级别对标签有意义。
#4
How about a tag "detail"? Since a subtag is a proper subset, it can be thought of as applying detail to a tag...
标签“细节”怎么样?由于子标签是适当的子集,因此可以将其视为将标签应用于标签...
#5
It sounds like an outline to me.
这听起来像是我的大纲。
There's the Outline Markup Language (OML).
有大纲标记语言(OML)。
#1
If your target audience is technical then TreeViews and/or Folders are common ways of abstracting hierarchical data. They're all variants of the Composite pattern.
如果您的目标受众是技术人员,则TreeViews和/或文件夹是抽象层次数据的常用方法。它们都是Composite模式的所有变体。
In the post-google era though, I've tended to consider hierarchical categorization less important than a flat tag/label space combined with a very fast search. IMHO if the size of the dataset is large (e.g., > 1000 documents/elements) then the overhead of hierarchical categorization overwhelms the nominal benefit of having documents placed into nice neat categories.
然而,在后谷歌时代,我倾向于认为分层分类不如平面标签/标签空间与非常快速的搜索相结合。恕我直言,如果数据集的大小很大(例如,> 1000个文档/元素),则分层分类的开销超过了将文档置于漂亮的整齐类别中的名义好处。
If your target audience is non-technical then it's been my experience that non-technical users do not get hierarchies and won't take the time to to figure out more than a single level of categorization.
如果您的目标受众是非技术性的,那么根据我的经验,非技术用户不会获得层次结构,也不会花时间来计算出超过一个级别的分类。
#2
For me, the answer comes from the Opera Desktop Team blog (as well as Dotclear’s blog, which used the same convention and thanks to whom I discovered it too):
对我来说,答案来自Opera桌面团队博客(以及Dotclear的博客,该博客使用相同的约定,也感谢我发现它的人):
tag:subtag - CSS:font
tag:subtag - CSS:font
When you click on the CSS:font, you know it is part of a larger CSS tag. The tag page should have a text indicating that a parent tag is available (or you can find it by yourself, much on Wikipedia with direct URL manipulation).
当您单击CSS:字体时,您知道它是更大的CSS标记的一部分。标签页应该有一个文本,表明父标签是可用的(或者你可以自己找到它,很多都是在*上通过直接URL操作)。
I have a discussion running on WordPress.
我在WordPress上进行了讨论。
#3
You could use "bundles" (as del.ico.us does). I am not sure if more than one level is meaningful for tags though.
您可以使用“bundles”(如del.ico.us所做)。我不确定是否有多个级别对标签有意义。
#4
How about a tag "detail"? Since a subtag is a proper subset, it can be thought of as applying detail to a tag...
标签“细节”怎么样?由于子标签是适当的子集,因此可以将其视为将标签应用于标签...
#5
It sounds like an outline to me.
这听起来像是我的大纲。
There's the Outline Markup Language (OML).
有大纲标记语言(OML)。