Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-1759

Agreements | Local KB | Support adding custom data to URLs for resources in Agreements

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Epic Link:
    • Development Team:
      ERM
    • Report Functional Area(s):
      Resource Access
    • Calculated Total Rank:
      15
    • PO Rank:
      35
    • PO Ranking Note:
      This is a blocker for implementers in Germany who wish to use Agreements to feed the Union Catalogue
    • Rank: Chalmers (Impl Aut 2019):
      R5
    • Rank: Chicago (MVP Sum 2020):
      R4
    • Rank: Cornell (Full Sum 2021):
      R5
    • Rank: Duke (Full Sum 2021):
      R5
    • Rank: 5Colleges (Full Jul 2021):
      R5
    • Rank: GBV (MVP Sum 2020):
      R1
    • Rank: Grand Valley (Full Sum 2021):
      R4
    • Rank: hbz (TBD):
      R4
    • Rank: Lehigh (MVP Summer 2020):
      R4
    • Rank: TAMU (MVP Jan 2021):
      R4
    • Rank: U of AL (MVP Oct 2020):
      R5

      Description

      Sometimes institutions need to be able to add custom data to URLs they use to access resources (or their patrons use to access resources). This can involve adding a prefix, suffix, or additional information in a specific part of an existing URL

      Examples
      Where institutions use reverse Proxy servers, in order for Patron's get the correct link it requires a prefix, and sometimes a suffix to be added to a resource URL to enable a proxy server to retrieve, and then serve up the resource to the user.
      e.g. instead of "http://example.org", the user would be directed to "http://proxy.org?url=http://example.org"

      In other scenarios a resource URL may need an institutional identifier provided by resource provider adding to the resource URL so that the user is directed to an appropriate interface by the provider
      e.g. instead of "http://example.org", the user might be directed to "http://instA.example.org" or "http://example.org/?code=instA" etc

      Business rules & constraints:
      This feature is for resources in the internal Agreements knowledgebase only. It is assumed that where resources are managed outside Agreements (e.g. in eHoldings) any localisation will be handled by the other application or external knowledgebase

      Use case examples: ~3 July 2020 | Related discussion

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                ostephens Owen Stephens
                Reporter:
                ostephens Owen Stephens
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases