Details
-
Bug
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
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:
- Go to Local KB Admin
- Click Actions and choose New JSON import job
- Upload the file attached to this issue
- Save and close
- Once job completed, search for "simple_package_simple_title" in Agreements e-resources
- View package details
- See Status field (where the lifecycleStatus property is displayed) is empty
- 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
This should be updated to use lifeCycleStatus and the GOKb adapter updated to populate lifeCycleStatus instead of status