Org root page: add browse species buttons conditionally

[kasugaijin]

Currently, the browse cats and browse dogs buttons are hard coded. However, not every organization is going to have both cats and dogs. So, we should build the necessary buttons based on the unique pet species represented in the organization.

For example, if you queried the unique species on all pet records for a given org, and it returned only 'dog', then we should only show a dog button...and so on.

I was thinking about what we should do when there are no adoptable pets for a given species. For now, let's still show the button, but we should show an empty state. This related issue is adding empty states.

Regarding implementation, we will be handling this in the Organizations::HomeController. I think we should add a scope on Pet called something like organization_species that returns a list of unique species for the org. Then we can use this list to build the buttons.

[Yuji3000]

@kasugaijin I'd be happy to take this issue

[kasugaijin]

@Yuji3000 all yours

[jmilljr24]

Just to point out/clarify, the Pet model is scoped to the current organization using acts_as_tenant. @kasugaijin I think using organization_species could cause confusion. Since the model is already scoped to the org, it doesn't really tell me what the method is doing. Maybe unique_species or species_present , thoughts?

[kasugaijin]

@jmilljr24 I think unique_species is proably the clearest name

[kasugaijin]

@Yuji3000 let us know if you have any questions!

[Yuji3000]

@kasugaijin thank you

[kasugaijin]

@Yuji3000 are you still able to work on this? Let me know if not and I can reassign.