Schema.org formatter #1511
Closed
Schema.org formatter #1511
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
introduce header/footer for no-js ui
This reverts commit 1936efc.
Need to be able to get all the groups, regardless of the logged in user. Conflicts: docs/manuals
manage WGS84BoundingBox from WMTS getCapabilities
…guideline. Add /records/{{uuid}} service (geonetwork#1508).
…n (to not to make user thinks the list will change when another dataset is choosen. Add current selection title next to the list of layers to make the user understand that the selected layers in the service layers list should match the selected dataset.
Add two translations admin/harvesting/webservices
This may happen on layer group having no name. eg. ``` Layer> <Title> <![CDATA[ ERRUISSOL - Classe de pente ]]> </Title> <SRS>EPSG:4326</SRS> <SRS>EPSG:31370</SRS> <SRS>EPSG:3857</SRS> <!-- alias 3857 --> <SRS>EPSG:102100</SRS> <LatLonBoundingBox minx="2.833713" miny="49.457554" maxx="6.469319" maxy="50.860598"/> <BoundingBox SRS="EPSG:4326" minx="2.833713" miny="49.457554" maxx="6.469319" maxy="50.860598"/> <BoundingBox SRS="EPSG:31370" minx="41995.000000" miny="18155.000000" maxx="298025.000000" maxy="172185.000000"/> <BoundingBox SRS="EPSG:3857" minx="315447.500862" miny="6352858.350196" maxx="720161.326116" maxy="6596672.014829"/> <Layer queryable="1"> ``` In such case, the selection process which expects a layer name does not work. So do not display those layers.
|
Why not inserting schema.org tags in the main xsl-view formatter ? We should have schema.org tags in any pages presenting a metadata record no ? including angular app ? |
|
Hi francois, indeed it makes sense to add it to the xsl-view itself, then we may not need s separate schema-org formatte. Haven't considered that before. The angular app currently can't be spidered by search engines (afaik), so doesn't make much sense to add schema.org there. But indeed on the search-nojs we could add schema.org annotations as well. |
|
Closing, replaced by #1609 |
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.
This pull requests suggests a minimal implementation of an html-export of iso19139 metadata annotated with schema.org using microdata, to optimise search engine crawlability. Most obvious is metadata describing datasets, which is annotated as schema.org/Dataset. Other resources, such as series and services are annotated as schema.org/dataCatalog (similar to geo-dcat-ap), and software as schema.org/SoftwareApplication.
A formatter seems a good concept for search engine optimisation, due to the fact that all formatter output is cached, formatter responses are generally very quick, which is well appreciated by search engines, which generally rank search results on response time.
This pull request still has an issue with the formatter html service, which seems to embed all formatter output in a < metadata > tag. Also the reference to css is hardcoded, because when embedding css with 'css-load' it will try to load a non existing css called gn_default.
The formatter uses header-footer concept as introduced in pull request #1492. The pages can be registered at search engines using the portal.sitemap service or by using the catalog.search.nojs service. Note that for this to function I introduced a rule in urlrewrite.xml that will forward any url /metadata/{uuid} to the schema.org formatter