[Koha-bugs] [Bug 13142] Change "mobile phone" label back to "other phone"

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13142

David Cook <dcook at prosentient.com.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dcook at prosentient.com.au

--- Comment #5 from David Cook <dcook at prosentient.com.au> ---
This is a good point. It always drives me nuts when I'm filling out forms that
say "Primary, Secondary, Mobile", as my mobile is always my primary number.

"Primary, Secondary, Other" probably makes the most sense.

*consults phone*

In my phone's contact list, I insert a number and then I can choose a label for
that number. I can even have two mobile numbers if I want.

Admittedly, in that case, I get to decide myself what number matters most. I'm
not sending out automated phone notifications or anything like that.

Honestly, if the database were more normalized, we'd have a
borrower_phone_number table with columns something like:
"phone_number_id","borrowernumber" (FK), "phone_number", "type".

Maybe even have another column for "primary" or "priority" (so you can choose
primary, secondary, whatever).

You could do the same thing for "borrower_email": "email_id","borrowernumber"
(FK), "email_address", "type", "priority" (or probably a better label than
priority).

If we wanted to make it even more flexible, we could just have "email" and
"phone_number" tables and have columns to determine whether it's for a library
or a patron (or maybe some other organization/group/listserv).

Koha isn't a very normalized database which causes a fair amount of pain
sometimes (that said, highly normalized databases can also be painful).

Of course, if we did that, we'd need to change everywhere that we
add/edit/view/send to email addresses and phone numbers, and who has that kind
of time.

--- 
tldr;

In any case, I agree with what I think Owen is saying. The label doesn't really
matter. It's the importance (i.e. whether or not it's primary) that matters. 

Locally, we often change the label using jQuery anyway, but the important one
is always the first one during data entry (at least with newer clients... older
clients will be tied a bit more to the email vs emailpro model which is a bit
tedious).

-- 
You are receiving this mail because:
You are watching all bug changes.