SOLR fields should not be removed but deprecated

[nickdos]

There are a number of SOLR fields which have been removed from the index yet these remain in some config files (e.g. http:https://biocache.ala.org.au/ws/search/grouped/facets).

So there is an issue of keeping the various listings of fields "in sync". Maybe have a single config file that defines these (including store/indexed/description) and generate everything from this file?

But a first step would be to keep the fields listed in http:https://biocache.ala.org.au/ws/search/grouped/facets but mark them indexed: false and stored:false and have a deprecated field or simply add "deprecated" in the description.

If the field has been changed or moved, then the new field should be mentioned as well. E.g. "imcra" is no longer indexed but it is equivalent to "cl21".

[djtfmartin]

Agree in principle, butkeeping these deprecated fields will result in a even more bloated index. Im not really sure where to take this issue so Im going to close. I guess in this instance we should have just raised a bug against the grouped/facets config and fixed that.

[nickdos]

I suppose I'd like to see a mechanism where we can mark a field as deprecated, leave it there for 6 months and then remove it. This way, external users of web services will have fair warning about the removal. ATM the removal of fields has caused ALA headaches with app functionality breaking, etc.

[nickdos]

Happened again as facet "state" has been removed and now all hubs advanced search forms and existing facets lists are missing state, as it is now cl2013. We need a mapping for named facets to clXXXX codes so we can continue to serve existing apps and 3rd party users of our web services.