Missing Collection Export Attribute

[jamlung-ri]

Collections exports are not including the cascade logic in the References portion. I can see what concept or mapping was referenced, but not the part that says "cascade": "sourcetoconcepts".

Example exported reference from this collection from Staging:

{
            "expression": "/orgs/CIEL/sources/CIEL/concepts/163201/",
            "reference_type": "concepts",
            "id": 2566553,
            "last_resolved_at": "2022-08-05T14:59:35.384910Z",
            "uri": "/users/jamlung/collections/CIEL-Example-OCL/v3/references/2566553/",
            "uuid": "2566553",
            "include": true,
            "type": "CollectionReference"
        }

which resolved to 10 concepts and 9 mapping via the "sourcetoconcepts" cascade.

[snyaggarwal]

@jamlung-ri This is deployed on QA.
Will have to regenerate existing imports. We can create new collection version for this or can force a new export for the same version. Let me know.
New imports should work as expected.

[jamlung-ri]

Awesome, I tested this on an existing collection and was able to confirm that an existing export is missing the new attributes, but new exports have the following additional attributes:

• cascade
• code
• concepts
• created_at
• display
• filter
• mappings
• namespace
• resource_version
• system
• transform
• translation
• updated_at
• valueset
• version

I think this is good to push on to Staging and Production.

@snyaggarwal Can you put the endpoint(s) to force a new export for a version? I'm guessing it's these, both with empty bodies:
DELETE /users/{user}/collections/{collection}/{version}/export/
POST /users/{user}/collections/{collection}/{version}/export/

[snyaggarwal]

@jamlung-ri Thats correct

[snyaggarwal]

@jamlung-ri This is deployed on Staging and Production.