Overview of content related to 'database' http://www.ariadne.ac.uk/taxonomy/term/50/all?article-type=&term=&organisation=&project=&author=thom%20bunting&issue= RSS feed with Ariadne content related to specified tag en Moving Ariadne: Migrating and Enriching Content with Drupal http://www.ariadne.ac.uk/issue69/bunting <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p><a href="/issue69/bunting#author1">Thom Bunting</a> explains some of the technology behind the migration of <em>Ariadne</em> (including more than 1600 articles from its back issues archive) onto a Drupal content management platform.</p> </div> </div> </div> <p>Tools and strategies for content management are a perennial topic in <em>Ariadne. </em> With&nbsp;<a href="/category/buzz/content-management?article-type=&amp;term=&amp;organisation=&amp;project=&amp;author=" title="Link to overview of articles including references to 'content management'">more than one hundred articles</a>&nbsp;touching on content management system (CMS) technologies or techniques since this online magazine commenced publication in 1996,&nbsp;<em>Ariadne</em>&nbsp;attests to continuing interest in this topic. Authors have discussed this topic within various contexts, from&nbsp;<a href="/category/buzz/content-management?article-type=&amp;term=intranet&amp;organisation=&amp;project=&amp;author=&amp;issue=#content-overview" title="Link to articles discussing 'content management', within 'intranet' context">intranets</a> to&nbsp;<a href="/category/buzz/repositories?article-type=&amp;term=content+management&amp;organisation=&amp;project=&amp;author=&amp;issue=#content-overview" title="Link to overview of articles referring to 'content management', within 'repositories' context">repositories</a>&nbsp;and&nbsp;<a href="/category/buzz/content-management?article-type=&amp;term=web+2.0&amp;organisation=&amp;project=&amp;author=&amp;issue=#content-overview" title="Link to overview of articles discussing 'content management', within context of Web 2.0">Web 2.0</a>, &nbsp;with some notable&nbsp;<a href="/sites/all/datacharts/hc/72-chart-wp.html#timeline" title="Link to timeline: articles referring to 'content management'">surges in references to 'content management' between 2000 and 2005</a>&nbsp;(see Figure 1 below). &nbsp;Although levels of discussion are by no means trending, over recent years it is clear that&nbsp;<em>Ariadne</em> authors have taken note of and written about content management tools and techniques on a regular basis.&nbsp;</p> <p>In the light of this long-established interest, it is noteworthy that&nbsp;<em>Ariadne</em> itself migrated into a content management system only recently. Although the formatting of its articles did change a few times since 1996, <em>Ariadne</em>&nbsp;remained 'hand-coded' for more than fifteen years. &nbsp;None of its articles had been migrated into a database-driven content management system until March 2012, when&nbsp;<a href="/issue68" title="Link to table of contents for Ariadne issue 68">issue 68</a>&nbsp;was published.&nbsp;&nbsp;</p> <p>As mentioned in the&nbsp;<a href="/issue68/editorial1" title="Editorial introduction: Welcome to New Ariadne">editorial introduction</a>&nbsp;to that first issue, launching the new content management arrangements, and as discussed in some more detail below (see 'Technical challenges in content migration'), the considerable size of&nbsp;<em>Ariadne</em>'s archive of back issues was daunting. &nbsp;With <a href="/articles" title="Overview of more than 1600 articles in Ariadne">more than 1600 articles</a>&nbsp;in hand-coded 'flat'-html formats,&nbsp;the process of migration itself required careful planning to result in a seamless, graceful transition into an entirely new content management arrangement. &nbsp;Over time, the sheer size of the <em>Ariadne</em> corpus had made it both increasingly rich in content and increasingly more challenging to convert retrospectively into a database-driven CMS as the total number of articles published within this online magazine steadily expanded.&nbsp;</p> <p>In looking back over the recent process of migrating <em>Ariadne</em> onto a CMS platform, this article discusses some tools and techniques used to prepare content for transfer, testing, and then re-launch. &nbsp;After explaining some of the background to and objectives of this work, this article focuses on key features of content management supported by Drupal.&nbsp;</p> <p style="text-align: center; "><img alt="Figure 1: Timeline of references in Ariadne to content management" src="http://ariadne-media.ukoln.info/grfx/img/issue69-bunting/content%20management-timeline.png" style="height: 453px; width: 500px; " title="Figure 1: Timeline of references in Ariadne to content management" /></p> <p style="text-align: center; "><strong>Figure 1: Ariadne timeline of references to content management</strong></p> <h2 id="Requirements_Analysis:_Planning_the_Way_Forward">Requirements Analysis: Planning the Way Forward</h2> <p>Based on surveys of readers and authors conducted in late 2010, the <em>Ariadne</em>&nbsp;management team analysed the range of feedback, drew up sets of re-development requirements, and then considered the options available.</p> <p>The following table provides an overview of key findings regarding the range of enhanced functionality and features considered:</p> <table align="center" border="1" cellpadding="1" cellspacing="1" id="500wtable" style="width: 500px; "> <tbody> <tr> <td colspan="2" style="text-align: center; "><strong>Overview of findings derived from survey responses</strong></td> </tr> <tr> <td style="text-align: center; "><em>enhanced functionality or feature</em></td> <td style="text-align: center; "><em>interest recorded in surveys</em></td> </tr> <tr> <td>browsing by keywords</td> <td>73.4% of respondents</td> </tr> <tr> <td>updated look and feel</td> <td>62.3% of respondents</td> </tr> <tr> <td>browsing by title</td> <td>50.0% of respondents</td> </tr> <tr> <td>enhanced use of search engine</td> <td>48.0% of respondents</td> </tr> <tr> <td>improved display for portable devices</td> <td>34.0% of respondents</td> </tr> <tr> <td>more summative information on articles</td> <td>32.1% of respondents</td> </tr> <tr> <td>improved navigability from article level</td> <td>32.1% of respondents</td> </tr> <tr> <td>improved social media options</td> <td>29.5% of respondents</td> </tr> <tr> <td>browsing by author</td> <td>28.0% of respondents</td> </tr> <tr> <td>improved RSS feeds</td> <td>27.0% of respondents</td> </tr> </tbody> </table> <p>In addition to these findings derived from surveys, the management team also recognised the need for some other functionalities to support monitoring of <em>Ariadne</em>'s on-going engagement with various domains and institutions across the UK and beyond.</p> <table align="center" border="1" cellpadding="1" cellspacing="1" id="500wtable" style="width: 500px; "> <tbody> <tr> <td colspan="2" style="text-align: center; "><strong>Additional features to support monitoring of engagement</strong></td> </tr> <tr> <td style="text-align: left; ">identification of author domains (higher education, further education, research, commercial, etc)</td> <td style="text-align: left; ">to support analysis of <em>Ariadne</em> connections and reach across various sectors</td> </tr> <tr> <td>identification of authors by organisation</td> <td>to support analysis of <em>Ariadne</em> connections and reach in UK and worldwide</td> </tr> </tbody> </table> <p>Taking into account the key findings derived from survey questions as well as the additional functionality identified as useful in monitoring UK and worldwide engagement, the <em>Ariadne</em>&nbsp;management team drew up sets of re-development requirements and considered how to proceed.&nbsp;Migration into a content management system represented the obvious way forward, as it became clear that <em>Ariadne</em>'s&nbsp;previous tradition of 'hand-coded' production (dating from the early days of the Web) had little chance of coping gracefully with the new sets of requirements.</p> <p>In a review of CMS options available, it also became clear that&nbsp;&nbsp;<a href="http://en.wikipedia.org/wiki/Drupal" title="Wikipedia article: Drupal">Drupal</a>&nbsp;[<a href="#1">1</a>] was well positioned as a content management system (or, emphasising its highly modular and extensible design, <em>content management framework </em>&nbsp;[<a href="#2">2</a>] ) to supply required functionality and features.</p> <p></p><p><a href="http://www.ariadne.ac.uk/issue69/bunting" target="_blank">read more</a></p> issue69 tooled up thom bunting ibm microsoft ukoln university of bath datagovuk gnu wikipedia apache api archives bibliographic data content licence content management css data data set database drupal framework further education graphics higher education html identifier jquery json licence linux metadata mysql open source perl php preservation python rdf repositories research rss search technology software sql server sqlite standards taxonomy usability video visualisation web 2.0 xml Fri, 27 Jul 2012 16:47:36 +0000 lisrw 2348 at http://www.ariadne.ac.uk