-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Raw values in occurrences have information from processed values #841
Comments
It has been fine like this for a long time and I do worry such a change will break something in biocache-hubs.
Not to mention that if a raw field is absent the non-raw field is used intentionally in the RAW section. It is more useful to deprecate this output format and version a format consistent with the download format, i.e. a format capable of listing of all fields in a flat structure that can reference Of course we could ignore everything else inconsistent and just fix these 2 fields, and do all of this again next time someone raises an issue of any of the other inconsistencies. |
Only moving subspecies and subspeciesID. pull request #864 |
Nefarious processed subspecies content is no longer appearing in raw: https://biocache-ws-test.ala.org.au/ws/occurrence/da76bbe0-0539-4051-bf08-9080a9f12775 |
@adam-collins just looking at this again, in test this record has a subspecies value appearing in the UI that's not in the data: |
moved the new issue to #903 |
See for example https://api.ala.org.au/occurrences/occurrences/da76bbe0-0539-4051-bf08-9080a9f12775
This record has an invalid name match caused by misprocessing and difficulty parsing the supplied name. However, it shows another error where the derived subspecies is inserted into the raw data. This seems to be coming from the service, rather than the SOLR index.
The originally supplied data is
The information in the solr index is
There is no
raw_subspecies
in the solr documentThe data returned by the API call, with assertions removed for brevity is
raw.classification.subspecies
andraw.classification.subspeciesID
contain values not in the original data.The text was updated successfully, but these errors were encountered: