Open mberg opened 8 years ago
@rowo I think we can have a spinner next to the search field that allows user to specify whether it's an org/project/name search. Should we assume 'project' and 'organization' tags in the formlist?
Another form-locating problem that was mentioned is when form names or IDs are very similar. Isaac, I think this is what you are saying with the project and organization tags means. So this will involve showing more data in each form row.
The specific scenario mentioned: two projects, same form. Form ID in one = jon1, another is jon2. Wanted one person to test one and another.
Question: What is the search able to search? It should probably be able to search any of the data shown in form rows (form name, project name, form id, etc). And the website search (and row information) should work the same.
@imwongela Regarding a spinner — that could work. I'm wondering if there is anything simple in the existing ODK Collect interface that is able to handle this interaction. Dropdowns that Matt suggested are conventional, but bulky. I will do some research.
So we could combine project and org into the same dropdown and also update the metadata for each form. What was there before was an "added" date, which we can keep if it's useful in ODK Collect. Any thoughts @mberg @imwongela @koros ?
The search uses the form names to filter. When you search only forms with the string within their names appear. I think we should delay showing the project until it is implemented otherwise each form will have a blank. It should be easy to push in later. We can implement the search on any field. I think what we need is to provide for granularity so that only the relevant forms show up.
@imwongela Which project do you think we should delay showing?
I meant the text showing the project in the screenshot above. We can keep the date for the time but this does not affect the search function.
If you have access to a lot of forms then finding the right form becomes a challenge with ODK Collect. However, if you are an enumerator and have just been shared forms from a single project being able to not have to navigate to access your forms is an important selling point.
So instead of browsing from an org to a project to view folder, I propose we provide a means to filter forms by org or project. This can be done via two pulldowns in the form list view (similar to how the search table was added).
This would require adding an org and projects property in the formList endpoint for each form.