We should look into whether or not elasticsearch has pan-index searches, in which case perhaps we have a different index per collection (which would lead to more protection than we currently have against a collection pushing a bad field and needing to redo the entire thing for all projects to "remove" that field, OR we just switch to using the collection field within the API and the data repository for handling different repositories.
We had been splitting our collections apart using _type, but now that functionality is being removed in elasticsearch 6:
https://www.elastic.co/guide/en/elasticsearch/reference/6.x/removal-of-types.html
We should look into whether or not elasticsearch has pan-index searches, in which case perhaps we have a different index per collection (which would lead to more protection than we currently have against a collection pushing a bad field and needing to redo the entire thing for all projects to "remove" that field, OR we just switch to using the
collection
field within the API and the data repository for handling different repositories.