Concept and concept-list datatype nodes should not store concept values in Resource Model JSON

[bferguso]

When exporting a resource model with a concept or concept-list datatype node, the values of the collection are stored in the node's configuration along with the URL to the Collection. Only the URL, not the values, should be stored in the exported/serialized Resource Model JSON.

[whatisgalen]

was this done intentionally to make the resource model fully portable even if you lacked the accompanying concept values?

[chiatt]

This wasn't intentional. My guess is that the domain datatype and concept datatypes share some code, and somehow the concepts are getting treated like domains.

[whatisgalen]

There is also this issue where things break because a graph gets imported with broken references to concept collections