Date: Fri, 29 Mar 2024 03:11:50 -0400 (EDT) Message-ID: <158161710.29960.1711696310318@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_29959_613927593.1711696310317" ------=_Part_29959_613927593.1711696310317 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Google Scholar, in crawling sites, prefers a meta-tag schema of =
its own devising. This schema contains names which are all prefixed b=
y the string "citation_", and provide various metadata about the article/it=
em being indexed.
As of DSpace 1.7, there is a mapping facility to connect metadata fields=
with these citation fields in HTML. In order to enable this function=
ality, the switch needs to be flipped in dspace.cfg:
google-metadata.enable =3D true
Once the feature is enabled, the mapping is configured by a separate con=
figuration file located here:
${dspace.dir}/config/google-metadata.properties
This file contains name/value pairs linking meta-tags with DSpace metada=
ta fields. E.g=E2=80=A6
google.citation_title =3D dc.title google.citation_publisher =3D dc.publisher google.citation_authors =3D dc.author | dc.contributor.author | dc.creator
There is further documentation in this configuration file explaining pro=
per syntax in specifying which metadata fields to use. If a value is =
omitted for a meta-tag field, the meta-tag is simply not included in the HT=
ML output.
The values for each item are interpolated when the item is viewed, and t= he appropriate meta-tags are included in the HTML head tag, on both the Bri= ef Item Display and the Full Item Display. This is implemented in the= XMLUI and JSPUI.