Searching Linked Open Data - Person Entity
Introduction
Primo VE uses Linked Open Data (LOD), which is structured data that utilizes Web technologies to link related information, to enable users to discover additional information regarding a person (such as an author or historical figure) and to relate it to materials provided by your library. The UI includes the following elements to enable discovery of person entities: Autocomplete Person, Person Info Card, and Person Page.
-
Changes to Library of Congress (LC) information take ~1 week to appear in Primo VE.
-
Changes to Wikidata pages take ~2 weeks to appear in Primo VE.
-
New Wikidata pages take 2-5 weeks to appear in Primo VE.
-
Currently, this functionality is supported in English only.
Person Information Sources
The sources of the person entity information are the Library of Congress Name Authority and Wikidata. If the information exists in LC, it is used. Otherwise, it is taken from Wikidata. The Person description is based on Wikipedia. The Library of Congress and Wikidata persons-related information is updated on our servers once a week. This means that materials removed by the Library of Congress or Wikidata (for any reason) is automatically removed from the Persons index within a reasonable time after the originating site makes the change.
The match between LC and Wikidata is based on the Identifier property. For example, in LC it is the LC ID (which is taken from 010 a, z), and in Wikidata it is the LC authority ID. We use the LCNAME identifier in Wikidata for matching with LC data. We do not add Wikidata authors if they do not exist in LC.
| Person Property | LC Field | Wikidata Property |
|---|---|---|
|
Person Name |
100 a,q,c,d |
|
|
Identifier |
010 a,z |
Library of Congress authority ID (P244) |
|
Birth date |
046 f |
date of birth (P569) |
|
Birth place |
370 a |
place of birth (P19), country (P17) |
|
Death date |
046 g |
date of death (P570) |
|
Death place |
370 b |
place of death (P20), country (P17) |
|
Variants (see from tracing—Personal Name) |
400 a |
|
|
Link to Wikidata |
024 1 |
https://www.wikidata.org/wiki/Special:EntityData/{id}.json |
|
Field of activity |
372 a |
field of work (P101) |
|
Occupation |
374 a |
occupation (P106) |
|
Short description |
N/A |
descriptions > "en" > value |
|
Link to image |
N/A |
image (P18) |
|
Link to Wikipedia |
N/A |
sitelinks > "enwiki" > url |
|
IdRef ID |
N/A |
IdRef ID (P269) |
|
GND ID |
N/A |
GND ID (P227) |
Autocomplete Person Entity
Person entity suggestions are provided for search terms entered for simple and advanced searches. These suggestions appear at the bottom of the autocomplete list, below the suggestions used to return results from the library catalog. Selecting one of these suggestions opens the associated Person page.
Ranking Logic
Autocomplete for the person entity utilizes Elastic's function_score query functionality, which calculates a score based on the field values returned from records in the initial query's results. More specifically, several new fields are indexed and leveraged during query time. The following fields are currently leveraged to generate values for these new fields:
| Existing Field | Indexed Field | Value | Notes |
|---|---|---|---|
| occupations | occupations_cnt | number (total count * 0.7) |
Emphasis is put on the occupations and field of work fields. |
|
field_of_work |
field_of_work_cnt | ||
|
variants |
variants_cnt | number (total count * 0.2) |
Counts for 'variants' have been discounted slightly since a large number of variants can negatively affect ranking. For example, Robyn William has many variants, but it appeared for names such as Waters Charles. |
|
short_description |
has_description | boolean (value of 3.5 if true) | |
|
image_info.link_to_image |
has_image_info | boolean (value of 3 if true) | |
|
link_to_wikidata |
has_link_to_wikidata | boolean (value of 2.5 if true) | |
|
link_to_wikipedia |
has_link_to_wikipedia | boolean (value of 2 if true) |
For example, a query for queen elizabeth returns several person entities including Elizabeth I, Elizabeth II, and Prince Philip, Duke of Edinburgh. Elizabeth II has more variants and less occupations than Prince Philip, but the original query has a higher score due to variants being included in the original scoring which results in its final score being higher. In addition, the existence of both a description and an image gives more weight to a result that has only links to Wikidata or Wikipedia.
Person Info Card
The Person Info Card appears at the top of the Recommendations panel on the Full Display page. It is displayed for each person entity (such as author or historical figure) that is associated with the record. Selecting the person's name in the card opens the Person page. The order of the cards in the Related Persons section is based on the following priority: 1) Creator, 2) Contributor, and 3) Subject. In the following example, the book is linked with the author and the person about which the book was written.
Person Page
The Person page is a dedicated page that displays the person's information on a full page. In addition, this page includes the following sections, which link to bibliographic records that are connected to LCNAMES authority headings:
-
Titles in Library Written by Person – Returns all bibliographic records where the person LC ID appears as a creator or contributor. This section is limited to a maximum of 25 records and is sorted by date.
-
Titles in Library Written about Person – Returns all bibliographic records where the person LC ID appears as a subject. This section is limited to a maximum of 25 records and is sorted by date.
-
People Associated with Person – From those matching bibliographic records, all other person entities that appear as a creator, contributor, or subject with a person LC ID are returned. In case of many related persons, the list is ordered by the most bibliographic records that are shared with the person. This section is limited to a maximum of 40 persons.
Configuration Options
This functionality is disabled by default and is configured at the institution level. Refer to the following table to enable this functionality and to configure related options.
| Element | Description |
|---|---|
|
Discovery Customer Settings page (Configuration > Discovery > Other > Customer Settings) |
The following parameters enable person entity at the institution level:
For additional information, see Discovery Customer Settings. |
|
New for December 2024 |
The following parameters enable person entity at the view level:
For additional information, see Configuring Discovery Views for Primo VE. |
|
Person Entity Labels code table (Configuration > Discovery > Display Configuration > Labels) |
The following codes have been added to support the Person page:
The following codes have been added to support the Person Info Card on the Full Display page:
|
|
Aria Labels code table (Configuration > Discovery > Display Configuration > Labels) |
The following codes have been added to support accessibility for the Person page:
The following codes have been added to support accessibility for the Person Info Card:
|
Analytics - Person Entity Discovery
To track information regarding this functionality, the Action Usage subject area includes the following actions:
| Group | Subgroup | Action | Description |
|---|---|---|---|
|
Exploration |
Related Persons |
Click on the link to Wikipedia |
On the Person page, the user selected the person's link. |
|
Click on "Show more" on a related person |
In the Person Info Card, the user selected the Show more link to expand the card. |
||
|
Related person section appeared |
In the Full Display, the Person Info Card appeared. |
||
|
Click on the link from info card to full person page |
In the Person Info Card, the user selected the person's link. |
||
|
Click on the link from autocomplete to full person page |
The user selected the person's autocomplete suggestion. |