Hi Richard,
I tried your curation task code because of my needs that I mentioned in my
post here: Question about Creative Commons settings
<https://groups.google.com/d/msg/dspace-tech/-K3juGMPGgY/1I4eTLA5AQAJ>. It
is indeed adding the cc license bitstream but one thing I noticed is that
it is not populating/updating the dc.rights which should contain the CC
license name although the status of the task said "STATUS: Success, RESULT:
xxxxx/xxxx added name: 'Attribution-NonCommercial-ShareAlike 3.0 United
States' added license bitstream.
if (updateName) {
// assume that we always want to synchronize the name to the URI
// this means that if a name is present and different, replace it
String oldName = nameField.ccItemValue(item);
String newName = ccl.getLicenseName();
if (oldName == null || ! oldName.equals(newName)) {
if (oldName != null) {
nameField.removeItemValue(item, oldName);
resultSb.append(" removed name: '").append(oldName).append("'");
}
nameField.addItemValue(item, newName);
resultSb.append(" added name: '").append(newName).append("'");
}
}
Could this be the reason for this is that updating the license name from
your curation task is not applicable for DSpace 5x version?
Thanks in advance and regards,
euler
On Wednesday, August 26, 2015 at 10:22:48 PM UTC+8, Richard Rodgers wrote:
> Hi folks:
>
> Just to add to this thread, I think the best approach is to directly edit
> these related CC fields (or add/remove bitstreams) as seldom as possible,
> since it is too easy to introduce inconsistencies among them (e.g. the
> name doesn't match the URI, or the bitstream, etc).
>
> To address this need in a 'safer' way, I just put up some curation task
> code:
>
> https://github.com/richardrodgers/ctask/blob/master/general/src/main/java/org/dspace/ctask/general/CCLicenseLookup.java
>
> that does the following: it uses the license URI as the 'key' and then
> fetches the values (license Name, and license RDF) from CC and assigns
> them to the item. That way one can be assured of having a consistent set
> of values (2 metadata fields and a bitstream). In fact, I think
> the submission UI can be configured to only set the URI, so that you don't
> need to redo anything but that field, and leave the rest to the task.
>
> It's untested as yet, but since we might be needing something like this
> for local MIT 1.8 upgrade work, I thought I'd share early…
>
> Thanks,
>
> Richard R.
> On Jan 21, 2013, at 3:20 PM, Andrea Schweer wrote:
>
> Hi,
>
> On 22/01/13 02:11, helix84 wrote:
>
> Anyway, there's no direct support for adding a CC license in XMLUI or
>
> JSPUI that we know of AFTER the original submission. I also tried
>
> looking at how you can do it manually by editing bitstreams/metadata,
>
> but the fact that the bitstreams are stored in the CC-LICENSE bundle
>
> together with the fact that you can't add or remove bundles from the
>
> UIs means, that it can't be done at this moment.
>
>
> You can add to the CC-LICENSE bundle via edit bitstreams in XMLUI if you
> add the bundle name to xmlui.bundle.upload in dspace.cfg -- in fact,
> just un-commenting the default should do it:
> https://github.com/DSpace/DSpace/blob/master/dspace/config/dspace.cfg#L1749
>
> cheers,
> Andrea
>
> --
> Dr Andrea Schweer
> IRR Technical Specialist, ITS Information Systems
> The University of Waikato, Hamilton, New Zealand
>
>
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122412
> _______________________________________________
> DSpace-tech mailing list
> [email protected] <javascript:>
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
> List Etiquette:
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
>
>
--
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.
