Enable viewing of draft codelists in the opencodecounts tool

Why are we doing this?

We are considering linking to the OpenCodeCounts web app in order to help codelist authors understand usage of codes in building their codelists.

This tool's opencodelists module calls the OpenCodelists API endpoint which lists a user/organisation's codelists and checks the user-provided codelist+version slug against the returned data to ensure the codelist ID's correctness, then uses the codelist version's download url to get the csv data.

Currently this doesn't work with draft codelists as their download URL redirects to the builder.

In order to make OpenCodeCounts a more useful tool for codelist development we should consider how draft codelists might be made available for this tool.

This may involve working with the research team to make changes to OpenCodeCounts.

We also need to consider what the behaviour should be regarding code statuses not permitted in In Review or Published codelists. Do our users want to see usage for all potential codes in a codelist or just the ones they've included.

As this will probably end up including some extra logic for draft codelists we should consider creating a dedicated API endpoint for the OpenCodeCounts tool as not to modify the established existing behaviour of the csv download endpoint.

How will we know when it's done?

Draft codelists will be usable in the OpenCodeCounts code usage tool.

What are we doing?

...

Defining delivery tasks guidance