Divided scraper list is confusing because it's unclear why it's divided

[equivalentideas]

On the owner show page lists of running, erroring and 'other' scrapers are divided by some space (I'm now unclear if this is the case as errored scrapers aren't split out here). See the gap between the first and following scrapers here:

As a user I found this confusing, as I wondered what the difference between these scrapers was.

The gap in the list is giving the user information that there is something different about these scrapers but not what the difference is. At first glance I assumed this was scrapers owned by this user and scrapers from an organisation they're part of. But then I realised that's not the case (because I've looked at lots of these pages and that didn't make sense). Then I went and looked at the source code and understood.

The design already indicates which scrapers are running and erroring by adding an icon or label to the item. I assume the space between lists is to reinforce this, but it's not effective because it's unclear.

To make this less confusing, here's a couple of potential solutions:

• remove the gaps and let the labeling of the scraper give the information.
• add headings to the lists to make it clear what they are for.

I think headings is probably the way to go because it seems important that users see scrapers that need attention prominently.

[mlandauer]

If in doubt look in the code ;-)

[equivalentideas]

I mean to users :) I should have said as a user—amending description.

[mlandauer]

I think to make your ticket clearer it would be better to say what specifically is unclear. Why does a space make something confusing?

If you don't know how to explain it clearly then try offering a solution to explain things

On Wed, Apr 29, 2015 at 11:08 AM, Luke Bacon notifications@github.com wrote:

I mean to users :) I should have said as a user—amending description.

— Reply to this email directly or view it on GitHub https://github.com/openaustralia/morph/issues/662#issuecomment-97278001.

[equivalentideas]

Thanks @mlandauer I've had a more thorough go at explaining why it's confusing and suggested a couple of solutions.

[mlandauer]

Thanks for update. This is now super clear!