What filters for tools listing?

[philipbaileynar]

We are about to embark on developing a new home page for tools.riverscapes.net. This will fulfill our vision of a FILTERABLE list of tool cards per our discussions with the information architect...

Questions

1. What filters do we want above the list of cards. I strongly recommend not more than 4 filters. Here is the wire frame of the existing design that we will follow if there are no other concerns.
2. What type of filter controls:
   • Multi-select checkboxes to the left (as shown in mock-up)
   • Multi-select dropdowns as horizontal ribbon across the top.
   • Single select dropdowns as horizontal ribbon across the top.

@joewheaton ????

[joewheaton]

Sorry @philipbaileynar. Here you go. I know you are out, but @MattReimer might be able to work with some of this.

Well, based on this, I would include for filtering & SORTING purposes

• Resolution (multiple possible)
  • Any
  • Cell
  • Reach
  • Point
  • Catchment
• Extent (multiple possible)
  • Any
  • Reach
  • Catchment
  • Network
  • Regional
  • National
  • Continental
  • Global
• Interface (multiple possible)
  • API
  • Web App
  • QGIS Plugin
  • ArcPro AddIn
  • ArcMap AddIn
  • ArcPy
  • ArcMap Toolbox
  • ArcPro Toolbox
  • Standalone Mac
  • Standalone PC
  • CLI
  • iOS App
  • Andorid App
• Status
• Pending Riverscapes Compliance
• Riverscape Compliant

Other Attributes I want in table

These are for Sort by (not filter by)

• Tool Grade (with link to report card where it exists)
  • Proof of Concept
  • Research Grade
  • Operational Grade
  • Professional Grade
  • Production Grade
  • Commercial Grade
• Language (w/ link to GitHub repo)
• Tool Group
  • Exploratory Tools for Visualizing Riverscapes Projects
  • Legacy CHaMP Tools
  • Reach Scale Tools
  • Network Scale Tools

Also, we will have this table appear at least twice on the tools page:

• Once for Riverscapes Compliant Tools
• Once for Tools Pending Riverscapes Compliance

[philipbaileynar]

Thanks @joewheaton

Comments:

1. We intend to make the default view "cards" rather than a table. Cards behave better on different screen sizes (i.e. they are more responsive). Tables should be reserved for "data". Not saying we can't get there, but the default should be cards (much like a lot of HiveBrite views).
2. We will skip the icons. They are hard to read and don't add much (per several readers I have spoken to). Each card can have a title graphic and we can bake things like the ESRI and Q logos into those. I came up with the "gas tank" graphic idea and don't think it works. Too small for the detail required.

Question

1. Can the two uses you list above be accomplished by simply an initial filter on "compliance status"?

[philipbaileynar]

Thanks @joewheaton