How to handle records that have no landing page

[jmckenna]

• several partners have many records that do not have a landing page
  • IOCAfrica, BeBOP-OBON
  • see sample result: https://oceaninfohub.org/results/Vehicle?page=0&facet_query=facetType%3Dtxt_provider%26facetName%3DIOC%2BAfrica%2BData%2BPortal
• for example, in the case of the IOCAfrica node, they now set the url property to point to their main viewer page, when there is no landing page for the record
• this is confusing to the user of the ODIS front-end search
• should we somehow provide a default landing page for those records?

related to #39
related to iodepo/odis-arch#337

[jmckenna]

• is it possible to somehow catch this in the front-end, and include a note inside the record, that this record does not have a landing page? (maybe we'd have to catch this instead at the graph level, and include a flag in Solr)

[jmlord]

Not sure how we could catch this, it would mean not trusting the metadata and searching for content on the page?

In the specific case of IOC Africa, they could change the JSON-LD to lead to the country page, which would at least include the project:
Example: https://ioc-africa.org/dbs/advancedSearch.php?action=browse&project_country=1

[pbuttigieg]

Well, if there's no landing page, the url property should not be filled.

If that's the case, the UI can render a very basic page (similar to what the schema.org validator renders) that at least displays the metadata clearly. We can add a note at the top of that page stating that no webpage is provided for that record, but its metadata is below.

ODIS partners should be encouraged to produce landing pages on their side, where possible.

[pbuttigieg]