Re: terminology help
I'm struggling to explain a ...
parent/child structure of objects. Users can create a relationship between
two objects; the one they start with is automatically the parent. After the
relationship has been added, it is displayed in a list, exactly the same way
on both objects. The only difference is when you open it to edit--then you
can see which is the parent and which is the child. It is possible to have
the same type of relationship twice between objects A and B-- where
A=parent, B=child and where A=child, B=parent. It looks like the same thing
is listed twice.
I am generally encouraged to provide usability feedback. I have already
commented that the words Parent Object and Child Object are too technical...
A little more background: this is a custom inhouse app that's already in
use, with barebones help that doesn't even mention relationships. I'm
writing new, in-depth help. Any suggestion for an interface change needs to
show a benefit in reduced data errors.
Anybody have any ideas of better words than parent and child?
Check out the new release of RoboDemo, our easy-to-use tutorial software.
Plus, buy RoboHelp Office in August and save $100 with our mail-in rebate.
Get details and download free trial versions at http://www.ehelp.com/techwr-l
TECHWR-L is supported by ads and sponsorships...and donations.
You can help maintain the TECHWR-L community with donations
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit
http://www.raycomm.com/techwhirl/ for more resources and info.
terminology help: From: Rosemary J Horner
Visit TechWhirl's Other Sites