Various hotels I have come across (though I remember that primarily from China) had simple lamps with the respective do not disturb and please clean room signs next to the door and accordingly labeled switches on the inside of the room to activate either of the exterior lights.
It cannot be used by anyone other than the guest.
It costs somewhat more than a ...
I have seen indicators that are inserted into the key card slot so that keys can't be inserted until the indicator is removed. These solve the problem of being accidentally changed, since they are anchored to the door.
The user is almost always required to be looking directly at the tag when inserting it into the door lock, so it is unlikely to be ...
Some of the invoices are not eligible for payment. They were excluded from payment processing. [details]
Error messages should separate two things:
Information for the end user (What they can do to "fix things")
Diagnostics for support and for the developers
Of course the developer is happy because they see what they want. But it's not helpful ...
There is something called Paperless Signs like below
While a passerby can still switch the action. Here the mode of turning the light on should be only available with the guest.
I guess punching the room card/keys. Whichever sign you'll punch your card on the light will glow.
Sliders attached to the doors can do the trick. The material used will determine the options to fix them, their appearance and their longevity. This solution seems to be consistent with your two first conditions. Here are examples :
Original wordings can then check your two last conditions. For example :
on the left under half : "Everything is just fine. ...
Hashtags are mostly used as unmoderated ad-hoc discussion forums; any combination of characters led by a hash sign is a hashtag, and any hashtag, if promoted by enough individuals, can "trend" and attract more individual users to discussion using the hashtag.
The tag you are talking of in this context is a keyword/...
They receive many names depending on the script you use, there seems NOT to be a consensus on a single specific name. Just to illustrate different options, here you have the names and link to the script that generates these blocks.
Select Box and also select box
There seems to be some kind of consistent naming around ...
It's not my words but NNGroup's:
Simplicity Wins over Abundance of Choice
Adding features that have little to no value to most users undermines people’s innate abilities to collect and process information efficiently.
"Simplicity Usually Wins"
I would strongly suggest solutions like the following for this situation. A simple Hint + Button named ...
As mentioned in Smashing UX Design by Jesmond Allen and James Chudley of cxpartners, who have many years of experience with high profile retail website, they recommend using tabs in this way with caution as in usability testing they find that people don't always see the tabs.
Tabs typically differentiate unconnected groups of items. Compartmentalizing items ...
When the description has a hashtag, automatically add a corresponding number of tag buttons to the right of the row. Those will take the user to the results of the search query for "#Lunch" or "#clients" for example.
As soon as the user adds/removes the hashtag to or from the description, the tag button gets added to or removed from the right hand side.
A solution that seems to meet the requirements, but still doesn't seem great: a stiff piece of plastic with a profile like this:
Top down it looks like this:
[ Clean | Do not disturb ]
You slide it under the door, with the appropriate bit sticking out. The vertical tab in the middle stays inside the room,...
For replacements I always prefer to use double square brackets with natural language:
Hello, [[first name]]
Double brackets rarely appear in normal text but are easy to type and read, natural language removes the need to know/lookup field names.
Alternatively you can use real data with highlighting and some tool-tips, bit trickier to implement but much ...
Using search tool to find categories is not the best way:
Search terms may contain errors in typo
People tend to use different words for the same meaning
Search makes invisible all the categories, so it is guessing-like
The idea is to let create new category only after failing to get right one.
To get appropriate category you could provide:
I'm not sure there is actually name for the field itself, but what you are referring to appears to be a tag editing widget applied to the field.
A link to an implementation of it called 'Tag-it!' is here: http://aehlke.github.io/tag-it/
You could have a long U-shaped plastic tab that fits over the latch portion of the door, with one side of it labeled 'Do Not Disturb' and the other side as 'Please Clean The Room'. The occupant puts this over the door latch before closing & then locking the door.
This should meet all of your requirements:
hard to misuse - the side of the plastic ...
Although I wouldn't change a prototype based purely on the feedback from the first tester, I would definitely and fearlessly make such a change if I got a majority of the first 4-5 testers revealed a problem. ...and I would stop wasting testers on the old design until that change was complete. Here is why...
In UX, Ignorance is precious. Every user only ...
Maximize information density
Tags are great for categorizing, but tough for quick scanning. If your goal is to enable users to quickly find an exercise to sculpt a specific muscle or region, try a visual approach.
Create a standardized map of the body that is small enough to fit your UI, but large enough that users can distinguish the muscle groups. For ...
Badges are numerical indicators of how many items are associated with an element (a link) and labels are used to provide additional information about something. A tag is a word or a group of words temporarily attached to an item, a SEO tool.
See this explanation on Atlassian Design Guidelines:
Badges provide quick visual identification for numeric values ...
Yes tags can be hierarchical and there is actually a lot of (not yet widely recognised) potential in it.
Although some people (probably like the question asker) have been curious and/or after hierarchical tagging for years, the reason it is not present on the CMS market now is more because of technical obstacles rather than not seeing point in it. With pure ...
My first question is, do you have a karma/points system? As I understand it you have a community edited database. Each user has their own content, which is browsable with community editable cetegories.
You could use tags instead of categories. You could filter on tags with a certain level of fuzziness so that near duplicate and related tags are included.
The advantage of hyphenating tags allows you to define when a tag starts or ends while if you went for the option of using spaces, there will be a lot of confusion about the start and end point of a tag.
For example, If I wanted to tag San Francisco and my next tag was niners, if I entered all of it together, the system my take the tag as "San Francisco ...
Facets. Colour size and material are facets as in faceted navigation. Most shops use faceted navigation to allow customers to find the item they are looking for. Red for example is a value under the colour facet. Price and anything with a range can be turned into a facet by slicing it into chunks (for example 50-100 pounds). Or you just leave it as a range ...
They're called tags or tag buttons.
It's so inherent in so many OSs that you can just call them tags. We just had a client saying they want dismissable tags in such and such ... so you could perhaps refer to them as that more fully.
In the context of a blog:
Categories are predefined and there should not be too many of them. Their use is closer to a folder system where a blog post gets put in one or more folders. They should be visible and easily accessible because they form the secondary organizing principle for the blog (primary being chronology).
E.g. a post about the ...
In my opinion tag hierarchy is not always a bad idea, but I think hierarchy is a bad word here, I would consider this being subsets.
Let's say we are on Stack Overflow and because you work often with Microsoft Excel, you are interested in all questions regarding it. So you add as favorite the "excel" tag and ignore all the others.
But there are other tags ...
You'll notice that the Wall Street Journal provides a Search utility in addition to tags and most popular content. They are providing multiple methods for users to find content.
For dynamic content sites, the only navigation design that could possibly hope to hold up over time is a combination of search, index by date, tags and most-popular pages, which is ...
Hashtags are just tags with a form of markdown to let you know that they are a tag. In essence the hash (#) is just formatting.
If you are going go visually mark tags so that they don't look like simple text, then you don't need the hash (#), as it is redundant. It's already clear that these are tags:
Adding a hash doesn't give you any additional ...
This is a very interesting topic. Opinions of information scientists are mixed but we're now getting better view with more empirical research done in this field. Along with some papers on SIGCHI, I have also referred to a study by Alexis Wichowski and would be discussing this in more detail below:
Empirical study on governing folksonomy tags
A paper by P.J. ...
[...] my goal was to eliminate the network shared structure.
It'll help to center the goal around a clear pain point. You mentioned issues of 'g-drive' but the top two issues (length of the file path and storage space) are technical and not related to usability. From your description I think it's getting to the right information quickly that's the biggest ...