|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ Mifos-issues mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mifos-issues
John,
What you have outlined sounds good to me
Considering that we would want to add different types of Identifiers for the client (Driving licence, passport, ration card, government Id or SSN etc based on the country) I would lean towards the second approach you have suggested.
i.e
1) Keep the client table 'clean' probably we only need to add system Id and mobile phone number to it as search parameters (searching by mobile phone number seems to be quite a valid use case to me. Do you think it is relevant?)
2) Add a separate table say 'm_client_identifier' to the database where all added client Identifier details are stored
This table could contain the following columns to begin with
a) Foreign keys to m_client and m_code_value (for type of identifier)
b) Column "document_id" = unique identifier for the client document
c) Column "description" = an optional description or note
d) Column "document_key" = an optional location of soft-copy of the document
So in the UI, in the section for adding loan application and note, there would be another section for adding client Identifiers using which we can add details of different client identifiers
Back to the search screen, we can continue having the search box which does a default search based on name
with a small link for search criteria next to it. In this search criteria, we would have a checkbox list (which shows phone number and other identiers) allowing the user to include any additional paramters he wants for the search.
Finally, I am not sure if I have a strong opinion on "whether you thinkIdentity Type / Id search is useful search to prioritise" - I spoke to a customer and they did want the core functionality (i.e on adding a new customer they wanted to find out if any of the documents he had provided were already in the system.Basically, an alert if a ration card with same ID is already associated with another customer etc)
However, in normal day to day activities, they do not really try to search for a customer based on his voter Id etc