The Search interface element on the home page behaves oddly.
First, when I click the magnifying glass icon without entering anything, I get a Search results page with "DM-09: Search metadata for specific objects of interest" as the page title. (It even appears in the breadcrumbs at the top of the page.) The search results seem to contain pages that have the word "Search" in them. It looks like it's taking the default text ("Search...") from the search UI element and actually performing a search for it. I don't think this is useful. It would make more sense to either not do anything when the user hits the icon with no text in the field, or else take the user to a generic search page without actually starting a search.
When I enter search terms, the results are weird. Since this is the "Research Software Portal," I expect the search feature will allow me to search for research software, and the results will be software packages. Instead, it seems to be pages on the site, and the hits aren't especially relevant. E.g., searching for "use case" returns the "XCSR Requirements" page as the top hit? Searching for "cosmology" returns zero hits. Searching for "MPI" returns one page: "L1-3 SP Operational Components." None of these are particularly helpful results.
IMO, this site search feature should be replaced by a link to the Comprehensive Software Search. (But see also the related thread, "Life Cycle - Available Software.")
We haven't put a lot of effort into the portal wide search yet as we continue to refine the content. We'll fix the weird behavior.
If we default to Comprehensive Software Search then search results won't include use cases, technical reviews, discussion forum, news items, or other content that is searchable. Would it make more sense for the RSP wide search to search all content types? How about an initial results page that lists how many software products had a match, discussion forums, news items, etc. where the user can click again to see content type specific matching results?
Just a thought.
Further refining the above idea: make the RSP wide search return a summary page listing the number of matches across different content types (available software, community needs, delivery efforts, discussion forums, and news), where the user then clicks on a content type to view the search results for that content type.