We have an image cataloging program in which we have a database holding the already cataloged images. Let's call them "The Archive".
Of course, everyone wants to keep the Archive clean, hence we need a GUI for searching duplicates in the Archive.
Besides the "Archive" users get photos/images from a myriad of sources: Internet, stock agencies, coworkers, friends, freelancers etc. etc. etc.
Hence, depending of situation, we need to check these new images (let's call them 'Candidates') if among them there are duplicates.
So, there are situations in which the users want to check their Archive for duplicates and there are situations to check their Candidates for duplicates.
But, also, there is the 3rd case in which the users want to check the Candidates against the Archive - perhaps a part from Candidates already exist in the Archive.
Behind the logical reasoning, the differentiation between Candidates and Archive is very important because:
- searching through Archive is much much faster (due of DB backend)
- by choosing how to search (eg. only between Archive and Candidates) we greatly reduce the number of comparisons. (in our example because the user accepts that Archive and Candidates are ok).
A GUI proposal is the wizard-like draft bellow: (the 3rd page are the methods of comparison - not directly related with the question)
How can we improve the above?