Date: Thu, 28 Mar 2024 08:17:43 -0400 (EDT) Message-ID: <1673876943.27684.1711628263548@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_27683_207686149.1711628263548" ------=_Part_27683_207686149.1711628263548 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]/config/crosswalks/google-metadata.properties
Please, note that the file location changed between DSpace = 1.7 and 1.8. It's now in the "crosswalks" directory, so check that the goog= le-metadata.config configuration property points to the right file:
google-metadata.config =3D ${dspace.dir}/config/crosswalks/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.