Hi Mark,

I'm kind of rookie on Dspace, although I have some coding experience. 

My goal is to add a RDF storage part to the Dspace system, so users can hand in 
their original works as well as the RDF triples which reveals their 
relationships at the same time. Then, when users browsing the web pages, the 
RDF relationships can be shown in some way.

I noticed the two projects you referred to both work under the Dspace2.0. 
Although I find the https://wiki.duraspace.org/display/DSPACE/DSpace+2.0,  it 
turns out to be a bit too simple, maybe just for me. I found 2.0 is different 
from 1.x in many ways, so is it the same way to bulid and deploy it? I have 
read the 1.x manual, it is quite straight forward, so is there something like 
this on 2.0?

Alexander Cheng

Best wishes~
At 2010-11-16 04:24:02,"Mark Diggory" <[email protected]> wrote:
>Hello Alexander,
>
>The GSoC project led to a "StorageService" implementation that would
>map a "DSpace Entity" to a set RDF statments.  this system is
>pluggable and uses Tupelo as a configurable middleware between DSpace
>and other available triplestore solutions such as Sesame and Mulgara.
>
>https://wiki.duraspace.org/display/DSPACE/GSOC10+-+Storage+Service+Implementations+Based+on+Semantic+Content+Repository
>
>This work should be continued by someone to begin mapping the DSpace 1
>Object Model into DSpace 2 Entities / RDF Statements.  Something that
>was progressing in the another GSoC project on integrating Storage
>Services into DSpace 1.x
>
>https://wiki.duraspace.org/display/DSPACE/GSOC10+-+Backport+of+DSpace+2+Storage+Services+API+for+DSpace+1.x
>
>What still needs to happen is an implementation mapping Individual
>DSpace Item Metadata and Bitstreams to a set of DSpace Entities.  This
>was work done partially in the above GSoC project, but more from the
>standpoint of treating the DSpace 1.x datamodel as a "store" under the
>storage service.
>
>Interesting work projects now would involve using 2 or more Storage
>Providers (Legacy and Semantic Store or Fedora Store) and
>copying/moving the Legacy DSpace Items/Bitstreams from the Legacy
>Store to the Semantic Store and/or Fedora Stores.  This would show the
>community:
>
>1.) How migration from one storage solution to another can be
>accomplished via services.
>2.) What the mapping would look like for DSpace Item <-> DSpace Entity
><-> RDF Statements
>
>Another area in serious need is that of mapping together the DSpace
>Metadata Registry, RDF Ontologies for Semantic Repositories and
>Extended Content Models in Fedora.  This area of development will lead
>us to have a means for the Storage solution to inform the DSpace
>application on the following:
>
>a.) What Metadata fields can be "asserted" on a DSpace Item Entity
>b.) What Metadata fields can be "asserted" on a DSpace Bitstream Entity
>c.) What Bitstreams are required to be "asserted" on a DSpace Item Entity
>
>Extending this area of work will enable the DSpace/Fedora integration
>to see a clear path to fruition.
>
>One concern I have is that this will require some in-depth analysis of
>what is happening with DSpace Metadata Fields where developers have
>attached more detail than just <item> <predicate> "value"^^lang such
>as order, confidence and authority.  We need to know how to present
>this added detail more correctly in the DSpace 2.0 manner, meaning
>that details such as confidence and authority would be "reifications"
>asserted about a StorageProperty (analogous to a DSpace 1.x DCValue),
>and that rather than additional properties of a DCValue object for
>something like "confidence", this data would be stored in a separate
>statements asserted in a separate service.
>
>In a DSpace 2 Service Manager approach, such details would be stored
>within a separate service / store.  For instance there would be an
>AuthorityControlService that stored the details concerning confidence
>on any statement asserted in the MetadataStore rather than deviating
>from an ERM (Entity Relationship Model) to make a StorageProperty
>something that gets extended and made more complex than being just an
>RDF statement.
>
>I would be interested in hearing more about what your goals are for
>integrating a triple-store, is it more of "Linked Open Data" that your
>seeking to expose this level of detail? I'm glad to see someone out
>there is interested in continuing this effort moving forward and I'll
>be glad to mentor you where possible.
>
>Cheers,
>Mark
>
>
>2010/11/14 Alexander <[email protected]>:
>> Hi, I'm trying to integrate RDF storage into the Dspace system, so that our
>> department can store RDF triples into it and display the data with a
>> browser. Through browsing and searching, I understand that there are some
>> projects going on, like the GSOC reports, and I also found the sesame part
>> in the SVN. However, few materials as to the progress is found, so anyone
>> please catch me up? I don't want to do some repeated work.
>>
>> Alexander
>> GUCAS
>>
>> --
>> Best wishes~
>> ------------------------------------------------------------------------------
>> Centralized Desktop Delivery: Dell and VMware Reference Architecture
>> Simplifying enterprise desktop deployment and management using
>> Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
>> client virtualization framework. Read more!
>> http://p.sf.net/sfu/dell-eql-dev2dev
>> _______________________________________________
>> Dspace-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/dspace-devel
>>
>>
>
>
>
>-- 
>Mark R. Diggory
>@mire - www.atmire.com
>533 2nd Street - Encinitas, CA 92024 - USA
>Technologielaan 9 - 3001 Heverlee - Belgium


------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to