Add feature to exclude retired concepts and/or mappings from exports

[paynejd]

This is especially pertinent for client applications that do not keep track of retired resources (such as OpenMRS for mappings). Note that separate cached exports would have to be created if supporting this.

[cassiemorgan11]

The addition of this feature would be incredible helpful. Editing the export after is cumbersome in general, but especially for large dictionaries.

[paynejd]

Discuss on future OCL Architecture call if we want to provide additional export options that apply a filter. Note that we could consider providing this functionality in the ocldev2 package as well to that this can be accomplished programmatically.

[rkorytkowski]

@snyaggarwal could you please point to a file in codebase where this change should be done to make it easier for new comers?

[snyaggarwal]

the method to export -- https://github.com/OpenConceptLab/oclapi2/blob/41cf8ad5cdc81e565d8db9e6ab7a345b130dd063/core/common/utils.py#L193

concept queryset should change here
mapping queryset should change here

[PatrickCmd]

As @snyaggarwal pointed to where the querysets should change, so I think they should be a filter like this

concepts_qs = version.concepts.filter(retired=False)
mappings_qs = version.mappings.filter(retired=False)

[snyaggarwal]

Yes @PatrickCmd you are right. The only other thing is, it should be an optional feature. Users should be able to optionally ask to exclude retired concepts/mappings.

[PatrickCmd]

@snyaggarwal is this option to be passed as a parameter in the write_export_file function and if yes, is it boolean and what would be it's appropriate name.

[snyaggarwal]

@PatrickCmd We are expecting to make use of our existing parameter for this INCLUDE_RETIRED_PARAM from requests query params.