Uploaded image for project: 'ERM Platform'
  1. ERM Platform
  2. ERM-387

Agreement content KBART export | correct coverage information

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      ERM Sprint 70
    • Development Team:
      Bienenvolk

      Description

      On export of an Agreement content as KBART (e.g. using https://folio-snapshot-okapi.aws.indexdata.com/erm/sas/f007a2f3-6cb0-48bf-8321-91e0f02dd126/export/kbart) the export does not populate:

      • num_first_vol_online
      • num_first_issue_online
      • num_last_vol_online
      • num_last_issue_online

      These should be populated based on the PCI or custom coverage (as appropriate) startVolume, startIssue,endVolume,endIssue respectively.

      The KBART coverage also currently does not choose the correct coverage for the PCI (PCI or Custom coverage) on export, with the current situation that multiple lines are output in KBART for different coverage statements - PCI, Custom, PTI

      Only applies to KBART export.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                jaf30@cornell.edu John Allen Fereira
                Reporter:
                ostephens Owen Stephens
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases