So, the collection of organisations in that view is not presented.  In order to go that route, it would mean modifying the OrganisationsIndexPresenter to return the scopes it implements wrapped in another instance of itself.  While not necessarily a terrible thing to do, that did feel like an overkill.

I think this is all coming back to that fairly subjective debate as to how much logic is permissible in a rails view.  To make the point, would you have objected to this if it was written like this?:

```
<%
  num_live = organisations.count(&:live?)
  num_exempt = organisations.count(&:exempt?)
%>
...
```
In the end, that's doing exactly the same thing except it's doing it in a slightly less efficient although prettier way.

So if I was going to factor this out, I would factor it out into something closer to the model layer, as it isn't really the kind of logic which belongs in a helper.  I would want a collection of organisations to be able to tell me how many of that collection are exempt, etc..  In truth, the collection already can do that, but it relies on a sql query to do so, so I didn't want to do that.

Anyway, rambling aside, my question is whether doing a count of objects in a view should be considered as inappropriate.