| Issue 96: | Add support to repository for representing data about remote collections | |
| 1 person starred this issue and may be notified of changes. | Back to list |
|
Add support to the repository to represent metadata and location information about remote repositories. Import Codaich collection from McGill as first example - for which we need to establish an iTunes XML parser tool. Detail from Cory on Codaich: Hi NEMA As we discussed at our meeting in Illinois, I’ve posted the metadata for Codaich as iTunes XML files. It’s divided into four general sets (which have some small overlap in genres due to compilation albums): http://coltrane.music.mcgill.ca/codaich/CodaichClassical.xml http://coltrane.music.mcgill.ca/codaich/CodaichJazz.xml http://coltrane.music.mcgill.ca/codaich/CodaichPopular.xml http://coltrane.music.mcgill.ca/codaich/CodaichWorld.xml This is the current mostly very clean version of Codaich. The “official” smaller but super clean version of Codaich’s metadata is also available at http://sourceforge.net/projects/jmir/. The file paths stored in the iTunes XML files do not correspond to where the files really are, but we can use the contents of this field as a unique identifier on the server once we get an OMEN-like infrastructure in place. If you don’t have a way of browsing iTunes XML conveniently, jMusicMetaManager (available at http://sourceforge.net/projects/jmir/) can be used (it also includes code that you can access externally to do this if you don’t want to use jMusicMetaManager directly). We can set up a better infrastructure once we have more specific details of exactly what OMEN-like software will be set up at nodes like McGill.
Jun 16, 2010
Project Member
#1
kris.west@gmail.com
Status:
Accepted
Jun 16, 2010
(No comment was entered for this change.)
Labels:
-Priority-Low Priority-High
Jun 22, 2010
Implemented, field needs to be used in remote processing components to prep and despatch jobs
Status:
Fixed
|
||||||||||