Uploaded image for project: 'DSpace'
  1. DSpace
  2. DS-824

Request Copy function for XMLUI and JSPUI

    Details

    • Attachments:
      2
    • Comments:
      28
    • Documentation Status:
      Needed

      Description

      The University of Minho developed a patch that gives this functionality in JSPUI: https://wiki.duraspace.org/display/DSPACE/RequestCopy .

      In implementing it for the XMLUI, I would like to alter the functionality so that the process looks something like:
      a. User clicks on restricted item link
      b. System responds with current behavior, adding a link/button to request privs to view item
      c. Clicking link to request privs to view item sends e-mail to author of item: includes Yes or No options
      d. Clicking yes sends e-mail to User with link to view item
      e. Clicking on link creates 'ghost' group with read access to item, including associated bitstreams. (Probably time-limited; one month?)

      This process would improve on the original process of sending the bitstreams to the User via e-mail; large documents often exceed outgoing mail limits, or incoming mailbox size restrictions. However, it also presents possible problems in trying to bypass the authorization system.

      I'm just starting to trace paths into the guts of XMLUI, so the general process is still in flux. I'd welcome any input, particularly regarding how to temporarily grant viewing privs to the restricted bitstreams.

        Attachments

          Issue Links

            Activity

            Hide
            adan.roman Adan Roman added a comment -

            Hi
            mail.helpdesk was inherited from jspui version. Originally was receiving all mails: the item policy change request and the item copy request.
            In xmlui new version is only used to handle policy changes and the request item of items whose submitter email address can not be obtained.

            Show
            adan.roman Adan Roman added a comment - Hi mail.helpdesk was inherited from jspui version. Originally was receiving all mails: the item policy change request and the item copy request. In xmlui new version is only used to handle policy changes and the request item of items whose submitter email address can not be obtained.
            Hide
            bram Bram Luyten (@mire) added a comment -

            updated:
            https://wiki.duraspace.org/display/DSDOC4x/Request+a+Copy

            I'm not sure I fully understood mail.helpdesk, but I gave it a try:

            "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."

            can you confirm that this is correct?

            Show
            bram Bram Luyten (@mire) added a comment - updated: https://wiki.duraspace.org/display/DSDOC4x/Request+a+Copy I'm not sure I fully understood mail.helpdesk, but I gave it a try: "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." can you confirm that this is correct?
            Hide
            adan.roman Adan Roman added a comment -

            I see the code and JSPUI seems to work as the XMLUI version. It is working as you describe with one addition: we was a bit paranoid so if mail.helpdesk is not found mail.admin is used.

            Show
            adan.roman Adan Roman added a comment - I see the code and JSPUI seems to work as the XMLUI version. It is working as you describe with one addition: we was a bit paranoid so if mail.helpdesk is not found mail.admin is used.
            Hide
            bram Bram Luyten (@mire) added a comment -

            Adan, I added your comment about the fallback to mail.admin.

            With regards to JSPUI vs XMLUI, the text currently reads:

            "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."

            If you say the behavior is the same, should I change it to:

            "The email address assigned to this parameter will receive two types of automated emails. The first type is the actual requests for copy, in case the original submitter email address can not be retrieved. The second type are the request for a change in item policies, if the original submitter/author has applied for such changes at the end of the request a copy process. This parameter is optional. Mail.admin will be used as a fallback in case the parameter is commented out or empty."

            Show
            bram Bram Luyten (@mire) added a comment - Adan, I added your comment about the fallback to mail.admin. With regards to JSPUI vs XMLUI, the text currently reads: "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." If you say the behavior is the same, should I change it to: "The email address assigned to this parameter will receive two types of automated emails. The first type is the actual requests for copy, in case the original submitter email address can not be retrieved. The second type are the request for a change in item policies, if the original submitter/author has applied for such changes at the end of the request a copy process. This parameter is optional. Mail.admin will be used as a fallback in case the parameter is commented out or empty."
            Hide
            bram Bram Luyten (@mire) added a comment -

            marked this as closed. If the current description in the docs appears to be wrong or unclear, we can still fix it in a different ticket.

            Show
            bram Bram Luyten (@mire) added a comment - marked this as closed. If the current description in the docs appears to be wrong or unclear, we can still fix it in a different ticket.

              People

              • Assignee:
                helix84 Ivan Masár
                Reporter:
                bfreels Brian Freels-Stendel
              • Votes:
                7 Vote for this issue
                Watchers:
                12 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: