Creative Commons License Selection - Metadata Fields

[Carolyn Sullivan]

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.

[DSpace Community]

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