Context:
To avoid no-clobber job errors when ingesting overlapping datasets, it has been suggested that json-only datasets can be set to avoid publishing anything to S3 and instead rely on (overwritable) ElasticSearch for storage of the json data product.
The documentation does not make it clear which values (under the "publish" and "browse" attributes of the dataset definition) are optional and may be omitted, what valid null values for these attributes are, or whether the "publish" and "browse" attributes may be omitted entirely.
Answer:
Omission of the "publish" and "browse" attributes is valid, and the suggested way of accomplishing this.