OK.
I tried implementing this.
But I was hoping something like a linked file, that appears in the parent
item and clicking on this linked item (child item) will take me to that
item, or maybe open that child item in the browser itself.
*From,*
*Arunendra MB.*
On Wed, Apr 21, 2021 at 6:26 PM
The URI of the related item is one option for the metadata, or another
identifier that links the items.
Here's an example of an item that has many parts:
The *parent* item, https://abc.xxx.org/handle/999/12340 ,contains
dc.relation.hasparthttps://abc.xxx.org/handle/999/12341
I haven't used dc.relation earlier.
Although I understood what you mentioned, in theory, what do I actually put
against this metadata- the handle ID or URI of the other item?
Also, I saw there are two dc.relation- dc.relation.isPartof and
dc.relation.hasPartof-- what is the difference?
I tried to
Do you use dc.relation in your metadata? If so, you might create several
items, one for each bitstream that needs its own metadata, and use
dc.relation.haspart and/or ispartof to relate them. The dc.relation data
is a link to the related item(s). For some types of items we create a
"parent"
Is it possible to enter individual metadata for individual bitstream where
multiple such bitstreams belong to a single item?
Using Dspace 5.10
--
All messages to this mailing list should adhere to the Code of Conduct:
https://duraspace.org/about/policies/code-of-conduct/
---
You received this
