Title: Message Title
|
|
|
|
Hi Hilton,
This sounds like a misunderstanding in how the 3.x Embargo works.
I had essentially the same misunderstanding which I logged in DS-1709.
Essentially, the 3.x Embargo does not set "end dates". The User interface is slightly confusing in that what you are really setting is the *START DATE* for when the Item will become available in the system. This is what you see in your "embargo-2.png" screenshot above, that a Start Date has been set for each of those policies. Prior to that "start date", the Item is fully private (i.e. embargoed). But, once the start date passes, then the Item will receive the permissions specified by those policies.
For 4.0, Andrea Schweer has redesigned the Embargo UI to try and make it clearer how to set embargoes properly. There is a new UI screenshot attached to DS-1709 (and it's already been merged into the 4.0 XMLUI, it's just waiting on porting to the 4.0 JSPUI and then we plan to close that ticket)
I'm going to close this ticket as a duplicate of DS-1709, but please feel free to let us know if this is still unclear.
|
|
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
