I am starting a pro bono project, which is the web interface for the world's largest collection of lute music, and it is a complex collection from several points of view. The pieces are mostly from 1,400 to 1,600, but they range from mid-1200 to the present. Needless to say, there is enormous variability in how parts are classified and to whom they are attributed. Obviously, any such rigid hierarchy with DB support will not work with this collection, so my thoughts turn to tags.
But not all tags are the same. I will have tags that represent the person / role (composer, translator, entabulator, etc.), tags that represent the instrument (s) written for the work, and tags that represent how the part was classified by any one half dozen various classification systems used over the centuries.
We will use a dictionary with a semi-controlled tag to prevent the proliferation of markup shortcuts (for example, del.icio.us), but I want to treat tags as belonging to different groups. People tags should not be offered when the editor marks the tool, etc.
Has anyone done something like this? I have several ways that I can come up with for this, but if there is an existing system that is well executed, it will save me some runtime / debugging time.
FWIW: This is a Django system, and I look at how to start with Django tagging and then hack there, possibly adding a category field or ...
source
share