Support non-PQS fields for create/edit CCE catalog via CSV

Description

Once https://openlmis.atlassian.net/browse/OLMIS-2604#icft=OLMIS-2604 is finished, this ticket handles additional data fields (ones not covered by PQS) needed by the system to keep track of CCE data.

Included fields:

  • Active / Inactive (archived)

  • from PQS catalog? (Y/N)

Acceptance criteria

  • Update CCE domain model for additional fields

  • Update RAML JSON schema for additional fields

  • Update CSV template fields with additional headers

  • Update CSV upload documentation for CCE with how to fill out additional fields

  • Validate that the two fields boolean values true/false only - others cause a validation error TBD: acceptable values

  • Handle empty fields as TBD

QAlity Plus - Test Management

Checklists

Activity

Show:
Mary Jo Kochendorfer
August 8, 2017 at 11:55 PM

Moving to dead because it is already covered in https://openlmis.atlassian.net/browse/OLMIS-2604#icft=OLMIS-2604

Chongsun Ahn
July 17, 2017 at 9:31 PM

I think these fields are generic enough and useful to multiple implementations that we should just have them as fields, so NOT extra data. We should make them both required and and default queries on the catalog should filter and return only active ones.

Rachel Powers
July 17, 2017 at 8:07 PM

Do you have any thoughts about Pawel's questions? Regarding the Q about fields other than the two mentioned I can email the CCE expert group.

Paweł Gesek
July 13, 2017 at 12:08 PM
(edited)

Question: Should 0/1 be treated as true/false for these fields? Should empty fields translate to false or should they be mandatory?

Paweł Gesek
July 13, 2017 at 12:07 PM

Question (actually question number 1): should we support fields other then the two mentioned?

Won't Fix
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Story Points

Priority

Time Assistant

Created May 30, 2017 at 1:57 AM
Updated February 8, 2023 at 1:29 PM
Resolved August 8, 2017 at 11:55 PM