Title: Message Title
|
|
|
|
I want to note her that the functionality architecture already make possible to implement different strategy to discover the recipient of the request a copy email. A strategy based on the item metadata is already implemented and available out-of-box, see
https://github.com/DSpace/DSpace/blob/master/dspace/config/spring/api/requestitem.xml#L25
I don't have checked if it is noted in the official documentation
I agree with Bram that this kind of information are related to the embargoed object and not the item but as such it should be stored as attribute of the bitstream not of the resourcepolicy (potentially you could have two resource policies one to grant immediate access to a special group one for the actual embargo).
|
|
|
|
|
|
|
A particular use case was reported by 2 different people during the DSpace 4 Roundup webinar (http://bit.ly/dspace4-roundup).
In cases where submission is delegated to a different person than the original author or rights holder, for example a librarian or secretary, this person may not be the right person to receive and approve the requests for copy. ...
|
|
|
|
------------------------------------------------------------------------------
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-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
