Thanks for all the responses, and insight thus far.
My thinking about the problem space of nested metadata, is that that is
trying to solve the problem of metadata about metadata about an item.
Item/1234 = Author = [Peter Dietz, Developer, Longsight, Brown eyes, ...]
What we've been doing is
Hi Peter,
I think you may not be too far off with that approach.
However, one key thing that gets missed - you provide an example where
dc.contributor.author that captures rich metadata. Which we shouldn't be
doing - dublin core is meant to be simple, and simple data is what we
should be
On Wed, Jul 29, 2015 at 04:06:19PM -0400, Peter Dietz wrote:
Has anyone stored nested / rich metadata in DSpace?
An example I'm thinking of is for storing richer amounts of metadata for an
object. For example:
- Author
- first-name: Peter
- last-name: Dietz
-
Hi Peter,
The new SOLR core for authority indexes supports that kind of JSON
structure, although has to be linked, via an autorithy key, with a
metadata field...
We are using it for storing name variations, Authors ids, bio and some
others fields
best luck
Emilio
El 29/07/2015 a las
Peter,
Just some brief feedback, this sounds very much like a DCMI Encoding
Scheme. The goal of which is to express the structure and/or source of the
value of a DC metadata field without needing to create extensive nesting.
http://wiki.dublincore.org/index.php/Glossary/Encoding_Scheme
Cheers,
Hi All,
Has anyone stored nested / rich metadata in DSpace?
An example I'm thinking of is for storing richer amounts of metadata for an
object. For example:
- Author
- first-name: Peter
- last-name: Dietz
- name-as-it-appears: Peter Dietz
- institution: Longsight
Hi,
On 30/07/15 08:06, Peter Dietz wrote:
Has anyone stored nested / rich metadata in DSpace?
In a freshwater quality data repository I've helped develop
(http://lernzdb.its.waikato.ac.nz), we're storing rich metadata in an
XML bitstream. This bitstream is considered the authoritative source
7 matches
Mail list logo
