DigtheDirt has an extensive search system built in. I’ll talk more about the meta model in a bit, but for now, I wanted to talk about the tagging system.
- I wanted tighter control of the metamodel within the search
- I needed to use the tags for many other associations, so we could associate plants with member contributions and users.
- I wanted to keep the deployment footprint dead simple.
So in general, every plant attribute is a tag. For search time behavior, it’s great because I have to count tags early and often, and tags are easy to count.
But write-time performance suffers, and it’s more complex to render a simple plant. I’ll talk about why this tradeoff doesn’t matter as much in a later post.
Next, I’ll introduce the plant card system and the adaptive search.