Hi Monika, On 1/10/2014 3:28 PM, Monika C. Mevenkamp wrote: > I recently started to work at Princeton University as Digital Repository > Programmer where I am working with their DataSpace/DSPACE instance, > version 1.8.2 using jspui. A couple years ago I was at Georgia tech > working with SMARTech. Lots has changed and I am trying to get up to > speed again. > > From reading DSpace 1.8 documentation I understand that CC_LICENSEs are > part of a items. They are meant to describe what a user can do with > bitstreams. As I understand the CC_LICENSE is defined when submitting > an item. It is either set to the default or to the license of the > containing collection. Setting > webui.licence_bundle.show = true > changes the ItemTag display a bit. It appears that only admin users can > then download bistreams.
A point of clarification here. There are two types of "licenses" supported by DSpace: 1. Deposit Licenses (stored in the LICENSE bundle in an Item). This *must* be accepted by submitters in order to complete a deposit/submission to DSpace. There is a default deposit license specified by DSpace. You can also define a different deposit license *per* Collection, as you see fit (this option is in the "Edit Collection" UI). 2. Creative Commons Licenses (stored in the CC_LICENSE bundle in an Item). These are disabled by default. They are *optional* during the deposit/submission process. If enabled, this license *must* be a valid Creative Commons License: https://creativecommons.org/licenses/ Therefore its role is only to define basic redistribution rights that the copyright owner allows to others. You CANNOT customize these licenses as they are defined by Creative Commons. > Stepping back: Our DSPACE instances has a community with collections > which contain senior theses documents. Access to these is supposed to be > restricted to University members and site visitors should be made *very > aware *of what they can and can not do with these files: aka read, > print, but do not share with outsiders. Unfortunately, as far as I'm aware, rights such as "printing" are not covered by Creative Commons licenses. You could add custom coding to DSpace in some way to allow for this, but by default there is no CC License that restricts printing or even sharing. > For access restriction I am envisioning using IPAuthentication. I > understand that I need to enter our specific values in > dspace/config/modules/authentication-ip.cfg file. I am envisioning a > stack, where first our custom authentication code is tried, then IP > Authentication, and then the Anonymous user is ‘authorized’. How do I > tie a pseudo user account to IP authentication ? IP ranges can be "mapped" to a DSpace internal Group. So, they cannot really be mapped to a "pseudo user", but *can* be mapped to a "pseudo group". See: https://wiki.duraspace.org/display/DSDOC4x/Authentication+Plugins#AuthenticationPlugins-IPAuthentication > We would like to make site users explicitly agree to our custom license > when they download a bitstream from a senior theses collection. Ideally > DSPACE should remember that agreement acceptance for a specified > duration. Looking at the code I came up with the following plan: > > * use collection’s CC_LICENSE to define the license agreement to be shown > * change BitstreamServlet:DSGet method such that > o if item’s collection is not listed in in > webui.confirm-license. collections setting do as before > o else: > + if session contains a time stamp for the given collection > that is within webui.confirm-license-aftermin do as before > + else redirect to /agreement with bitstream parameter > * add AgreemntServlet (is that what it would be - I am not much of JSP > developer) > o DSGet: display a custom jsp page that shows the agreement and a > ‘Cancel’, ‘Accept’ button, ‘Cancel’ just navigates back and > Accept triggers POST /agreement with bitstream param > o DSPost: sets agreement time stamp for community and redirects > to /bistream/…. > > > So now - in theory this seems not a huge project. In practice, as I said > I am not much of JSP/Servlet developer. How are redirects done for > example - I have no idea. Maybe instead, I should go ahead and try to > hack something up based in Javascript and cookies - which would involve > exposing the bitstream url in the html page. Since there would be no > changes server side a skilled user could peel that bitstream out of the > HTML and just go ahead and download. So not quite as good a solution. So, this sounds like a custom use of the CC_LICENSE bundle (not supported by default, obviously). To be honest, you may even want to create your own bundle for this purpose (e.g. "USAGE_LICENSE" bundle), as what you are suggesting does not really sound like a Creative Commons license. Beyond that, it sounds relatively reasonable. One thing to be aware of is that it will require some sort of customization to the Submission UI, if you want to provide users with a way to select which "Usage rights" they wish to allow. I'm not sure if anyone else out there has already built something similar. But, this idea may be interesting to others as well. - Tim ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ 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
