handle type Service records / how to handle types that are not supported by the front-end

jmckenna commented 2 months ago

some partners have JSON-LD with type Service
however, if those records are loaded into Solr and exposed on the front-end, the entire front-end breaks
- because none of the 7 types supported by the front-end, are of type Service
- and because the records contain spatial, when a user clicks on Spatial Search the entire page will break (JS error / blank page) see screen capture below
- for several years now I 'get around this' by changing the type through the Solr indexer to something that is supported in the front-end (such as changing type SoftwareSourceCode to type CreativeWork ie. issue #131 )
- I could temporarily change the type Service records to display as type Dataset, but, that seems incorrect, if partners have records of type Service that have nothing to do with data.

What is the way forward?

Screenshot 2024-05-07 163225

jmckenna commented 2 months ago

other related issues:

pbuttigieg commented 2 months ago

No. the TOR of the contracts issued to both the back and front end include terms for adding arbitrary types to the UI .

if we can't add a service facet, these TOR are violated. this is trivial- it's just another type.

there must be no workarounds or tricks. ANY new type MUST be supported.

This has been known for years.

iodepo / oih-ui