Hi everyone,
We’ve been facing an issue with the Creative Commons license step in DSpace 8 and wanted to share the full context in case anyone has experienced the same. Here’s what we’ve done so far: - Enabled the <step id="cclicense"/> in the submission definition for our collection. - Confirmed the collection is correctly mapped via <name-map> to the submission definition that includes the CC license step. - Configured all cc.* properties in dspace.cfg exactly as recommended, using https://api.creativecommons.org/rest/1.5 for cc.api.rooturl, no classfilter, and an empty cc.license.jurisdiction. - Restarted the backend after every change. - During submission, the CC license step appears in the UI, but the dropdown is empty (no licenses to select). - Checked dspace.log with DEBUG enabled for org.dspace.license and org.dspace.app.rest, but there are no errors or warnings logged — it’s completely silent. - The server has internet access, and a direct curl to the Creative Commons API returns results successfully. Given all this, it seems the configuration is correct, but the system is still not retrieving any licenses. Has anyone encountered this behavior in DSpace 7.x or 8.x? Were you able to find a workaround or solution? Thanks in advance for any insight you can share. -- 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 Technical Support" 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-tech/a4ca1d0c-3e8d-4a65-b672-d2a3fc0e1a99n%40googlegroups.com.
