Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

I am asking users to handle entities (here a subject) with multiple attributes. The first attribute shown here is a numeric value. The second is multi-valued text.

desired experience: 1.5
desired qualification: BE-CS, BE-EC

The values are used for hard comparisons such as "Find all professors who have 'BE-CS' or 'BE-EC' as qualification".


What is the appropriate term for calling 'multi-valued text' for an attribute? I will be using it like:

  • create a new 'multi-valued text' attribute
  • search for some values in this 'multi-valued text' attribute

and such.


And no 'tag': it's never (AFAIK!) used for a context other than attaching a 'soft' associated concept to the entity itself; never to an attribute of the entity.


FYI: I am contemplating the term 'attribute' in the UI, but do correct me if it's not helpful.

share|improve this question
    
"code", as in experience codes? –  Erics Jan 7 '12 at 10:03
2  
"desired qualification(s)" instead of "desired qualification" comes to mind. –  Marjan Venema Jan 7 '12 at 11:19
    
Will users only be adding qualifications as in your example, or is it just an example and will users be adding any kind of generic value to a pre-existing key? –  Rahul Jan 9 '12 at 11:42

3 Answers 3

I'd call them 'Qualifications'. Users won't be interested in how computers work.

share|improve this answer
    
I think @aitchnyu is looking for a common term for both qualification and experience and other "entities". –  JOG Jan 9 '12 at 14:17

You might as well post this over at english.

I would want to see a list with more attributes than the two you mention, to sort out what they actually are. But Attribute, Field, Prerequisite, or Entity all sound good to me.

EDIT: As @naoise reacts, of course these terms are not friendly to normal users. Creating content, forcing them into the abstract metas of their own data, is for super users. So name it what it is. You wont gain UX by naming complex elements to "Thingie". ;)

share|improve this answer
    
I don't agree. Attribute, field and entity aren't too user-friendly, and pre-requisite is broad. –  Naoise Golden Jan 9 '12 at 11:33
    
I agree, it's not. –  JOG Jan 9 '12 at 13:39

Don't. Tell users what they need to do, not how you are internally processing their data. So you might present the entry fields as

Desired Qualifications
___________
___________
___________
[+Add More]
share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.