[
http://jira.dspace.org/jira/browse/DS-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10961#action_10961
]
Stuart Lewis commented on DS-426:
---------------------------------
[16:15] <stuartlewis> http://jira.dspace.org/jira/browse/DS-426 Item's
submission license accessible without beiing configured to be public
[16:16] <stuartlewis> Old bug? Leave for post 1.6?
[16:16] <lcs> it _is_ shown in teh xmlui, and has been since 1.5..
[16:16] <mdiggory> http://jira.dspace.org/jira/browse/DS-422 etc was never
actually used/run in [dspace-dir] it gets run during ant install in [dspace-src]
[16:17] <mdiggory> so having etc in [dspace-dir]/etc doesn't actually serve a
purpose unless we decide we want to recommend that should be where it is always
executed from
[16:18] <lcs> so the information in the license which "might conflict with
privacy laws" is the email address of the submitter, right? I think that is now
configurable; i was working on it with andrea a while ago.
[16:18] <richardrodgers> ok so mistaken report?
[16:18] <mdiggory> or more specifically where the sql files on fresh_install
are aquired from
[16:19] <stuartlewis> What shall we do with ds-422?
[16:19] <mdiggory> 426 .... take it out of XMLUI template +1 for fixing in 1.6
[16:19] <richardrodgers> Update issue with this explanation
[16:19] <stuartlewis> Sorry - yes, 426 (not 422!)
[16:19] <mdiggory> sorry, I'm now here for a bit
[16:20] <stuartlewis> Who shall we assign 426 to?
[16:20] <mdiggory> focusr on 426 first
[16:20] <lcs> oops, it looks like DS-217, the license work, got dropped on the
floor.
[16:21] <stuartlewis> Does 217 fix 426? (can it be marked as duplicate and
closed?)
[16:21] <lcs> they are related -- 217 allows you to prevent the confidential
info from getting into licenses. but it doesn't necessarily fix it.
[16:22] <jtrimble> <==has to leave. Nighty night all...
[16:22] <stuartlewis> Thanks Jeff. Bye.
[16:22] <mdiggory> no 426 is about exposing the Collection submission license
in the presentation of the collection view
[16:22] <richardrodgers> bye
[16:22] * jtrimble ([email protected]) Quit ("Leaving")
[16:22] <stuartlewis> Anyone happy for us to assign 426 to them?
[16:22] <mdiggory> it shows only if it has been customized... claudia brought
it up
[16:22] <lcs> d'oh, i thought it was in the Item, you're right..
[16:23] <mdiggory> hmm, wait this is stlightly different than that
[16:24] <mdiggory> this is about access rights on license bitstreams
[16:24] <lcs> nope again, ds-426 _is_ about the Item's deposit license.
[16:25] <caryn> so, if u can customize item license (as prescribed in 217),
does this solve it?
[16:25] <lcs> if we change the access so it is not public than we should remove
the links in the xmlui item page (full view at least has it).
[16:25] <mdiggory> thought this was... http://jira.dspace.org/jira/browse/DS-398
[16:26] <lcs> this is getting complicated enough that perhaps it ought to be
put off to the next release.
[16:26] <mdiggory> I want to caution that, we are now talking about individual
organization policies here, not neccessarily what the DSpace application should
be hardwired to do
[16:26] <mdiggory> we want to be cautious and support configurability
[16:26] <caryn> mdiggory: +1
[16:27] <caryn> for some, the license could be considered part of metadata,
which is typically openly available... (w/o confidential info, of course)
[16:27] <lcs> +1 mdiggory
[16:27] <stuartlewis> So to conclude: What (if anything) do we do for 1.6?
[16:28] <lcs> i would like to postpone it and combine it with DS-217 - already
drew the link in jira.
[16:28] <stuartlewis> OK - thanks.
[16:28] <caryn> +1 lcs - having a good sense of "requirements" would be useful
> Item's submission license accessible without beiing configured to be public
> ---------------------------------------------------------------------------
>
> Key: DS-426
> URL: http://jira.dspace.org/jira/browse/DS-426
> Project: DSpace 1.x
> Issue Type: Bug
> Components: JSPUI
> Affects Versions: 1.6.0
> Reporter: Claudia Jürgen
>
> The item's license derives it's rights during the submission process from the
> default settings of the collection.
> So on a collection with default item read set to anonymous the READ for the
> license.txt is set to anonymous.
> Per default the license is not shown in the item page, as it contains
> information which might conflict with privacy laws. Furthermore it is of
> little use for the end user, because it usually does not contain the terms of
> use.
> In the JSPUI it is possible to retrieve the license via the direct retrieve
> link regardless of the configuration settings.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
