v2: search results

[josh-chamberlain]

part of #248

see wireframe

Front end

• replaces existing data source search results (example)
• users can see currently open requests related to the search criteria
• users can click a source to navigate to the details page
• users can submit a new source
• users can submit a new request
• logged-in users can see a button to view recent searches
• logged-in users can click a "Follow search" button to be notified about new sources and requests in the search
• results are grouped by geographic area (in the wireframe as of 8/21), and the groups are collapsible (not in the wireframe)

  • 409 goes into more detail

• not in wireframe: give people the ability to sort search results by date added (default to most recent)
• top level properties to show for each result row
  • name
  • time range covered
  • agency
  • formats available
  • date added
  • description? (truncate, option to show more)

API

• [ ] #256

Cut from this issue

• 14

  We can still show people their search terms in a simpler way, without showing all the options + scaffolds.

• 21 only becomes useful if people can make custom searches

[mbodeantor]

@josh-chamberlain Do users that save a search automatically "follow" it for new results or do we want separate functionality for that?

[josh-chamberlain]

@mbodeantor I adjusted the issue—follow and save are separate.

[josh-chamberlain]

consider: adding a non-intrusive "Did you find what you were looking for?" prompt with yes and no options. If "no", you could introduce the form to make a request, with the geography pre-filled from the search. there's a comments field on that form.

If yes, allow them to add more about their research question but even if they don't submit that, record a generic "search for xyz successful" data request with "completed" status. maybe allow people to comment or just thank them for letting us know?