Closed ebenenglish closed 1 year ago
By default, Blacklight provides several alternate links in the HTML source for the catalog#show view:
<link rel="alternate" title="xml" type="application/xml" href="https://qc-dc3dev.bpl.org/search/oai-dev:wp988k45j.xml" /> <link rel="alternate" title="dc_xml" type="text/xml" href="https://qc-dc3dev.bpl.org/search/oai-dev:wp988k45j.dc_xml" /> <link rel="alternate" title="oai_dc_xml" type="text/xml" href="https://qc-dc3dev.bpl.org/search/oai-dev:wp988k45j.oai_dc_xml" />
These response are not supported by our application, the links return an empty XML document:
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd"></oai_dc:dc>
We should remove these links to cut down on unnecessary traffic to the application.
The links are rendered in the <head>, just after the CSRF tokens and before the OpenGraph meta tags.
<head>
By default, Blacklight provides several alternate links in the HTML source for the catalog#show view:
These response are not supported by our application, the links return an empty XML document:
We should remove these links to cut down on unnecessary traffic to the application.
The links are rendered in the
<head>
, just after the CSRF tokens and before the OpenGraph meta tags.