Inconsistent naming of terms across filter, select and facet parameters

[gorbynet]

Is it possible to make terminology consistent across the parameters in the API?
For example, the parameter is called 'type' in filter and select, but 'type-name' when used in facet.
This makes it quite hard to hand-write API queries, as I'm never sure whether I've got the right parameter name until I run the query. Here's a table of the discrepancies that regularly trip me up, as they're different or missing across different parameters:

filter	select	facet
doi	DOI
isbn	ISBN
issn	ISSN	issn
issue	journal-issue
orcid		orcid
prefix	prefix
publisher	publisher-name
relation.type		relation-type
type	type
type-name*		type-name
volume	journal-volume

*Although 'type-name' is permitted as a filter parameter, it doesn't return any results. Compare:
https://api.crossref.org/works/?rows=0&filter=type-name:book-chapter
https://api.crossref.org/works/?rows=0&filter=type:book-chapter

[pdavis8]

Hi, thanks for sending this over. I have the same issues as described here, I will add it to the enhancements list.

We are currently migrating the REST API from a Solr to an ElasticSearch database. This is needed to scale the REST API, and it will resolve particular eccentricities in the data model due to Solr's constraints as well as speed deployment of new features. During this time we have paused work on the REST API, including non-critical bugs and new features, to facilitate a smooth transition so that users do not experience any disruption to the service.

Apologies for any inconvenience while we work on making the API more robust and efficient.