[
https://jira.duraspace.org/browse/DS-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22872#comment-22872
]
Àlex Magaz Graça commented on DS-1055:
--------------------------------------
Thanks for your clarification about the bundles, I hadn't thought about other
possible uses they could have.
About the way to fix the problem, I'm not sure I understand you. As I might not
have explained my self very well in the bug report I'll try be more detailed:
Right now DSpace gives you three options to harvest from another repository:
1. Harvest metadata only.
2. Harvest metadata and references to bitstreams (requires ORE support).
3. Harvest metadata and bitstreams (requires ORE support).
The one I'm referring in this bug report is the second one. There's no problem
with the first as it only harvest metadata, and I've just tested the third one
and it works just fine, each bitstream is put in its corresponding bundle.
In the second case, in a harvested item, there's only the 'ORE' bundle with an
ORE.xml file from which the bitstreams links are extracted when displayed.
Then, are you suggesting the harvester should add a bitstream for each one on
the source repository and store a link into it?
> References to bitstreams not from the 'ORIGINAL' bundle are shown in
> harvested items
> ------------------------------------------------------------------------------------
>
> Key: DS-1055
> URL: https://jira.duraspace.org/browse/DS-1055
> Project: DSpace
> Issue Type: Bug
> Components: XMLUI
> Reporter: Àlex Magaz Graça
> Attachments: only-show-ORIGINAL-bitstreams.patch
>
>
> When harvesting a collection with references to bitstreams (ORE) from another
> DSpace instance, all the bitstreams from the source repository are shown
> instead of only the ones in the 'ORIGINAL' bundle. For example, if a
> 'document.pdf' is shown in the item of the source repository, in the
> harvested item 'document.pdf.txt' (THUMBNAIL bundle) and 'license.txt'
> (LICENSE bundle) are also shown. It should look at the <dcterms:description>
> value in the RDFs statements of the corresponding bitstream to filter out the
> other bundles:
> [...]
> <atom:link [...]
> href="https://buleria.unileon.es/xmlui/bitstream/handle/10612/793/1945333.pdf.txt?sequence=4";
> title="1945333.pdf.txt" [...]/>
> [...]
> <rdf:Description
> 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>
> [...]
> snippet taken from here:
> https://buleria.unileon.es/oai/request?verb=GetRecord&metadataPrefix=ore&identifier=oai:buleria.unileon.es:10612/793
> I think the code to be fixed is in
> dspace-xmlui/dspace-xmlui-webapp/src/main/webapp/themes/dri2xhtml-alt/aspect/artifactbrowser/ORE.xsl
--
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
------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Ciosco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
