Skip to content

Conversation

@esko-piirainen
Copy link
Contributor

No description provided.

> {
> "species": true, // Matches taxa that have "species": true
> "informalTaxonGroups": "MVL.1", // Matches taxa with informalTaxonGoup MVL.1
> "informalTaxonGroups": "MVL.1,!MVL.2", // Matches taxa with informalTaxonGoup MVL.1 but not MVL.2
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be ["MVL.1" ,"!MVL.2"]

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

* Aggregate queries are separated to their own endpoints (`/aggregate`)
* Old filter parameter names are no longer supported. Use the actual property names from the model. For example `informalGroupFilters` -> `informalTaxonGroups`
* Name fields ("vernacularName" etc) are served also as multi-lang ("vernacularNameMultiLang"), so the translations can be shown even though `lang` param isn't `multi`
* All query parameters used for filtering are now moved to the request body, which must be named `filters`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The "filters" IS the body. By stating 'The body is called "filters"', I meant that when this documentation talks about "filters" or a "filter", it refers to a property in the body.

Maybe just leave out the whole sentence, since the example later explains it maybe better?

Copy link
Contributor Author

@esko-piirainen esko-piirainen Dec 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Original text was

"All query parameters that affect filtering are moved to the request body. The body is called "filters". Filtering can be now done by any property."

I interpreted that to mean the request must have a multipart body where the body part is named "filters".
Is it the intention of the original phrasing that the body will be later be called "filters" in this document?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made changes and dropped the 'filters' entirely

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it the intention of the original phrasing that the body will be later be called "filters" in this document?
Yes

Copy link
Contributor

@olzraiti olzraiti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@olzraiti olzraiti merged commit a67b9a2 into development Jan 5, 2026
@olzraiti olzraiti deleted the doc-language-refinement branch January 5, 2026 09:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants