[
https://jira.duraspace.org/browse/DS-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22754#comment-22754
]
Mark Diggory commented on DS-1050:
----------------------------------
Scotts right, its already there...
Some elaboration about the output ORE
The detail about which Bitstream is ORIGINAL and which is TEXT and which is
LICENSE is already very well defined in the output of the example above...
<oreatom:triples>
<rdf:Description xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";
rdf:about="https://buleria.unileon.es/oai/metadata/handle/10612/793/ore.xml";>
<rdf:type rdf:resource="http://www.dspace.org/objectModel/DSpaceItem"/>
<dcterms:modified>2011-03-26T02:00:11.748+01:00</dcterms:modified>
</rdf:Description>
<rdf:Description xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";
rdf:about="https://buleria.unileon.es/xmlui/bitstream/handle/10612/793/1945333.pdf.txt?sequence=4";>
<rdf:type rdf:resource="http://www.dspace.org/objectModel/DSpaceBitstream"/>
<dcterms:description>TEXT</dcterms:description>
</rdf:Description>
<rdf:Description xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";
rdf:about="https://buleria.unileon.es/xmlui/bitstream/handle/10612/793/license.txt?sequence=3";>
<rdf:type rdf:resource="http://www.dspace.org/objectModel/DSpaceBitstream"/>
<dcterms:description>LICENSE</dcterms:description>
</rdf:Description>
<rdf:Description xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";
rdf:about="https://buleria.unileon.es/xmlui/bitstream/handle/10612/793/1945333.pdf?sequence=2";>
<rdf:type rdf:resource="http://www.dspace.org/objectModel/DSpaceBitstream"/>
<dcterms:description>ORIGINAL</dcterms:description>
</rdf:Description>
</oreatom:triples>
So you can create a processor that can operate to exclude those if you need to.
Albiet, The use of dcterms:description as the predicate is rather a poor
choice IMO, I would have expressed something that is more dspace specific
concerning the Aggregated Resource
The bundle should probably just either be
a.) an additional statement about the Aggregated Resource that is something like
<AR-URI> ds:bundle "ORIGINAL"
<AR-URI> ds:bundle "LICENSE"
<AR-URI> ds:bundle "TEXT"
b.) or if we want to allow the system to get more descriptive about what a
bundle is, express it as another resource
<BUNDLE-URI> dc:identifier "ORIGINAL'
<BUNDLE-URI> rdf:type <http://www.dspace.org/objectModel/DSpaceBundle"/>
and express the statement in the AR-URI as
<AR-URI> ds:bundle <BUNDLE-URI>
On top of this, we really need to get the community to get on the "same page"
about defining these types and making sure they are resolvable to actual RDFS
or OWL definitions... See for instance the work I did while at MIT.
http://purl.org/dspace/model
> ORE disseminator should only export bitstreams from the ORIGINAL bundle
> -----------------------------------------------------------------------
>
> Key: DS-1050
> URL: https://jira.duraspace.org/browse/DS-1050
> Project: DSpace
> Issue Type: Bug
> Components: OAI-PMH
> Reporter: Àlex Magaz Graça
>
> If a collection is harvested with references to bitstreams, the bitstreams
> used internally by DSpace are also linked in the files section of the
> harvested items. It's due to the ORE disseminator exporting bitstreams from
> all bundles in the item. For example, plain text version of PDFs, thumbnails,
> and license files are exported, although they aren't shown in JSPUI and XMLUI
> interfaces.
> Here is an example item when this problem occurs:
> https://buleria.unileon.es/oai/request?verb=GetRecord&metadataPrefix=ore&identifier=oai:buleria.unileon.es:10612/793
> In the output two links appear to files used internally by DSpace:
> [...]
> <atom:link [...]
> href="https://buleria.unileon.es/xmlui/bitstream/handle/10612/793/1945333.pdf.txt?sequence=4";
> title="1945333.pdf.txt" type="text/plain" length="61150"/>
> <atom:link [...]
> href="https://buleria.unileon.es/xmlui/bitstream/handle/10612/793/license.txt?sequence=3";
> title="license.txt" type="text/plain; charset=utf-8" length="1487"/>
> [...]
> When harvested, the item appears with 3 bitstream instead of the one shown in
> the source:
> https://buleria.unileon.es/handle/10612/793
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
