The tags branch
Tony Olivo
I haven't looked into the tagging code you've been working on, but I did just run it locally. It pretty much behaves how I would expect already. I'm not sure what you have planned already, but three ideas popped up for me.
1. Tag reports - Pretty much the same view you have now when you select someone's tag from their person show page, but accessible from the report page where you can just select the tag from the list of possible tags.
2. Mass tagging - Doesn't really fit in with any of the reports that are there now, but say if you had a report that could list all members that haven't shown up in a year, you could "tag all as..." and put a tag like "expired" in for them. This is a little silly, because I know membership status is already shown on the people/1 page. This might end up subverting some things that actually belong as attributes of the people class, but it gives non-rails savvy co-ops the chance to extend Freehub's functionality without too much effort.
3. Automatic tagging - This ends up getting a little complicated, but in the same vein as above. If certain conditions are met, like say 10 hours of volunteering/month for the last three months, add a particular tag to them. I don't even know where to begin with that one, because the thought again would be to let it be an easy way for non-developers to extend Freehub.
All of this reminds me, there might be some opportunity in the reports section for more advanced search mechanisms. More on that if I think about it again.
-Tony
Alon Salant
> just run it locally. It pretty much behaves how I would expect already. I'm
> not sure what you have planned already, but three ideas popped up for me.
I'm planning to merge it in to master and release it soon to
freehub.bikekitchen.org with some minor enhancements, primarily more
person details on the view that lists all people with a specific tag.
> 1. Tag reports - Pretty much the same view you have now when you select
> someone's tag from their person show page, but accessible from the report
> page where you can just select the tag from the list of possible tags.
Yep. This will likely be the next feature/enhancement. Along with this
you may want more sophisticated filters like all people with tag 'foo'
and tag 'bar'. Or with tag 'foo' and not tag 'bar'. That would
probably come later if it seems desirable.
I've looked a couple systems that implement tagging and have been
modeling much of my strategy after 37 Signals' Highrise -
http://highrisehq.com.
> 2. Mass tagging - Doesn't really fit in with any of the reports that are
> there now, but say if you had a report that could list all members that
> haven't shown up in a year, you could "tag all as..." and put a tag like
> "expired" in for them. This is a little silly, because I know membership
> status is already shown on the people/1 page. This might end up subverting
> some things that actually belong as attributes of the people class, but it
> gives non-rails savvy co-ops the chance to extend Freehub's functionality
> without too much effort.
Yep. I any time you have a list of people, you may want to tag all or
some of them.
> 3. Automatic tagging - This ends up getting a little complicated, but in the
> same vein as above. If certain conditions are met, like say 10 hours of
> volunteering/month for the last three months, add a particular tag to them.
> I don't even know where to begin with that one, because the thought again
> would be to let it be an easy way for non-developers to extend Freehub.
Interesting. I'd better be able to think about this with a real world
need in mind.
> All of this reminds me, there might be some opportunity in the reports
> section for more advanced search mechanisms. More on that if I think about
> it again.
For sure. Reporting is pretty primitive. I haven't heard much in the
way of specific needs for reporting so they have not received much
love.
Alon