Hi Robin,
I was recently playing with this module myself -- there are two modules you
need to build, dspace-rdf and dspace-xmlui-rdf-aspect.
You can download the source from scm.dspace.org/svn/repo/modules, or simply add
them ass dependencies to your XMLUI overlay in
[dspace-src]/dspace/modules/xmlui/pom.xml, like this:
<dependency>
<groupId>org.dspace</groupId>
<artifactId>dspace-xmlui-rdf-aspect</artifactId>
<version>1.5.1-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.dspace</groupId>
<artifactId>dspace-rdf</artifactId>
<version>1.5.2-SNAPSHOT</version>
</dependency>
In my case, I also needed to add the following to my sitemap, in the
appropriate pipelines (put the generator with the other generators, and the
match just underneath the existing METS metadata match):
<map:generator name="DSpaceObjectRDFGenerator"
src="org.dspace.app.xmlui.rdf.DSpaceObjectRDFGenerator"/>
<map:match pattern="metadata/handle/*/*/rdf.xml">
<map:generate type="DSpaceObjectRDFGenerator">
<map:parameter name="handle" value="{1}/{2}" />
</map:generate>
<map:serialize type="xml" />
</map:match>
Note that the code has changed a little bit since that email you're
referencing.. containers don't list the records they contain, like the RDF
generated on MIT's Dspace does. Best that I just quote Mark:
[quote]
"I abandoned describing DSpace Communities and Collections as ORE Aggregations
for two reasons.
1.) ORE Aggregations are supposed to be a bit "finite" in nature and are not
very good for describing growing/changing collections.
2.) Describing a DSpace Collection in ORE doesn't map very well when you go to
represent it as an Atom Entry. I realized this about the time that they
switched from describing ORE Aggregations as Atom Feeds and instead started
using Atom Entries.
Thus, when I create the dspace-rdf generator, I excluded ORE in the
representation of Communities and Collections. If I ever got the Atom
representation completed, they would be Atom Feeds containing Items as Atom
Entries, not too dissimilar to what is provided in DSpace 1.x today."
[/quote]
So, the short answer to your question is that it doesn't need to find its way
into any specific version, because it's a good example of a module that you can
tell DSpace to include with your next build, no manual downloading, no patching
your existing source. Maven does it all for you.
Cheers,
Kim.
> -----Original Message-----
> From: Robin Taylor [mailto:[email protected]]
> Sent: Thursday, 17 September 2009 11:35 p.m.
> To: [email protected]
> Subject: [Dspace-devel] FW: Getting ahead of the ORE "ball" in dspace
> 1.5 ...
>
> Apologies for the scatter gun approach, I was looking for an up to date
> email address for Mark Diggory but couldn't find one. I was wondering
> if this work ultimately made its way into 1.5.x ?
>
> Cheers, Robin.
>
>
>
> Robin Taylor
> Main Library
> University of Edinburgh
> Tel. 0131 6513808
>
> --
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
>
>
> -----Original Message-----
> From: [email protected] [mailto:dspace-devel-
> [email protected]] On Behalf Of Mark Diggory
> Sent: 24 March 2008 21:44
> To: DSpace Developer List; Michele Kimpton
> Subject: [Dspace-devel] Getting ahead of the ORE "ball" in dspace
> 1.5 ...
>
> Developers,
>
> (I originally sent this email to the commiters list, but think that it
> should be more openly discussed... so I am reposting here)
>
> I've been working hard for the last month on a project for dsp...@mit
> that you may find very complementary to the roll RichardJ has proposed
> for ORE in Sword. I'd like to introduce you to an ORE and Semantic Web
> enabled DSpace test server I've constructed using a SAX driven RDF
> serialization pipeline in Cocoon.
>
> http://dspace-test.mit.edu
>
> If you have a Firefox /RDF Browser Addon (http://www.w3.org/2005/ajar/
> tab) you can view the RDF at the same URI as the Content... Likewise,
> to view it in a regular browser, I've exposed it on secondary URI.
>
> Site:
> http://dspace-test.mit.edu
> http://dspace-test.mit.edu/rdf
>
> Community:
> http://dspace-test.mit.edu/handle/1721.1/33970
> http://dspace-test.mit.edu/rdf/1721.1/33970
>
> Collection:
> http://dspace-test.mit.edu/handle/1721.1/33972
> http://dspace-test.mit.edu/rdf/1721.1/33972
>
> Item:
> http://dspace-test.mit.edu/handle/1721.1/35257
> http://dspace-test.mit.edu/rdf/1721.1/35257
>
>
> the point is that ORE/RDF can be generated lightly and we can use
> cocoon to expose it in a way that is quite complementary to the rest of
> the User interface. The RDFizer is all SAX based and independent of the
> XMLUI, so it can be reused in JSPUI and OAI if we so choose.
> I've made an AddOn Aspect for DSpace XML-UI that includes this RDF
> capability into the rendering as described above... the only
> significant limitation as an "addon" is that it requires customization
> of the default sitemap in XMLUI to create new pipeline, matchers and
> serializers for the RDF Generator.
>
> I plan to include this functionality into dsp...@mit around the same
> time that DSpace 1.5.0 is released.
>
> -----
> Note: I've reworded my proposal since it was posted in the commiters
> list because we are actually about to cut 1.5.0 shortly and its almost
> unanimous in the response to this subject in the commiters list that we
> do not want to delay this release any longer...
> -----
> I'd like to propose the idea that we may actually want to put this in
> place in 1.5-SNAPSHOT after the 1.5.0 release to lay a foundation for
> DSpace's adoption of ORE. Having it available in the code-base planned
> for 1.5.1 means that we can have sites out in the wild after our 1.5.1
> release and we can make enhancements to the ORE/RDF
> generation in the maintenance release branch of 1.5.x. This would
> also really showcase DSpace as an adopter of both ORE and Semantic Web
> tooling.
>
> I really see an opportunity here, if for instance we can show that ORE
> exposed via the XMLUI can be handed to Sword (and elsewhere) to
> initialize the ingest/replication process of DSpace content... I think
> that will spark even more excitement around the DSpace Community and
> situate us at the forefront in the adoption of ORE...
> what are your thoughts?
>
> Cheers,
> Mark
>
> ~~~~~~~~~~~~~
> Mark R. Diggory - DSpace Developer and Systems Manager MIT Libraries,
> Systems and Technology Services Massachusetts Institute of Technology
>
> -----------------------------------------------------------------------
> --
> This SF.net email is sponsored by: Microsoft Defy all challenges.
> Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Dspace-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-devel
>
>
>
> -----------------------------------------------------------------------
> -------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart
> your
> developing skills, take BlackBerry mobile applications to market and
> stay
> ahead of the curve. Join us from November 9-12, 2009. Register
> now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Dspace-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-devel
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
