Issue with search when it concerns custom schema entity
Reported by Rex from bld.ai
Hello experts, my name is Rex from bld.ai currently working for BHP. Currently, we're having issues regarding the fields that's showing up from the osdu search endpoint. We're expecting all the fields that were registered on our custom schema to show up in every record, however, some of the fields/property are missing. Upon observation this is what I've noticed: if the data type of the particular field is "string", the field will show up in the search endpoint irregardless if that particular field is included in the ingested record or not <- this is the behavior we want, (field "A" would show as "A": None if it's not part of the ingested record). however, if the data type of the field is non-string, it will only show up in the search endpoint if the field is part of the ingested record We want the fields to still show up even if we're working with non-string data type. Setting the all the fields to a "string" datatype may be potential solution, however, we might lose some search functionalities that are only true for the intended data type. I've tried ways that I've found from osdu documentation such as anyOf, oneOf, etc. to no avail. Perhaps some of you might have something that can help us?
cc @chad