Change By: johnwoodlock (12/Sep/12 5:23 AM)
Description: Some design decision needed first.

When looking at individual lending apps at GK, Enda and Al Majmoua it seems that a typical client search would be by
 Identifying  "Identity  Type "  (passport  no , gov id) and then the Id itself.

Does this seem right to you Vishwas?  If
 not, we won't do it.

If
 so how would we implement it on the database?   Would we just add fields to m_client for passport, government_id etc. (because there would be limited list of them) or would be build a separate m_client_identity table where any type of identity could be added and subsequently searched?

We would put the "Identity Type" code on m_code and its allowed values on m_code_value (the maintenance screen for this has not been done yet but you shouldn't need it and can just add the data manually and we'd add the populating script to our base data files).
still writing

I'm happy for now to just add more searches to our current demo search UI so people just choose what's good for them (apart from the original dropdown list which we'll take out later on) but I guess there might be a need for a person to indicate which search they want.  We can wait till an actual MFI becomes opinionated about it before implementing any customisations/configurations though.

So
 this  one To Be finished  task has 3 bits
1) deciding whether you thinkIdentity Type / Id search is useful search to prioritise
and if so
2) then deciding on the db design
3) adding to client search UI
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

Reply via email to