1 | <?xml version="1.0" encoding="UTF-8"?>
|
---|
2 | <!DOCTYPE videocollection [
|
---|
3 | <!ENTITY ndash "–">
|
---|
4 | <!ENTITY mdash "—">
|
---|
5 | ]>
|
---|
6 | <xsl:stylesheet version="1.0"
|
---|
7 | xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
|
---|
8 | xmlns:java="http://xml.apache.org/xslt/java"
|
---|
9 | xmlns:util="xalan://org.greenstone.gsdl3.util.XSLTUtil"
|
---|
10 | xmlns:gslib="http://www.greenstone.org/skinning"
|
---|
11 | extension-element-prefixes="java util"
|
---|
12 | exclude-result-prefixes="java util">
|
---|
13 |
|
---|
14 | <!-- use the 'main' layout -->
|
---|
15 | <xsl:include href="layouts/main.xsl"/>
|
---|
16 |
|
---|
17 | <!-- set page title -->
|
---|
18 | <xsl:template name="pageTitle"><gslib:collectionName/></xsl:template>
|
---|
19 |
|
---|
20 | <!-- set page breadcrumbs -->
|
---|
21 | <xsl:template name="breadcrumbs"><gslib:siteLink/><gslib:rightArrow/></xsl:template>
|
---|
22 |
|
---|
23 | <!-- the page content -->
|
---|
24 | <xsl:template match="/page">
|
---|
25 |
|
---|
26 | <!--Display the description text of the current collection,
|
---|
27 | and if some services are available then create a list
|
---|
28 | of links for each service within a <ul id="servicelist"> element.-->
|
---|
29 |
|
---|
30 | <xsl:variable name="httpPath">
|
---|
31 | <xsl:value-of select="/page/pageResponse/collection/metadataList/metadata[@name='httpPath']" />
|
---|
32 | </xsl:variable>
|
---|
33 |
|
---|
34 |
|
---|
35 | <style>
|
---|
36 | p.about { text-align: justify; }
|
---|
37 | h2 { /* line-height: 135%; */ }
|
---|
38 | h3 { margin-top: 4pt; margin-bottom: 7pt; line-height: 135%; }
|
---|
39 |
|
---|
40 | a.mashup {text-decoration: none; }
|
---|
41 | a.mashup:link {color:#000080;} /* unvisited link */
|
---|
42 | a.mashup:visited {color:#303080;} /* visited link */
|
---|
43 | a.mashup:hover {color:#000040;} /* mouse over link */
|
---|
44 | a.mashup:active {color:#0000a0;}
|
---|
45 |
|
---|
46 | </style>
|
---|
47 |
|
---|
48 |
|
---|
49 | <script src="{$httpPath}/script/browser-detect.js" type="text/javascript">
|
---|
50 | /* space filler needed */
|
---|
51 | </script>
|
---|
52 |
|
---|
53 |
|
---|
54 | <div style="width: 800px; margin-left: auto; margin-right: auto;">
|
---|
55 |
|
---|
56 |
|
---|
57 | <style>
|
---|
58 | li { padding-bottom: 10px; }
|
---|
59 | </style>
|
---|
60 |
|
---|
61 | <h2>A Traditional Music Digital Library: my-ipod </h2>
|
---|
62 |
|
---|
63 |
|
---|
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:
|
---|
66 |
|
---|
67 |
|
---|
68 | <ol>
|
---|
69 | <li>The selected audio files are automatically converted to a format suitable for streaming
|
---|
70 | over the web
|
---|
71 | </li>
|
---|
72 |
|
---|
73 | <li>
|
---|
74 | Metadata embedded in the files (such as ID3 tags) is automatically extracted and made
|
---|
75 | available to form browsing structures, used in full-text indexes for searching, as well as
|
---|
76 | being manipulated and presented to the user, where applicable.
|
---|
77 | </li>
|
---|
78 |
|
---|
79 | <li>
|
---|
80 | Automatically extracted metadata can be override by manually assigned. This
|
---|
81 | can either be done through a desktop application (the Greenstone Librarian Interface, or GLI for short)
|
---|
82 | a graphical user interface that controls all aspects of collection design, or directly through
|
---|
83 | the web browser, on a per-document basis.
|
---|
84 | </li>
|
---|
85 | </ol>
|
---|
86 |
|
---|
87 | </p>
|
---|
88 |
|
---|
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>
|
---|
133 |
|
---|
134 |
|
---|
135 |
|
---|
136 |
|
---|
137 | <p class="about">Interested in the song <i>Candela</i> our curious musicologist clicks
|
---|
138 | 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 |
|
---|
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 |
|
---|
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>
|
---|
167 |
|
---|
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>
|
---|
174 |
|
---|
175 |
|
---|
176 |
|
---|
177 | <h3>Implementation details</h3>
|
---|
178 |
|
---|
179 | <p class="about">The core part of the interactive elements in the document view were
|
---|
180 | implemented using SVG combined with Javascript. The left- and
|
---|
181 | right-panning interactively available from the self-similarity map was
|
---|
182 | implemented by processing the raw audio stream, made accessible by the
|
---|
183 | Firefox Audio extension
|
---|
184 | <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 through
|
---|
187 | two components of the digital library software architecture: its
|
---|
188 | build-time document processing plugin system, and its runtime
|
---|
189 | message-passing service-base framework. The developed plugin accepts
|
---|
190 | a wide range of audio formats (including OGG and MP3), and converts
|
---|
191 | them to WAV, the format needed by AudioDB for processing. The new
|
---|
192 | search service took the form of a proxy, accepting messages in the
|
---|
193 | XML syntax used by Greenstone, turning them into the necessary calls
|
---|
194 | to the AudioDB command-line interface, and then converting the output
|
---|
195 | from AudioDB back into the XML syntax expected by the digital library
|
---|
196 | architecture. Finally, the two parts were packaged to operate as a
|
---|
197 | 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 |
|
---|
202 |
|
---|
203 | </xsl:template>
|
---|
204 |
|
---|
205 |
|
---|
206 | </xsl:stylesheet>
|
---|
207 |
|
---|