[
https://jira.duraspace.org/browse/DS-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22571#comment-22571
]
Richard Rodgers commented on DS-1027:
-------------------------------------
Hi Gareth:
There are various ways to use the REST API - and it sounds like you might have
taken a different path. Let me explain the rationale for the work we did. The
initial drop-down is not really a list of licenses (as the simple chooser might
give you), it is a list of what CC calls license 'classes' (accessed via
http://api.createcommons.org/rest/1.5/classes). When you have selected a class
(roughly a family of licenses), the UI will put up specific questions to allow
selection of one member of that class (in some classes there is only one
member, so there are no questions e.g. CC0) We felt that it was desirable to
make this a like a mini--click thru acknowledgement and *not* preselect any
given license. The UI puts up the language from the Web Service to allow the
chooser to understand the option space better. We thought there was some risk
of inadvertent mis-selection with a simple drop-down of all licenses. So to
answer your question, yes, it was deliberate (albeit slower) to have the 'Allow
Commercial' etc questions.
As to retirement of Sampling, you may very well be correct: all we are doing is
'passing through' what the API call gives us for license classes (this from the
1.5. API URL above):
<licenses>
<license id="publicdomain">Public Domain</license>
<license id="standard">Creative Commons</license>
<license id="recombo">Sampling</license>
<license id="zero">CC0</license>
<license id="mark">Public Domain Mark</license>
</licenses>
But you can, (as I observed above), filter this down for UI display.
Does this make sense?
Thanks,
Richard
> CC License selection view now supports non-CC licenses - misleading text
> ------------------------------------------------------------------------
>
> Key: DS-1027
> URL: https://jira.duraspace.org/browse/DS-1027
> Project: DSpace
> Issue Type: Bug
> Components: XMLUI
> Affects Versions: 1.8.0
> Reporter: Gareth Waller
> Assignee: Robin Taylor
> Fix For: 1.8.0
>
>
> The CC license step has now changed to support other license types. The
> wording on the step should therefore be changed:
> - the step name should not be CC License
> - the text "If you wish, you may add a Creative Commons License to your item.
> Creative Commons licenses govern what people who read your work may then do
> with it." should be re-worded to not specifically mention CC if other
> licenses are being supported in the pull down
> - CC0 is a CC license so it shouldn't have a separate entry in the pull down
> from Creative Commons
> - "No Creative Commons License" option should be re-named to "No License"
> On a side issue, are the other license types well known enough to be included
> in the default distribution? In particular "Sampling" and "Public Domain
> Mark"?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
