Invisible Facets

[LucaCinquini]

We should have a mechanism for facets to be listed in the file facets.properties (so that they can be used to query the search back-end), but not show up as facet options in the web-fe. This can be needed, for example, when multiple portals use the same underlying services.

With respect to the current format of each line in the file facets.properties:

facet_short_name=number:facet_long_name:<true|false>:optional_facet_descrip

possible mechanisms include:

a) ignore the facet if the "facet number" is 0 or negative

b) ignore the facet if the facet label is empty

c) include a new field named "visible"

[stephenpascoe]

Further, we need to be able to configure the interface to show different facets in different contexts. Can this be added to a ticket or shall I open a new one?

E.g. CORDEX is using these facets

• RCM Model
• Model Version
• Domain

ESGF ISI-MIP portal (in testing) will use these facets:

• Social Forcing
• CO2 Forcing
• Irrigation forcing
• crop
• impact model

In both cases these facets are only relevant if the user is interested in that project and would be confusing otherwise. Is a solution in the works or can we (IS-ENES) help accelerate it?

[LucaCinquini]

Hi Stephen, there is nothing in the work right now and we could discuss development plans at one of the developers calls (Thursday), or GO-ESSP calls ? Having multiple facets should not be a problem at all for the search back-end, but the front-end was never architected to support this functionality, so it would probably be a big change. We could look for examples at the CoG site, where different projects can define different sets of facets, see for example: http://earthsystemcog.org/search/ncpp/ and: http://earthsystemcog.org/search/dcmip-2012/