Capturing properties on enumerable "sub-items"

[Stephen Brush]

Hi,

The scenario I'm exploring is that an Item will often contain multiple files and for each of these files we would like to capture some metadata related to the file.

One approach would be to capture everything (ie. multiple properties separated by a delimiter) in a single field, such local.file.metadata, and used the order field to differentiate between files.

Another approach could be to set up a configurable entity for each file with specific fields for each property we'd like to capture, though that adds some complexity and overhead to data entry.

Is there best practice/other methods for this sort of problem?

Steve

[Reed, Marianne A.]

What kinds of metadata are you hoping to capture, Stephen? 

 

-- Marianne

 

Marianne Reed (she/her/hers)

Digital Publishing & Repository Manager

Watson Library, Room 470-G

University of Kansas Libraries

mr...@ku.edu

785-864-8913

--
All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups "DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-communi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/b6037e9e-3df6-4609-83ec-49051cf1495en%40googlegroups.com.

[Stephen Brush]

In one case the Item would contain a collection of maps. Ideally each map would have a few properties associated with it, such as type, scale, projection, etc.

Steve