At 2/4/02 6:56 PM, Pflege@aol.com wrote:
>This will be difficult with info/biz
>If you f.ex. use 'transfer confimation code'
>users will be confused with 'authorisation code'
>(already probably most users are confused with 'authorisation code'.
>
>I would suggest something like
>'Special transfer password' instead of another 'code'
Well, I'm not that picky about what it's changed to, as long as it's does
NOT include the word "password". Having two totally different things in
the OpenSRS system both labeled "password" is extremely confusing, and
sticking more words in front of it doesn't help.
But yes, two things labeled "code" would also be bad (although I'm not
clear on whether the biz/info tokens will actually be referred to as a
"code" -- has a consistent terminology been established for that?
Consistent terminology was one of the things I suggested was required of
Neulevel to make their scheme work).
Anyway, if we want to avoid both "password" and "code", "key" is another
word that comes to mind. "Transfer approval key".
(As an aside, I discovered separately that the word "confirmation" is a
bad word to use for anything like this. A phrase like "transfer
confirmation" can have two meanings: "this confirms that your transfer
has been completed" or "use this to confirm your transfer". I had a Web
page marked "Order Confirmation Page" that was intended to convey the
meaning "use this page to confirm your order", and found that a lot of
customers were quitting at that point without going to the final step,
because they were reading it as meaning "the order is complete; here is
your confirmation". I solved that by changing it to "Review Your Order"
and nobody ever made that mistake again.)
-- Robert L Mathews, Tiger Technologies"The trouble with doing something right the first time is that nobody appreciates how difficult it was."
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:37:03 EDT