Include and process languageCode facet field

[Twan Goosen]

A field 'languageCode' is now created by the importer (see #547). Depending on the available information, it will generate a value in one of two formats:

• code:{ISO639-3 code}
• name:{non-standardised name}

In the first case, the language code should be mapped to a (localised) language name read from a resource (probably a property file generated from the iso639-3 list).

In the second case, the name should be shown without the prefix.

The verbatim value should be used in queries, URL parameters etc.

Notice: this facet will replace the existing 'language' and 'languages' fields and should be renamed to 'language' after removal of these two fields.

[Twan Goosen]

The importer/solr prerequisite #547 has been completed by Thomas. Turning this into a 'blocker' as the changes need to be reflected in the webapp.

Notice that the facet 'languageCode' needs to be renamed to 'language', replacing both 'language' and 'languages' after this has been completed and it has been assured that neither of the old facets is still used in the webapp.

[Twan Goosen]

Made the LanguageCodeUtils available from VLO commons in r5997

[Twan Goosen]

Replace 'language' and 'languages' fields with 'language code' in r5999, then implemented a label that converts the language code/name strings to language names and applied this to various panels in r6002:6003.

TODO: generate link to language info page

[Twan Goosen]

Sorting of 'all values' based on converted value in r6005:6007

[Twan Goosen]

Link to language info page & converted value display in breadcrumb in r6010:6012
Also includes a handle api json parsing fix

[Twan Goosen]

Search/Filtering? should also happen on basis of converted values

[Twan Goosen]

Replying to twan.goosen@…:

Search/Filtering should also happen on basis of converted values

Fixed in r6040