Hello, I have a bunch of questions regarding the CC License Step during submission. We use XMLUI and DSpace 1.8.2. I browsed the Git Repository and got the impression that there havent been so many commits in this area since then, so I hope I dont ask questions that are solved meanwhile.
Our goal is to make it mandatory for users of our repository to publish under either CC-BY-SA or CC-BY-ND. The task includes to contact all users who have published their items in our repository in the past and get their consent to change the license on all existing items. These license types are widely accepted by aggregators, who harvest us already or will do so in the future if we can guarantee these license terms for all our content. We welcome the gain in visibility provided by aggregators and see this as a cause to put a change into effect right now that we agree to anyway. I could imagine changing and limiting licensing options might be a task that others running a DSpace repository are faced with as well sooner or later. Limiting the number of choices opens a chance to further simplify the User Interface. Best case would be to have checkboxes for CC-License and deposit license on the bottom of the review step of the submission process, but I guess that requires more then just a little bit of configuration. At least, Id like to understand why there remain some strings that cant be localized in the CC License step. When thinking about how to fix the licenses for existing items, I stumbled across the option cc.submit.addbistream in dspace.cfg which defaults to true. It attaches a small file containing a desription of the license chosen in RDF format. When changing the license, this file requires extra work to keep it in sync with the dc.rights and dc.rights.uri fields, so I thought about what it might be good for. If keeping it offers any advantage, I will deal with that, but I am curious what it was meant for in the beginning. I cant see, that there is made use of it e.g. during OAI-export. Currently I tend to disable this feature for all future ingests as well. Please stop me from doing so if I overlook something important. After reading both CCLicenseStep.java files in either dspace-api and dspace-xmlui and playing with the creative commons api manually (http://api.creativecommons.org/docs/readme_15.html) I dont yet understand how they work their magic. When somebody chooses to ad a CC license, currently the item gets a field dc.rights.uri, filled with a value like "http://creativecommons.org/licenses/by/3.0/de/";. We use jurisdiction german, but I wonder why we get specifically version 3.0. International version 4.0 is current, but not yet translated to german. Can I expect the system to switch to the most current version within my jurisdiction for future items as soon as they get online without me configuring anything? The CC License page during the submission process offers a drop menu set to "Select or modify your license ..." as a default. May I set the option "Creative Commons" (standard) as a default instead? Or does its existence in the menue depend on the answer of <http://api.creativecommons.org/rest/1.5/?locale=de>? (besides cc.license.classfilter in dspace.cfg). Why do the following questions "Allow commercial uses of your work?" and "Allow modifications of your work?" get displayed in english including there options in the german interface? I want to translate them, but I dont know where this should be done. Also, I want to set a default option for the answers. Third, I would like to remove the question regarding commercial use completely and maybe limit the choice regarding modifications to "ShareAlike" or "No". I could not find these questions in the messages.xml nor anywhere else in the source hardcoded. Tinkering with <http://api.creativecommons.org/rest/1.5/> supplying various arguments I could not force the creativecommons.org server to supply these messages. In reading the source of CCLicenseStep.java, I found variables "commercial_chooser" and "derivatives_chooser" which probably describe just these two questions and there answering options, but I did not understand where they are read from. My catalogue of questions has grown rather large already. Thats why I stop here. Only one thing regarding the deposit license Id like to mention. It gets customized for each item by prepending a line starting with "License granted by ". This message is hardcoded in LicenseUtils.java and can not be translated using the messages.xml system. Bye, Christian ------------------------------------------------------------------------------ Time is money. Stop wasting it! Get your web API in 5 minutes. www.restlet.com/download http://p.sf.net/sfu/restlet _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
