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

Support export of entitlements in current agreements for discovery systems

    XMLWordPrintable

Details

    • Medium < 5 days
    • Medium < 5 days
    • Bienenvolk
    • 86
    • This is a go-live requirement for GBV and Leipzig "ERM Only" implementations. It is essential for these institutions to be able to show what e-resources are available in their user-facing discovery systems
    • R5
    • R2
    • R4
    • R5
    • R5
    • R4
    • R1
    • R1
    • R1
    • R4
    • R1
    • R1
    • R4
    • R5

    Description

      Create export of entitlements which are part of "current" agreements. "current" defined by
      (Status = Active) AND (("Is Perpetual" == "Yes") OR (("agreement start date" =< today OR not-populated) && (today =< "agreement end date" OR not-populated))

      This applies to local KB only.

      Out of scope:

      • export of full (MARC-style) bibliographic descriptions

      TestRail: Results

        Attachments

          Issue Links

            is defined by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ERM-215 Export Agreement data as KBART

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ERM-265 Export Agreement data as JSON

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ERM-327 Export entitlements as JSON from single agreement

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ERM-328 Export entitlements as KBART from single agreement

            • TBD - To be determined
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. ERM-385 Export of Agreement content as JSON does not use custom coverage

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. ERM-386 Export of Agreement content as JSON does not use PCI coverage

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. ERM-387 Agreement content KBART export | correct coverage information

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Activity

              People

                ostephens Owen Stephens
                ostephens Owen Stephens
                Mark Deutsch Mark Deutsch
                Steve Osguthorpe Steve Osguthorpe
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases