found the linked data which was added in datum
moving all the json into a json attribute to make it more clear

that the fields can have any heirarchical structure inside of them if the apps know how to display them. (value and mask are searchable representations of the structure) for #1524  and #1526 this should help clarify since before only the enteredByUser and modifiedByUsers had internal json because all the default fields were IGT strings. the morphemes field did have json in it (the alternate segmentations that the system proposed and the user didnt choose) but since that only emerged as the user used the prototoype app, if youre developing a new app you would never notice that there was json in there. in realiity any field can have json in it.
more linked data
commonjs-ification of datumfields for #209 #228 #219 #157 and #183
one more linkedData to relatedData
commonjs-ification of datumfield for #209 #228 #219 #157 and #183
corpus can create datum

and commonjsificaiton of datumstates and datumtags
collections and datum fields can be cloned
import can ask corpus to make a datum for it
import preprocessing pipeline is running
testing custom import