10787 search export as system values

[whatisgalen]

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Description of Change

This PR enables exported search results to be rendered as their "system values", i.e. the node value comes from
datatype.transform_export_values() instead of datatype.get_display_value(). For exmaple concepts would render as their uuids instead of preflabels. It has a minor addition to the UI as well.

Issues Solved

#10787

Checklist

• Unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Ticket Background

• Sponsored by: @scholiumtech
• Found by: @whatisgalen
• Tested by: @chiatt
• Designed by: @whatisgalen

Further comments

[chiatt]

This is a good start, but would be much better concept specific but rather apply to all datatypes. That would eliminate the need for datatype checking and allow for future and custom datatypes to control how data is exported.

The boolean variable could be 'Export System Value' and then in search_export the boolean would just determine whether 'get_display_value' or 'transform_export_values' is called.

[whatisgalen]

This is a good start, but would be much better concept specific but rather apply to all datatypes. That would eliminate the need for datatype checking and allow for future and custom datatypes to control how data is exported.

The boolean variable could be 'Export System Value' and then in search_export the boolean would just determine whether 'get_display_value' or 'transform_export_values' is called.

fix in latest

[whatisgalen]

FWIW coverage "failed" because of this delta:
Coverage decreased from 65.89301327398458% to 65.87992212023681%

[chiatt]

Looks good to me!

[chiatt]

Just a note - 'concept_export_value_type' is used here because that's the argument in both the domain and concept datatypes. Might be nice to use something more generic in the controlled list manager.