Description

The SDP Data Product Dashboard will be the primary access mechanism for users to access Data Products produced by the telescope. It is expected that the number of these products, produced will grow large. Each of these Data Products will be 'decorated' with metadata describing it. The metadata might be distinct based on the product type. In order to enable users to find these data products, a capable search back end will be needed. Since search is a well understood problem and a search back end will have most common use-cases created, this will prevent the development of code that would otherwise just be "reinventing the wheel".

The expected capability of the search back end would include capability to cater key value pair searches, geospatial search, time range filters. It should also be an industry accepted solution and it would be great if this does not increase the technology footprint of the project. A prototype implementation by the NALEDI team has used Elasticsearch as a prototype technology which could be optionally included in the SDP Data Product Dashboard.

WHY: Making a decision here, will allow teams to invest effort into the accepted technology rather than spending effort on something that will become obsolete.

WHAT:

• Search back end for the SDP Data Product Dashboard.
• Off the shelf.