Hi Carolyn, I tried to answer this question in the ticket you are referring to:
https://github.com/DSpace/DSpace/issues/11808#issuecomment-4290059803 The example configuration for CC licenses in that ticket is configurable and you can decide which metadata field you'd like to store the values in. My hope is still that we will find a volunteer to help us provide an "out-of-the-box" configuration that makes it easier on everyone. This out-of-the-box configuration would likely use "dc.rights.uri" because that's the field we've traditionally used for this metadata. Tim On Tuesday, April 21, 2026 at 10:53:34 AM UTC-5 Carolyn Sullivan wrote: > With the transition away from using the CC API to select licenses via > DSpace, some folks have suggested using the out of box oaire dropdown > option. However, this puts the metadata in a different field > (oaire.license.condition vs, previously, dc.rights.uri or dc.rights). > > A few questions for folks then: > (1) Are there any benefits to switching to the oaire.license.condition -- > ie, for oaire harvests? Should we crosswalk our metadata if this is > expected format? > (2) Any problems with just making a creative commons dropdown option that > offers the same metadata fields for inputs as the API radio buttons picker > does? > > Thanks, > Carolyn. > -- All messages to this mailing list should adhere to the Code of Conduct: https://lyrasis.org/code-of-conduct/ --- 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 visit https://groups.google.com/d/msgid/dspace-community/37d3bc32-8152-45a5-9010-6278d323b51cn%40googlegroups.com.
