Develop Registry reporting / visualization component

[jordanpadams]

Provide something like Sol Banana or some other visualization component that can sit on top of the Registry and Search Services to enable visualization / access to metadata out of the box.

This can be very simplistic, but just something that comes built-in so users can easily see things like:

• archive metrics based on registry data
• set of attributes that exist in the indices
• attribute value sets

Actors: PDS Node Personnel, PDS EN Personnel (not especially tech saavy)
Use Cases:

• As a PDS Node, I want to be able to show a pie chart of all the different types of data products ingested into the PDS (Product Collection vs Bundle vs Products
• As a PDS Node, I want to see some simple visualization of the raw vs derived vs partially processed.
• As a PDS Node, I need to be able to easily answer questions like:
  • How many MER products are in the archive? How much total data size?
  • How many MER products by instrument are in the archive? How much total data size?

[jordanpadams]

July Schedule Status: Delayed due to slip in other tasks. Expected to catch back up with other tasks moving forward.

[tloubrieu-jpl]

@tdddblog Eugene looked at Banana but it as not been updated for about 5 years.

Silk can be an alternative. We will have a meeting to discuss that (Jordan, Eugene, Thomas).

Eugene will look at silk in the mean time https://github.com/lucidworks/silk

And https://gethue.com/solr-search-ui-only/

[tloubrieu-jpl]

Requirements: are to have a tool for visulization of the database content with charts.

[tloubrieu-jpl]

@tdddblog was able to deploy banana in nginx and configured it to work as the existing dashboard does (https://pds-gamma.jpl.nasa.gov/services/search-analytics/#/dashboard).

The configuration can be saved, but we don't know how to hide the button config.

@tdddblog will add the deployment documentation in pds-registry-app documentation as a guide for discipline nodes.

Next, eugene will look at alternative with elasticSearch/kibana. The way forward would be to generate json out of 'harvest' and push the results in elasticSearch. It is fine to spend 1 week on that part. A ticket will be created.

[tloubrieu-jpl]

Eugene is finalizing the documentation.

[tloubrieu-jpl]

The documentation is ready and available in the mvn site of the pds-registry-app.