Classical Music Tree
Posted: Mon Jan 25, 2010 5:14 pm
I was given to understand that TMS 5.1.2 with xxx.view.xml files would allow one to organise classical music in a logical and accessible manner eg Composer/Work/Movement, Artist/Composer/Work/Movement
The "View configuration TwonkyMedia server.pdf" file (which is repleat with errors eg is it defaut.view or view.definitions? and omissions eg comprehensive database properties and fixed ID strings) provides some insight but I conclude that if the relevent [fixed ID string] eg [music/composerindex] doesn't exist (which is doesn't) you can't, for example, index on the database to set up a composer alpha list etc.
Nor can I see (I have tried and still working on this) how to modify composer tree to give composer/work( I use album for this purpose) and movement (I use track for this).
So all this stuff about configurability is not much use for a classical collection dispite all the chatter and promises related to this subject. If elements such as music/composerindex don't exist then that is the end of the story. I conclude that each fixed ID string is hard coded and if you want to do something as described above you can't.
Is this right? or have I missed something?
Does TwonkyMedia have any idea about classical music structure? Do they even care? An honest answer would save me wasting time trying to fathom the futile.
Thanks for any thoughts on the above Chris Worthington
The "View configuration TwonkyMedia server.pdf" file (which is repleat with errors eg is it defaut.view or view.definitions? and omissions eg comprehensive database properties and fixed ID strings) provides some insight but I conclude that if the relevent [fixed ID string] eg [music/composerindex] doesn't exist (which is doesn't) you can't, for example, index on the database to set up a composer alpha list etc.
Nor can I see (I have tried and still working on this) how to modify composer tree to give composer/work( I use album for this purpose) and movement (I use track for this).
So all this stuff about configurability is not much use for a classical collection dispite all the chatter and promises related to this subject. If elements such as music/composerindex don't exist then that is the end of the story. I conclude that each fixed ID string is hard coded and if you want to do something as described above you can't.
Is this right? or have I missed something?
Does TwonkyMedia have any idea about classical music structure? Do they even care? An honest answer would save me wasting time trying to fathom the futile.
Thanks for any thoughts on the above Chris Worthington
