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

Cannot populate package lifecycleStatus when uploading JSON package

    XMLWordPrintable

Details

    • ERM Sprint 146, ERM Sprint 147
    • Bienenvolk
    • Nolana (R3 2022)
    • Implementation coding issue

    Description

      Overview:

      When uploading a JSON package via the local KB admin, I expect to be able to populate the lifecycleStatus when specifying it in the JSON. Currently this does not seem to populate the property as expected.

      Steps to Reproduce:

      1. Go to Local KB Admin
      2. Click Actions and choose New JSON import job
      3. Upload the file attached to this issue
      4. Save and close
      5. Once job completed, search for "simple_package_simple_title" in Agreements e-resources
      6. View package details
      7. See Status field (where the lifecycleStatus property is displayed) is empty
      8. View the package JSON returned for this page (via browser console) and see that the lifecycleStatus property not present

      Expected Results:

      Package lifecycleStatus property is populated from uploaded JSON (as "Current")

       

      simple_package_simple_title-2.json

      Sprint planning discussion

      Ingest service currently uses status instead of lifeCycleStatus

      https://github.com/folio-org/mod-agreements/blob/f0e4313dc8db9ccebd07dae5b6ed8f77eaa280ee/service/grails-app/services/org/olf/PackageIngestService.groovy#L130

      This should be updated to use lifeCycleStatus and the GOKb adapter updated to populate lifeCycleStatus instead of status

       

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                ostephens Owen Stephens
                ostephens Owen Stephens
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases