List of Links to Person Aggregation Pages

[dlschwartz]

@emgeier @davidamichelson

Here is a description of what we would like to see in the list of links to person aggregation pages on the Person Browse page, see #115.

---

Theodora, Roman empress — ܡܠܟܬܐ ܬܐܘܕܘܪܐ (38 factoids)
[Syriaca ID: http://syriaca.org/person/779]
{Abstract}

---

The first line above would start with the English rdfs:label in the Syriaca.org graph (not the SPEAR graph) + an em dash + the Syriac rdfs:label in the Syriaca.org graph. This would be followed by a count of the factoids including this person in parentheses. And this whole string would be a hyperlink to the person aggregation page for this person: https://dev.spear-prosop.org/aggregate/person/779.html.

The second line simply states the Syriaca.org URI. To avoid confusion, there should be no hyperlink here. That link is available on the aggregation page itself.

The third line above indicates that we would like to include the Syriaca.org abstract here for disambiguation purposes. This should be the object of schema:description in the Syriaca.org graph.

I'm hoping this isn't too confusing. Please let me know if there are any questions.

[emgeier]

Some persons have two descriptions associated with them. I put in both, concatenated, for the "abstract" display. Display example:

Aphrahat -- ܐܦܪܗܛ
[http://syriaca.org/person/10]
Syriac author of 23 ‘Demonstrations’, known as ‘the Persian Sage’. In hagiography: Aphrahat was known as an anchorite who converted from Zoroastrianism to Christianity and fought Arianism in Antioch .

Example search result ouput: "head": {
"vars": [
"person",
"label",
"description"
]
},
"results": {
"bindings": [
{
"person": {
"type": "uri",
"value": "http://syriaca.org/person/10"
},
"label": {
"xml:lang": "en",
"type": "literal",
"value": "Aphrahat"
},
"description": {
"xml:lang": "en",
"type": "literal",
"value": "Syriac author of 23 ‘Demonstrations’, known as ‘the Persian Sage’."
}
},
{
"person": {
"type": "uri",
"value": "http://syriaca.org/person/10"
},
"label": {
"xml:lang": "syr",
"type": "literal",
"value": "ܐܦܪܗܛ"
},
"description": {
"xml:lang": "en",
"type": "literal",
"value": "Syriac author of 23 ‘Demonstrations’, known as ‘the Persian Sage’."
}
},
{
"person": {
"type": "uri",
"value": "http://syriaca.org/person/10"
},
"label": {
"xml:lang": "en",
"type": "literal",
"value": "Aphrahat"
},
"description": {
"xml:lang": "en",
"type": "literal",
"value": "In hagiography: Aphrahat was known as an anchorite who converted from Zoroastrianism to Christianity and fought Arianism in Antioch ."
}
},
{
"person": {
"type": "uri",
"value": "http://syriaca.org/person/10"
},
"label": {
"xml:lang": "syr",
"type": "literal",
"value": "ܐܦܪܗܛ"
},
"description": {
"xml:lang": "en",
"type": "literal",
"value": "In hagiography: Aphrahat was known as an anchorite who converted from Zoroastrianism to Christianity and fought Arianism in Antioch ."
}
},

[dlschwartz]

@dlschwartz
We need to update the RDF serialization to include one predicate for our preferred description and another predicate for alternate descriptions. We currently use schema:description for all abstracts.

I think the above is the easiest solution. The other would be to qualify the schema:description statement instances with a predicate whose object would connect the description with the appropriate series. These are indicated in the TEI with a @corresp attribute.