guaq/sikteeri — comment on commit 09473c8538af97401f1b18724816fa09d0220f49
File:  line 0
By joneskoo:

> Should be refactored into list_duplicates or get_duplicates, or even find_duplicates. Which one is preferred? find_duplicates could take parameters. What params would be needed?

I think where this is needed most is when the board is reviewing the
application. So at that point we have the new membership (application)
and we need to list potential duplicates for the reviewer's aid.

We need to find a list of duplicates for that application. Thinking
about the user experience, should we list the reason why we suspect
this is a duplicate? What format we need for the listing? It certainly
affects the implementation strongly. The reviewing should be quick so
the information needs to be short and relevant.

I guess there's no way to avoid going back to the actual users'
wishes. Ideally I think we should get a listing of what to show and
where.

1. Initial requirements
2. Mockup
3. Implementation