Previously, the way meta data was saved on melative was using bbcode (described near the bottom of this post). This was a good solution as it is similar to ml tags and can be easily transformed to xml for filtering (usually just replace [] with <>, of course it wasn’t that simple).
After examining Wikipedia’s wikitext markup, I decided that this is an easier format to work with, for user data entry. While context is everything, here is the basic translation from bbcode to wiki-like markup on melative (I’ll call it double-braced, dubraced for short):
bbcoded: [artist]Love Is All[note]Original music[/note][/artist]
dubraced: [[artist|Love Is All|Original music]]
bbcoded: [character]Tyler Durden[actor]Brad Pitt[/actor][note]multi[/note][/character]
dubraced: [[character|Tyler Durden|Brad Pitt|multi]]
bbcoded: [character]Nogizaka Haruka[note]?????[/note][/character]
dubraced: [[character|Nogizaka Haruka||?????]] (notice double v.bar)
bbcoded: [artist]D[di:][/artist]
dubraced: [[artist|D[di:]]] (notice triple bracket)
The context of what each partition ‘|’ represents differs slightly depending on the containing field (ie. Production, Characters, Standards). While the limit of partitions and meaning has not been decided, 2-3 will be the maximum. Here are the current specs on meta fields:
- Base, Production, Standards
- [[tag|data|note]]
- Characters
- [[tag|character_name|actor_name|note]]
Looking at the context for Characters, the tag partition is redundant and should be [[character_name|actor_name|note]], because all tags within the Characters field will be ‘character’.
On another note, this has been implemented, and the variations have been translated from the bbcode format to this format. They are now stored as serialized arrays, rather than the bbcode text. Of course this does take more space, but for the sake of editing ease.
