Document IDs in List Incorrect

[brian-ruf-ezd]

trafficstars

For any GET /[model-name] that provides a list of OSCAL content, the JSON list includes a document-ids field. That field incorrectly has two layers of document-ids. It should only have one.

For example, the list OpenAPI spec shows:

        "document-ids": [
          {
            "document-id": {
              "scheme": "BoB0wJwhtaQULoNYt0VJMJVw1AX7SkuNQZTOOGcTbVyrWzCOaJleyp9+oDZ:%RRx/#h8mA4aFnX:3S&n1yWZ34Mv};&zXsfVEL]C\\uMJId~zw>ncOdr$} -B%NN@W+88pM\"#a",
              "identifier": "string"
            }
          }
        ]

It should show:

        "document-ids": [
          {
              "scheme": "BoB0wJwhtaQULoNYt0VJMJVw1AX7SkuNQZTOOGcTbVyrWzCOaJleyp9+oDZ:%RRx/#h8mA4aFnX:3S&n1yWZ34Mv};&zXsfVEL]C\\uMJId~zw>ncOdr$} -B%NN@W+88pM\"#a",
              "identifier": "string"
          }
        ]

[brian-ruf-ezd]

May be a leftover artifact form when we were allowing both XML and JSON returns. Now that we are only offering JSON returns, this should be flattened.

[brian-ruf-ezd]

Made good progress on the collection of issues. This one will be addressed in sprint 68.