Dear All,

One of the repository I'm working on (DSpace 5.4 XMLUI) would like to 
implement Creative Commons license step in the submission process. Based 
from what I've read here: Configuring Creative Commons License 
<https://wiki.duraspace.org/display/DSDOC5x/Configuration+Reference#ConfigurationReference-ConfiguringCreativeCommonsLicense>,
 
the field dc.rights will be automatically populated by the Creative Commons 
license Name assuming that the cc.submit.setname is set to true. So for 
example if dc.rights.uri is 
http://creativecommons.org/licenses/by-nc-nd/3.0/igo/, the value for 
dc.rights would be *Attribution-NonCommercial-NoDerivs 3.0 IGO*. Is it 
possible to change the value of dc.rights such that instead of the lookup 
value *Attribution-NonCommercial-NoDerivs 3.0 IGO*, it would instead use *CC 
BY-NC-ND 3.0 IGO*? Example: 
https://openknowledge.worldbank.org/handle/10986/27237?show=full. I also 
noticed that the language attributes for dc.rights and dc.rights.uri were 
asterisks (*) and not the value of cc.license.locale. Also, I would also 
like to ask if it's possible to use the https version of the cc.license.uri? 
I changed my cc.api.rooturl to use https://api.creativecommons.org/rest/1.5 
but it is still assigning the http version. Lastly, since activating the CC 
license step only required that you uncomment Step 6 portion in 
item-submission.xml, is it possible to have these step require the 
submitter to enter the dc.rights.holder field or I can only do that (ie 
adding the dc.rights.holder field) in the Describe portion of the 
submission process?

Thanks in advance and best regards,
euler

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Reply via email to