Changeset 28470
- Timestamp:
- 2013-10-16T17:54:38+13:00 (10 years ago)
- Location:
- main/trunk/model-sites-dev/multimodal-mdl/collect
- Files:
-
- 6 edited
Legend:
- Unmodified
- Added
- Removed
-
main/trunk/model-sites-dev/multimodal-mdl/collect/js-dsp-my-ipod/etc/collectionConfig.xml
-
Property svn:mime-type
changed from
application/xml
totext/plain
-
Property svn:mime-type
changed from
-
main/trunk/model-sites-dev/multimodal-mdl/collect/linkeddata-my-ipod/etc/collectionConfig.xml
-
Property svn:mime-type
changed from
application/xml
totext/plain
-
Property svn:mime-type
changed from
-
main/trunk/model-sites-dev/multimodal-mdl/collect/linkeddata-my-ipod/transform/pages/about.xsl
-
Property svn:mime-type
changed from
application/xml
totext/plain
r28435 r28470 46 46 </style> 47 47 48 48 <!-- 49 49 <script src="{$httpPath}/script/browser-detect.js" type="text/javascript"> 50 50 /* space filler needed */ 51 51 </script> 52 52 --> 53 53 54 54 <div style="width: 800px; margin-left: auto; margin-right: auto;"> … … 59 59 </style> 60 60 61 <h2>A Traditional Music Digital Library: my-ipod </h2>62 61 63 62 64 <p class="about">This collection represents the <i>status quo</i> in traditional 65 digital library design for music content. When the collection is built: 63 <h2>Utilizing Linked-data in a Music Digital Library: my-ipod </h2> 66 64 65 66 <p class="about"> 67 This collection explores the role linked data can play in a 68 music digital library. There are two key phases where 69 linked data has been applied to the digital library design: 70 </p> 71 72 <ol> 73 <li> 74 <i>Build-time</i>, when the digital library collection is initially formed 75 (also when subsequently rebuilt). 76 </li> 77 78 <li> 79 <i>Runtime</i>, when ... 80 </li> 81 </ol> 82 83 84 85 <p class="about"> 86 At ingest time, audio fingerprinting is used 87 to using to allign (where possible) audio content with MusicBrainz 88 IDs. From there 89 90 linked-data 91 </p> 92 93 <p class="about"> 94 95 The selected audio files are automatically converted to a format suitable for streaming 96 </p> 97 98 <p class="about"> 99 Or else access the <a href="http://localhost:3030/">Sparql Endpoint</a> to the digital library. 67 100 68 101 <ol> … … 87 120 </p> 88 121 89 90 <h3>A Walkthrough</h3> 91 92 <p class="about">Taking as a starting point a set of music files identified as worthy 93 of study, the <a href="#browse">figure below</a> shows the result of browsing 94 the formed digital library collection <a href="dev?a=b&rt=s&s=ClassifierBrowse&c=salami-audioDB&cl=CL1" target="_blank">by title</a> from a web browser. 95 The figure is a useful snapshot in which to orientate ourselves with 96 the main structure and features to the digital library. Functionality that 97 persistently reoccurs is accessible through the header to the page.</p> 98 99 <p class="about">This includes: 100 <ul> 101 102 <li>help and preferences (top-right);</li> 103 <li>a quick-search option (located just 104 below) with links to more sophisticated searching options; and</li> 105 <li>pin-pointing where within the site a user is currently located 106 (top-left).</li> 107 </ul> 108 109 110 <a name="browse" /> 111 <table style="width: 700px; margin-left: auto; margin-right: auto; margin-bottom: 6pt;"> 112 <tr> 113 <td style="border: solid 1px;"> 114 <img style="width: 700px" src="{$httpPath}/images/figs/cropped/salami-browse.png" /> 115 </td> 116 </tr> 117 <tr style="background-color: #bbeebb"> 118 <td> 119 <i>Browsing in the digital library 120 <a href="dev?a=b&rt=s&s=ClassifierBrowse&c=salami-audioDB&cl=CL1" target="_blank">by titles</a>.</i> 121 </td> 122 </tr> 123 </table> 124 125 126 The specific content to this location within the site (in this case 127 browsing by title) is shown beneath the main banner. Various 128 groupings of title can be accessed by clicking on the bookshelf icons 129 vertically aligned as the main part of the page: currently <a 130 href="dev?a=b&rt=s&s=ClassifierBrowse&c=salami-audioDB&cl=CL1#CL1.2">CâD</a> 131 is open, with the remaining letters to the alphabet below this, 132 accessed through scrolling.</p> 122 </div> 133 123 134 124 135 125 136 126 137 <p class="about">Interested in the song <i>Candela</i> our curious musicologist clicks138 on <a href="dev?a=d&ed=1&book=off&c=salami-audioDB&d=D145&dt=simple&sib=1&p.a=b&p.sa=&p.s=ClassifierBrowse" target="_blank">the link for this</a>. This brings up the document view to this song:</p>139 127 140 <a name="self-similarity" />141 <table style="width: 700px; margin-left: auto; margin-right: auto; margin-bottom: 6pt;">142 <tr>143 <td style="border: solid 1px;">144 <img style="width: 700px" src="{$httpPath}/images/figs/cropped/salami-self-similarity2.png" />145 </td>146 </tr>147 <tr style="background-color: #bbeebb">148 <td>149 <i>The <a href="dev?a=d&ed=1&book=off&c=salami-audioDB&d=D145&dt=simple&sib=1&p.a=b&p.sa=&p.s=ClassifierBrowse" target="_blank">musicologically enriched document view</a> for</i> Candela.150 </td>151 </tr>152 </table>153 128 154 <p class="about">Normally in a digital 155 library the document view brings up a page that is strongly derived 156 from textual metadata. If the document viewed was a text-document, 157 some summary information such as title and author is typically 158 presented, say in tabular form, before the main text is presented. 159 Even in the case of multimedia digital libraries, the view presented 160 is still strongly derived from textual metadata: this time including 161 details such as the length of the video, the TV company that produced 162 it, whether captions are available, and so forth, accompanied with an 163 embedded video player for viewing the contentâessentially more 164 textual metadata (in this case the URL to the video content) which in 165 terms of the user-interface is largely divorced from the other 166 elements displayed on the page.</p> 129 <script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.6.2/jquery.min.js"><xsl:text> </xsl:text></script> 167 130 168 <p class="about">This contrasts sharply with the document view developed in this 169 digital library. 170 Naturally it allows the song to be played (akin to the embedded video player), 171 however this is largely of secondary importance to the 172 other functionality available this is much more closely 173 integrated.</p> 131 <script type="text/javascript" src="https://www.google.com/jsapi"><xsl:text> </xsl:text></script> 132 <script type="text/javascript" id="sgvzlr_script" src="http://sgvizler.googlecode.com/svn/release/0.5/sgvizler.js"><xsl:text> </xsl:text></script> 133 134 <script type="text/javascript"> 135 <xsl:text disable-output-escaping="yes"> 136 sgvizler.option.namespace.mo ='http://purl.org/ontology/mo/'; 137 sgvizler.option.namespace.salami = 'http://nema.lis.illinois.edu/salamiEndpoint/'; 138 139 sgvizler.option.namespace.salami = 'http://nema.lis.illinois.edu/salamiEndpoint/'; 140 141 sgvizler.option.namespace.gsembedded = 'http://greenstone.org/gsembedded#' 142 sgvizler.option.namespace.greenstonedata = 'http://localhost:3030/greenstone/data/' 143 $(document).ready(sgvizler.go()); 144 </xsl:text> 145 </script> 146 147 <div id="sgvzl_example" 148 data-sgvizler-endpoint="http://localhost:3030/greenstone/query" 149 150 data-sgvizler-chart="gPieChart" 151 XXdata-sgvizler-chart="gBarChart" 152 data-sgvizler-loglevel="2" 153 data-sgvizler-chart-options="title=Songs by ID3.Genre" 154 style="width:100%; height:300px;"> 155 <xsl:attribute name="data-sgvizler-query"> 156 SELECT (?genreTag) (COUNT(?genreTag) AS ?freqCount) 157 WHERE { 158 GRAPH <http://localhost:3030/greenstone/data/linkeddata-my-ipod> { 159 ?s <http://greenstone.org/gsembedded#ID3.Genre> ?genreTag . 160 } 161 } 162 GROUP BY ?genreTag 163 </xsl:attribute> 164 </div> 174 165 175 166 176 167 177 <h3>Implementation details</h3>178 179 <p class="about">The core part of the interactive elements in the document view were180 implemented using SVG combined with Javascript. The left- and181 right-panning interactively available from the self-similarity map was182 implemented by processing the raw audio stream, made accessible by the183 Firefox Audio extension184 <a href="https://wiki.mozilla.org/Audio_Data_API" target="_blank">API</a>.</p>185 186 <p class="about">AudioDB content based searching was integrated into Greenstone through187 two components of the digital library software architecture: its188 build-time document processing plugin system, and its runtime189 message-passing service-base framework. The developed plugin accepts190 a wide range of audio formats (including OGG and MP3), and converts191 them to WAV, the format needed by AudioDB for processing. The new192 search service took the form of a proxy, accepting messages in the193 XML syntax used by Greenstone, turning them into the necessary calls194 to the AudioDB command-line interface, and then converting the output195 from AudioDB back into the XML syntax expected by the digital library196 architecture. Finally, the two parts were packaged to operate as a197 Greenstone extension; the software is available at:198 <a href="http://trac.greenstone.org/gs3-extensions/audioDB/trunk/src" target="_blank">http://trac.greenstone.org/gs3-extensions/audioDB/trunk/src</a>.</p>199 200 </div>201 168 202 169 -
Property svn:mime-type
changed from
-
main/trunk/model-sites-dev/multimodal-mdl/collect/salami-ground-truth/etc/collectionConfig.xml
-
Property svn:mime-type
changed from
application/xml
totext/plain
-
Property svn:mime-type
changed from
-
main/trunk/model-sites-dev/multimodal-mdl/collect/selfsim-my-ipod/etc/collectionConfig.xml
-
Property svn:mime-type
changed from
application/xml
totext/plain
-
Property svn:mime-type
changed from
-
main/trunk/model-sites-dev/multimodal-mdl/collect/trad-my-ipod/etc/collectionConfig.xml
-
Property svn:mime-type
set to
text/plain
-
Property svn:mime-type
set to
Note:
See TracChangeset
for help on using the changeset viewer.