updating our couch views to search in the mask, not in the value of the datum fields
updating our couch views to search in the mask, not in the value of the datum fields

this means that confidential data wont be indexed in the glosser or in the morpheme analyser which might not be ideal for the user since they wont get to use confidential data in the training sets. but then at least their morpheme precedence rules wont leak the goals of their work, although we expect people to use the confidentiality button to protect their informants stories, rather than protect their itnellectual property. the search will still work if the user is running in a decrypted mode where the masks have data in them, since the serach runs client side. we can probably also make the glosser run client side too later if the user needs to use confidential data to train on. ideally, if the user has  100% confidential corpus they can mark it as private and not use the encryption buttons. then they get all the normal features.


Former-commit-id: 69a01b04e37a0fac55a05c716ed66df6d99327cb
iLanguage/iLanguage,vronvali/iLanguage,vronvali/iLanguage,cesine/iLanguage,vronvali/iLanguage,iLanguage/iLanguage,vronvali/iLanguage,cesine/iLanguage,cesine/iLanguage,iLanguage/iLanguage,cesine/iLanguage,iLanguage/iLanguage,vronvali/iLanguage,vronvali/iLanguage,cesine/iLanguage,iLanguage/iLanguage