Values to display on HTML pages
These are the fields to be pulled though onto the SERPS page. [field] denotes field in the index this should be taken from, where multiple items (e.g. [field1, field2]) are fallbacks.
-
Image: 320x240px (4x3 aspect entropy crop) (naturally 272x204px on large screens) [
???] -
Title: Stephenson's Rocket [
title] -
Category: Locomotive and rolling stock [
category] ObjectName: Steam locomotive (object name or term)-
Date: 1890 (or 1890 - 1910) [
lifecycle.creation.date] -
Icons: object icon + on display (if on display) [
???] -
Graph text (if no image) [
description,title,summary_title]
-
Image: 320x240px (4x3 aspect entropy crop) (naturally 272x204px on large screens) [
???] -
Title: The Charles Babbage Papers [
title] -
Date: 1890 - 1910 [
???] Icons: archive folder icon-
Graph text (if no image): extent field [
???]
-
Image: 320x240px (4x3 aspect entropy crop) (naturally 272x204px on large screens) [
???] -
Title: End view of inning printing paper (may need to truncate) [
title] -
Archive Name: The Charles Babbage Papers (may need to drop this one?) [
fonds.summary_title] -
Date: 1890 - 1910 [
???] Icons: archive document icon-
Graph text (if no image): extent field [
???]
-
Image: 384px wide [
???] -
Name: Charles Babbage [
name,summary_title] -
Occupation: [
occupation] ie. "occupation": "mathematician; computer pioneer", -
Date: 1890 - 1910 [
lifecycle.birth.date] - [lifecycle.death.date] - Icons: person icon
-
Graph text (if no image): [
description:type=brief biography] (this is the short 1 line biog.)
Example record Duchess of Hamilton Accession No. #1976-7000 /objects/smgc-objects-205752
Note: category, materials, terms, taxonomy terms, makers, locations, places etc. should all be linkable (back to the search results page with the relevent fiter set)
These should be listed at the top of the page on seperate lines, prefixed by their relationship/role. (prior to launch we will need to supress all but a defined/limited set of relationships (maker, designer, inventor etc; which will be supplied), but for now it would be useful to allow testers to see all the values)
"maker": [{
"@link": {
"role": [{
"value": "designer"
}],
"type": "reference"
},
"admin": {
"id": "agent-1015",
"uid": "smgc-agent-1015"
},
"summary_title": "Stanier, Sir William Arthur"
}, {
"@link": {
"role": [{
"value": "maker"
}],
"type": "reference"
},
"admin": {
"id": "agent-3891",
"uid": "smgc-agent-3891"
},
"summary_title": "London, Midland & Scottish Railway"
}],
credit_line
"legal": {
"credit_line": "Butlins",
"legal_status": "permanent collection"
},
component.measurements[].display
Multiple measurements should be displayed on seperate lines
length over buffers: 22511 mm, driving wheel diameter: 2057 mm
"component": [{
"measurements": {
"dimensions": [{
"dimension": "depth",
"units": "in",
"value": "886 1/4"
}, {
"dimension": "depth",
"units": "mm",
"value": "22511"
}],
"display": "length over buffers: 22511 mm,"
},
"name": "length over buffers"
},
{
"measurements": {
"dimensions": [{
"dimension": "diameter",
"units": "in",
"value": "81"
}, {
"dimension": "diameter",
"units": "mm",
"value": "2057"
}],
"display": "driving wheel diameter: 2057 mm,"
},
"name": "driving wheel diameter"
}
"name": [
{
"primary": true,
"type": "object name",
"value": "steam locomotive"
}
]
In addition to the above name.value (which is a free text field) an object can have multiple 'terms' associated with it.
These will be de-normalise in the index so that the parent/broader terms for each individual term is stored on the object document itself. Once that index work is complete, a hierarchy for each term can be constructed directly from the object page. The taxonomies will be displayed side by side; up to three wide.
Until the above work is complete, we should simple display a comma seperated list of 'terms' where the value is equal to "Object Name" in a style similar to the other 'tombstone' fields.
"terms": [
{
"@link": {
"role": [
{
"value": "Object Name"
}
],
"type": "reference"
},
"admin": {
"id": "term-262150",
"uid": "smgc-term-262150"
},
"summary_title": "photograph"
},
{
"@link": {
"role": [
{
"value": "Object Name"
}
],
"type": "reference"
},
"admin": {
"id": "term-267305",
"uid": "smgc-term-267305"
},
"summary_title": "Photography"
},
Description fields
-
biography(short biog) -
note(full biog)
"type.sub_type": "person"
-
name.valuelifecycle.birth.datelifecycle.birth.date(name normalised/reversed on comma, date in smaller font) - OCCUPATION:
occupation(split on semicolon) - BORN IN:
lifecycle.birth.location
"type.sub_type": "organisation"
-
name.valuelifecycle.birth.datelifecycle.birth.date(name normalised/reversed on comma, date in smaller font) - INDUSTRY:
occupation(split on semicolon) (???) - LOCATED:
lifecycle.birth.location(???)
These should all be displayed in a related links block on the RHS
For now list all the relationships, but open a new issue with a screenshot (once finished) as we will want to restrict the list of relationships we explicitly label (ie. we won't show (relationship) as that is the default; expect we'll want to constrain it to a set of 'known' relationship labels TBA).
The person page should display (up to) two rows of related results for both object and documents (two rows each type).
These should be constrained to rows/multiples of 6, to eliminate 'orphans' (ie. 6 and 12 is good, 9 should be trimmed back to 6 and 14 trimmed back to 12).
Each block should have a more link that takes the user back to the search result page with a filter for that person and the object or document filter selected (as appropriate).