I'm about to write a custom module dealing with chemical hazards symbols. It's basically a 300-item dictionary of simple objects: a symbol, its description (around 100 chars) and in some cases a supplementary short information.
I'm still undecided whether I'd make my module a text filter, field or entity, but regardless (I think) of the way I choose, I'm clueless about what would be the Drupal way to install this simple dictionary: as a PHP variable or a database table?
My guess would be that storing it as PHP variable would not burden the momenry too much, would provide quick lookup access and would save database queries. Would there be any benefit to choose the table option?
What is limiting me in using taxonomy here is that some terms would have to be supplemented by a piece of information on a binding/instance level. For example there would be a symbol (term)
P0123: Store in temperatures below %1 C/ %2 F or
P2345: Wash %1 thoroughly after handling. For each node referencing that term there should be a possibility to add the precise values that might be different per node. That is the reason I have been thinking of making it a text filter that would parse line:
P0123,10,50 (<- term with supplementary contextual values, %1 and %2) P2345,en:hands|de:Hande|es:manos (<- i18n-savvy contextual string) P3456 (<- term without additional info)
I have already filed a feature request for the Relation module, to provide labelling of relationships on instance level. We'll see if the authors consider it as worth implementing for a wider public. For now I'm trying to find a swift workaround.