<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Richard Jones on Ariadne</title>
    <link>http://www.ariadne.ac.uk/authors/richard-jones/</link>
    <description>Recent content in Richard Jones on Ariadne</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Fri, 30 Nov 2012 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="http://www.ariadne.ac.uk/authors/richard-jones/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Motivations for the Development of a Web Resource Synchronisation Framework</title>
      <link>http://www.ariadne.ac.uk/issue/70/lewis-et-al/</link>
      <pubDate>Fri, 30 Nov 2012 00:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/70/lewis-et-al/</guid>
      <description>This article describes the motivations behind the development of the ResourceSync Framework. The Framework addresses the need to synchronise resources between Web sites. &amp;nbsp;Resources cover a wide spectrum of types, such as metadata, digital objects, Web pages, or data files. &amp;nbsp;There are many scenarios in which the ability to perform some form of synchronisation is required. Examples include aggregators such as Europeana that want to harvest and aggregate collections of resources, or preservation services that wish to archive Web sites as they change.</description>
    </item>
    
    <item>
      <title>Towards a Toolkit for Implementing Application Profiles</title>
      <link>http://www.ariadne.ac.uk/issue/62/chaudhri-et-al/</link>
      <pubDate>Sat, 30 Jan 2010 00:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/62/chaudhri-et-al/</guid>
      <description>The development of the Dublin Core Application Profiles (DCAPs) has been closely focussed on the construction of metadata standards targeted at specific resource types, on the implicit assumption that such a metadata solution would be immediately and usefully implementable in software environments that deal with such resources. The success of an application profile would thus be an inevitable consequence of correctly describing the generalised characteristics of those resources. Yet despite the earlier success of application profiles, more recent growth in usage of the DCAPs funded by the Joint Information Systems Committee (JISC) has been slow by comparison [1].</description>
    </item>
    
    <item>
      <title>The Tapir: Adding E-Theses Functionality to DSpace</title>
      <link>http://www.ariadne.ac.uk/issue/41/jones/</link>
      <pubDate>Fri, 29 Oct 2004 23:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/41/jones/</guid>
      <description>The Theses Alive Plugin for Institutional Repositories (Tapir) [1] has been developed at Edinburgh University Library [2] to help provide an E-Thesis service within an institution using DSpace [3]. It has been developed as part of the Theses Alive! [4] Project under funding from the Joint Information Systems Committee (JISC) [5], as part of the Focus on Access to Institutional Resources (FAIR) [6] Programme.
This article looks at DSpace, the repository system initially developed by Hewlett-Packard and MIT and subsequently made available as a community-owned package.</description>
    </item>
    
    <item>
      <title>DSpace Vs. ETD-db: Choosing Software to Manage Electronic Theses and Dissertations</title>
      <link>http://www.ariadne.ac.uk/issue/38/jones/</link>
      <pubDate>Fri, 30 Jan 2004 00:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/38/jones/</guid>
      <description>The Theses Alive! [1] Project, based at Edinburgh University Library and funded under the JISC Fair Programme [2], is aiming to produce, among other things, a software solution for institutions in the UK to implement their own E-theses or Electronic Theses and Dissertations (ETD) online submission system and repository. In order to achieve this it has been necessary to examine existing packages that may provide all or part of the solution we desire before considering what extra development we may need to do.</description>
    </item>
    
  </channel>
</rss>