Advanced search: list of fields needs to be repositioned on the page

[sandaionescu]

Visually, the list of fields does not connect well with the search boxes. Perhaps some slight redesign and/or brief instructions - "select a field here:" The way it sits right now, the list of fields can be easily overlooked.

[CSimmer]

Hi Sanda,
Are you talking about moving the Field Type block, on the https://demo.ncrn.cornell.edu/ced2ar-web/advanced_search page? (See screenshot)

If so, I think moving to the left of the "Any Field" block would be an excellent idea.

[sandaionescu]

Hi,
Yes that's the block that I'm suggesting be moved. Perhaps on top of the type-in boxes, you could do a drop-down list under the title: Choose a field, and have the fields listed.
But that is more of cosmetic improvement.
"Codebook instructions" is NOT a field that should be listed here - it is not part of the variable description. Unless you mean "Coder instructions" (see issue 23)
Also, very importantly, the question text should be searched and listed among the searched fields.

[CSimmer]

re: initial comment
I looked at the functionality of the Advanced Search page. The page is designed so that any number of field types can be use in a single search. (See screenshot below.)

The Field Type blocks are coded as a set of navigation tabs. There is a comment in the code about "Right tabs fair better for mobile first design". Placing the tabs at the top would not be good because of the number and length of some tab names.

The recommended solution would be to add some instructions in the wiki User Guide. I did not see a screenshot of the Advanced Search page in the User Guide.

Reminder: Add the variable field descriptions listed on the API Guide page to these new instructions.

[CSimmer]

re: "Codebook instructions"
Please see issue Advanced search: Codebook instructions? #23

re: question text
Please see other issues where question text is the main issue.

[sandaionescu]

I see from your example that multiple fields may be selected. Yet I think that is not apparent on the page, in addition to the actual fields being easily overlooked. This is from a simple, outside user perspective. In my experience you cannot expect anybody to actually read instructions. People just don't do it. What they can do has to be intuited from the page layout/design. That's why I made the comment. The options simply did not jump at me.

[CSimmer]

Will see what minor UI changes can be made to the page as I work other Advanced Search issues like #23.

(No major changes are allowed since v3 is under development.)