<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="http://iplus.ukoln.ac.uk/taxonomy/term/102/component-associated/all" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#">
  <channel>
    <title>Technical overview and related use cases: rioxx</title>
    <link>http://iplus.ukoln.ac.uk/taxonomy/term/102/component-associated/all</link>
    <description>RSS feed: components in specified supplier category</description>
    <language>en</language>
          <item>
    <title>RIOXX</title>
    <link>http://iplus.ukoln.ac.uk/technology/rioxx</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p&gt;RIOXX is a JISC-funded project (managed by UKOLN) to develop a simple DC application profile for bibliographic metadata to be exposed by UK open access repositories.  The RIOXX profile should enable UK repositories to be as compliant as possible to the OpenAIRE guidelines and to satisfy the simplest possible requirements as set out in the final report of the RIO extension project: including unambiguous fields for project identifier, funder identifier, DOI, identifier for related dataset, embargo type, embargo end date, access level semantics.&lt;/p&gt;
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Fri, 05 Oct 2012 11:45:47 +0000</pubDate>
 <dc:creator>admin</dc:creator>
 <guid isPermaLink="false">67 at http://iplus.ukoln.ac.uk</guid>
  </item>
  <item>
    <title>Proposed dashboard for tracking OA mandate compliance</title>
    <link>http://iplus.ukoln.ac.uk/usecase/proposed-dashboard-tracking-oa-mandate-compliance</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p&gt;This use case outlines potential user requirements and technical development considerations for a proposed dashboard tool monitoring compliance rates with regard to funder policies on Open Access (OA).  This proposed dashboard, as part of its wider remit, would also help track various outputs and payments as funded research progresses through stages towards OA publication.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Thu, 01 Nov 2012 15:32:21 +0000</pubDate>
 <dc:creator>admin</dc:creator>
 <guid isPermaLink="false">69 at http://iplus.ukoln.ac.uk</guid>
  </item>
  <item>
    <title>Proposed deposit uptake monitor</title>
    <link>http://iplus.ukoln.ac.uk/usecase/proposed-deposit-uptake-monitor</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p&gt;This use case outlines potential user requirements and technical development considerations for a proposed deposit uptake monitoring tool, designed to track deposit rates of research publications into Institutional Repositories (IRs). This proposed tool would be designed to distinguish between automated and manual deposit procedures, with capability of reporting the rate of manually ingested deposits by authors or supporting services versus the rate of automated (RJ Broker) deposits via machine-to-machine transfers.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Mon, 05 Nov 2012 15:39:47 +0000</pubDate>
 <dc:creator>admin</dc:creator>
 <guid isPermaLink="false">71 at http://iplus.ukoln.ac.uk</guid>
  </item>
  <item>
    <title>Proposed metadata enhancement suite</title>
    <link>http://iplus.ukoln.ac.uk/usecase/proposed-metadata-enhancement-suite</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p&gt;This use case outlines potential user requirements and technical development considerations for a proposed suite of metadata enhancement tools, designed to support automated extraction of metadata useful for repository deposit management and reporting. The proposed metadata enhancement suite would focus on requirements of several stakeholders in the Research Information Management (RIM) arena, who have firmly expressed their perceived need for metadata enhancement in current RIM systems (both Open Access repositories and CRIS). &lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Mon, 05 Nov 2012 15:59:09 +0000</pubDate>
 <dc:creator>admin</dc:creator>
 <guid isPermaLink="false">72 at http://iplus.ukoln.ac.uk</guid>
  </item>
  </channel>
</rss>
