JSON-LD / Schema.org mapping #25
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Mapping developed from https://developers.google.com/search/docs/data-types/dataset and schema.org
Also handles entity loading better and removes special handling of Items when generating breadcrumbs (unnecessary since Items will always be leaf pages).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Among minor rendering improvements, this introduces a (partial) mapping of STAC to JSON-LD / Schema.org as recognized by Google Dataset Search in order to facilitate structured search + display of STAC records.
Search engines will see these JSON-LD records in a
<script>tag withtype="application/ld+json"when catalogs are pre-rendered. Browser extensions (e.g. OpenLink Structured Data Sniffer) can read dynamically-generated metadata.