<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Scholarly Works Application Profile on Ariadne</title>
    <link>http://www.ariadne.ac.uk/buzz/scholarly-works-application-profile/</link>
    <description>Recent content in Scholarly Works Application Profile on Ariadne</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Sat, 30 Jan 2010 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="http://www.ariadne.ac.uk/buzz/scholarly-works-application-profile/index.xml" rel="self" type="application/rss+xml" />
    
    
    <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 RSP Goes &#39;Back to School&#39;</title>
      <link>http://www.ariadne.ac.uk/issue/61/strsp-rpt/</link>
      <pubDate>Fri, 30 Oct 2009 00:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/61/strsp-rpt/</guid>
      <description>I recently attended the Back to School event [1] run by the Repositories Support Project (RSP)[2] at Matfen Hall [3], Northumberland, where I gave a workshop on metadata and also attended the second and third days of the event as a delegate. I was sorry not to be able to attend the sessions on the first day, but arrived in time for dinner so was able to meet the delegates and other presenters.</description>
    </item>
    
    <item>
      <title>Assessing FRBR in Dublin Core Application Profiles</title>
      <link>http://www.ariadne.ac.uk/issue/58/chaudhri/</link>
      <pubDate>Fri, 30 Jan 2009 00:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/58/chaudhri/</guid>
      <description>Efforts to create standard metadata records for resources in digital repositories have hitherto relied for the most part on the simple standard schema published by the Dublin Core Metadata Initiative (DCMI) [1], the Dublin Core Metadata Element Set, more commonly known as &#39;simple Dublin Core&#39; [2]. While this schema, by and large, met the aim of making metadata interoperable between repositories for purposes such as OAI-PMH [3], the explicit means by which it achieved this, a drastic simplification of the metadata associated with digital objects to only 15 elements, had the side effect of making it difficult or impossible to describe specific types of resources in detail [4].</description>
    </item>
    
    <item>
      <title>VIF: Version Identification Workshop</title>
      <link>http://www.ariadne.ac.uk/issue/55/vif-wrkshp-rpt/</link>
      <pubDate>Tue, 29 Apr 2008 23:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/55/vif-wrkshp-rpt/</guid>
      <description>The Version Identification Framework Project (VIF) [1] is a project partly funded by the Joint Information Systems Committee (JISC) and is in partnership with the Science &amp;amp; Technology Facilities Council, the University of Leeds and Erasmus University, Rotterdam. The project was undertaken in order to investigate the growing issues surrounding the identification of revised or related materials being deposited in repositories, with the aim of providing a framework for consistent identification.</description>
    </item>
    
    <item>
      <title>SWORD: Simple Web-service Offering Repository Deposit</title>
      <link>http://www.ariadne.ac.uk/issue/54/allinson-et-al/</link>
      <pubDate>Wed, 30 Jan 2008 00:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/54/allinson-et-al/</guid>
      <description>This article offers a twofold introduction to the JISC-funded SWORD [1] Project which ran for eight months in mid-2007. Firstly it presents an overview of the methods and madness that led us to where we currently are, including a timeline of how this work moved through an informal working group to a lightweight, distributed project. Secondly, it offers an explanation of the outputs produced for the SWORD Project and their potential benefits for the repositories community.</description>
    </item>
    
    <item>
      <title>Version Identification: A Growing Problem</title>
      <link>http://www.ariadne.ac.uk/issue/54/puplett/</link>
      <pubDate>Wed, 30 Jan 2008 00:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/54/puplett/</guid>
      <description>The problem of version identification in institutional repositories is multifaceted and growing. It affects most types of digital object now being deposited, and will continue to grow if left unaddressed as the proliferation of repositories continues and as they are populated with more and more content.
The JISC (Joint Information Systems Committee) has consequently funded the VIF Project as part of the Repositories and Preservation Programme, running from June 2007 to May 2008.</description>
    </item>
    
  </channel>
</rss>