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 On Thursday, December 22, 2022 at 12:03:10 PM UTC-5 Reed, Marianne A. wrote: > 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 > > [email protected] > > 785-864-8913 <(785)%20864-8913> > > > > *From:* [email protected] <[email protected]> *On > Behalf Of *Stephen Brush > *Sent:* Thursday, December 22, 2022 10:29 AM > *To:* DSpace Community <[email protected]> > *Subject:* [dspace-community] Capturing properties on enumerable > "sub-items" > > > > 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 > > > > -- > All messages to this mailing list should adhere to the Code of Conduct: > https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx > <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.lyrasis.org%2Fabout%2FPages%2FCode-of-Conduct.aspx&data=05%7C01%7Cmreed%40ku.edu%7C27788e68d8d64f3e341108dae439a5a4%7C3c176536afe643f5b96636feabbe3c1a%7C0%7C0%7C638073233492980321%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=eiOC0Y1QpOrpSGehC%2FoDYGtZQ3wkGALtagJzAYXey4E%3D&reserved=0> > --- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-community/b6037e9e-3df6-4609-83ec-49051cf1495en%40googlegroups.com > > <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Fmsgid%2Fdspace-community%2Fb6037e9e-3df6-4609-83ec-49051cf1495en%2540googlegroups.com%3Futm_medium%3Demail%26utm_source%3Dfooter&data=05%7C01%7Cmreed%40ku.edu%7C27788e68d8d64f3e341108dae439a5a4%7C3c176536afe643f5b96636feabbe3c1a%7C0%7C0%7C638073233492980321%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=DhoG2IcbdD6k6e9lc7kVYJtQ9WN3cSHfph15g%2FDaac4%3D&reserved=0> > . > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/79b08b88-9497-4f0d-81b1-475bba4e6927n%40googlegroups.com.
