Hello William, we at stadtteilgeschichten.net a running DSpace 1.4.2. We updated to this version only recently and wont be ready for DSpace 1.5 any time soon.
Having said that, the CreativeCommons submission issue has popped up at our site exactly the time when it was fixed for the rest of you. Our users are so patient that they expected this to be their fault and did not inform me within the last three weeks. So I stumbled upon it only this week and it took me some time to find out the relation to the issue discussed here. The last last submission featuring a CC license was submitted around noon MESZ August, 3rd. The first submission where it was impossible to choose the CC License was done in the afternoon MESZ August, 5th. What is happening is, that the value of the URL para- meter license_url does not get appended to the exit_url parameter by creativecommons any longer. THE DETAILS There was a change in how DSpace handles this parameter between DSpace 1.4 and DSpace 1.5, probably due to the Configurable Submission Process introduced with Revsision 2081. The change is in the jsp/submit/creative-commons.jsp around lines 70-80. There is a URL parameter defined as: String exitURL = baseURL + "/submit/cc-license.jsp? license_url=[license_url]"; where the license_url is not set in DSpace 1.4. In DSpace 1.5, license_url gets set already at that point and gets passed in to creativecommons later on: ... licenseURL = CreativeCommons.getLicenseURL(subInfo.getSubmissionItem().getItem()); There line including the creativecommons page stays unchanged between both releases: <iframe src="http://creativecommons.org/license/?partner=dspace&stylesheet= <%= java.net.URLEncoder.encode(ssURL) %>&exit_url=<%= java.net.URLEncoder.encode(exitURL) %>" width="100%" height="540"><fmt:message key="jsp.submit.creative-commons.info3"/> </iframe> Now, this is happening in DSpace 1.4 at our site. During submit process, when entering the CC Licensing page, Dspace displays this URL in the iframe: http://creativecommons.org/license/?partner=dspace&stylesheet=http://stadtteilgeschichten.net/submit/creative-commons.css&exit_url=http://stadtteilgeschichten.net/submit/cc-license.jsp ?license_url= Please note, that license_url comes without value. The licensing page of creativecommons gets displayed in german which reflects the browser settings. We choose our license settings and hit the button "Select a License". The resulting page is in english. The Adress field contains these parameters: http://creativecommons.org/choose/results-one?lang=en&language=en&referrer=&partner=dspace&exit_url=http%253A%252F%252Fstadtteilgeschichten.net%252Fsubmit%252Fcc-license.jsp%253Flicense_url%253D&stylesheet=http%253A%252F%252Fstadtteilgeschichten.net%252Fsubmit%252Fcreative-commons.css&partner_icon_url=&field_commercial=y&field_derivatives=y In other words, the license_url does not get completed. The proceed link within the page points to http://stadtteilgeschichten.net/submit/cc-license.jsp?license_url= and does not contain a value as well. If completing the request for the last page, adding the value for license_url manually, then the address field and the proceed link contain the required value: http://creativecommons.org/choose/results-one?partner=dspace&exit_url=http://stadtteilgeschichten.net/submit/cc-license.jsp ?license_url=http://creativecommons.org/licenses/by/3.0/ Probably, Creative Commons has removed this functionality during their rework because it seemed to them that it is not neede any longer. I know that it is much to request to keep such a function for a single installation, but I guess that there are other out there who still use it and just did not notice until now. I cant judge how much work it is to include this functionality again on their side. IMPACT For us, this is a major issue. We are a not for profit organization and we got funded by our government to complete a digitalisation project during this year and work together with external partners for that reason. We have treaties with these partners where we have taken responsibility to provide accessibility of the platform, id est DSpace during the whole project time. Part of the treaty is also, that these partners publish their materials under CC License. Now, we give them reason, not to fulfill their responsibilities and in turn we would have to pay back the money we got to complete this project. Besides, this project has already revealed wonderful res- sources of social history. You probably know the name of St. Pauli. Sources of this archive would not be published without this project: <http://stadtteilgeschichten.net/handle/2339/1032/browse-date?order=oldestfirst > We decided not to apply major changes to the platform during project runtime, id est in 2009 and we would not have the ressources to do so besides the project. I could not figure out a simple way to apply the Configurable Submission Process patches from 1.5 to the 1.4 sources without breaking a lot of other stuff. So I guess, my only choice is to switch to DSpace 1.5 if this cant be fixed. While you and the creative commons people dont need to be concerned about our situation, we would really appreciate if you would. Should I contact somebody at Creative Commons directly? Should I write a bug report o ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech