Title: Message Title
|
|
I think the problem is that as people come up with more strategies you are going to wind up calling getSubmitterOrHelpdeskEmailOrStrategy3OrStrategy4...OrStrategy69(). That seems to be what the injection of specific strategy classes was meant to avoid. I would suggest interposing a common strategy class between the detail strategy classes and the UIs. The common strategy is "if the detail strategy returns nothing useful, try submitter then helpdesk then admin." Then supply a HelpdeskOnlyStrategy class that returns the helpdesk address. Inject that detail strategy into the common strategy and you have the behavior you need, with centralized fallback code wrapping all detail strategies.
|
|
|
|
|
Some institutions want the DSpace admininistrator or DSpace helpdesk to receive all Request Copy emails instead of the emails going to the original submitter. The Request copy has two config options right now: request.item.type = all mail.helpdesk = dsp...@myu.edu This pull request will add a new config option to allow the override.
|
|
|
|
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel