Versions Compared

Old Version 1

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 2

changes.mady.by.user Tim Donohue

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected helpdesk strategy docs

...

Property:

request.item.type

Example Value

request.item.type = all

Informational Note

This parameter manages who can file a request for an item. The parameter is optional. When it is empty or commented out, request a copy is disabled across the entire repository. When set to all, any user can file a request for a copy. When set to logged, only registered users can file a request for copy.

Property:

mail.helpdesk

Example Value

mail.helpdesk = foo@bar.com

Informational Note

In JSPUI, the email address assigned to this parameter will receive the emails both for granting or rejecting request a copy requests, as well as requests to change item policies. In XMLUI, the parameter will also receive these requests to change item policies. However, the actual requests for copy in XMLUI will initially be directed at the email address of the original submitter. When this email address can not be retrieved, the address in mail.helpdesk will be used as a fallback.

This parameter is optional. If it is empty or commented out, it will default to mail.admin.

WARNING: This setting is only utilized if the RequestItemHelpdeskStrategy bean is enabled in [dspace]/config/spring/api/requestitem.xml (see below)

Property:

request.item.helpdesk.override

Example Value

request.item.helpdesk.override = true

Informational Note

Should all Request Copy emails go to the mail.helpdesk instead of the item submitter? Default is false, which sends Item Requests to the item submitter.

WARNING: This setting is only utilized if the RequestItemHelpdeskStrategy bean is enabled in [dspace]/config/spring/api/requestitem.xml (see below)


 

Selecting Request a Copy strategy via Spring Configuration

...

The process that DSpace will uses to determine who is the recipient of the Item Request is configureable by Spring.configurable in this Spring file: [dspace]/config/spring/api/requestitem.xml

By default the the RequestItemMetadataStrategy is  is enabled, but falls back to the Item Submitter eperson's name and email. You can configure the the RequestItemMetadataStrategy to  to load the author's name and email address if you set that information into an item metadata field.  For example:

Code Block
<bean class="org.dspace.app.requestitem.RequestItemMetadataStrategy"

...


 id="org.dspace.app.requestitem.RequestItemAuthorExtractor">

...


 <!--

...


 Uncomment these properties if you want lookup in metadata the email and the name of the author to contact for request copy.

...


 If you don't configure that or if the requested item doesn't have these metadata the submitter data are used as fail over

...

...


 <property name="emailMetadata" value="schema.element.qualifier" />

...


 <property name="fullNameMatadata" value="schema.element.qualifier" />

...

...


 -->

...


 </bean>

 


Otherwise, if Another common request strategy is the use a single Helpdesk email address to receive all of these requests (see corresponding helpdesk configs in dspace.cfg above). If you wish to use the Helpdesk Strategy, you have to must first comment out the other RequestItemAuthorExtractordefault RequestItemMetadataStrategy,  bean and uncomment this bean:

Code Block
<!-- HelpDesk to instead get RequestItem emails-->
<bean class="org.dspace.app.requestitem.RequestItemHelpdeskStrategy"
        id="org.dspace.app.requestitem.RequestItemAuthorExtractor"></bean>

...