We're updating the issue view to help you get more done. 

Make JSON-LD localization configuration for OLFS.

Description

The JSON-LD content sent by Hyrax contains fields that should be part of the localized configuration of the server. We may wish to add these tot the BES and have the OLFS retrieve them, or we may want to add it to the olfs configuration.
There are two places in the OLFS that build json-ld responses.

One is in the construction of the contents.html page, the other is in the OPeNDAP Data Access form page (aka IFH).

In the contents.html pages we have this block:

1 2 3 4 5 6 7 8 9 10 11 12 "@type": "Organization", "name": "@PublisherName@", "address": { "@type": "PostalAddress", "addressCountry": "@Country@", "addressLocality": "@Street,City@", "addressRegion": "@State@", "postalCode": "@PostalCode@" }, "telephone": "@PublisherPhoneNumber@", "email": "@PublisherEmail@", "sameAs": "@OrganizationLandingPageURL@"

All of the RValues bracketed by '@' characters need to be provided in a configuration setting.

In the OPeNDAP Data Access Form page we currently have this block of json-ld:

1 2 3 4 5 "includedInDataCatalog": { "@type": "DataCatalog", "name": "Hyrax Data Server", "sameAs": "http://localhost:8080/opendap/hyrax/contents.html" },

And the value of includedInDataCatalog.name should be reviewed against the schema and I suspect it will need to be replaced with some site wide configuration value.

Status

Assignee

Nathan Potter

Reporter

Nathan Potter

Priority

Medium

Labels

None

Story Points

None

Fix versions

Epic Link