@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
@prefix dct: <http://purl.org/dc/terms/>
@prefix foaf: <http://xmlns.com/foaf/0.1/>
@prefix void: <http://rdfs.org/ns/void#>
@prefix bl: <http://http://www.bl.uk/ns#>
@prefix blt: <http://www.bl.uk/schemas/bibliographic/blterms#>
@prefix event: <http://purl.org/NET/c4dm/event.owl#>
|
Base URI
Item source
ItemPath | Templates |
---|
/sitecore/content/Home/Collection Items |
BL_Global_Page_CollectionItem |
#item
Item Definition
#publication
Item Definition
Property | Value Source | Sample Value | Notes |
---|
rdf:type |
Fixed |
blt:PublicationEvent
|
|
event:time |
BL_Global_Page_CollectionItem:PublishedDateDisplay or, if empty PublishedDateFrom - PublishedDateTo
|
"estimated 1892" |
if PublishedDateFrom is populated, the and xsd:date is generated
If not, then PublishedDateDisplay is examined for a 4 digit number and if found a xsd:gYear is generated. This is the same logic as the website.
|
event:place |
BL_Global_Page_CollectionItem:Location |
http://www.bl.uk/place/london
|
V1: String literal from CMS
V2: These locations are selected from a picklist in /Global/Lookups/Place so could be exposed as URIs
|
See Also: Common Definitions
Comments (2)
Elliot Smith said
at 10:03 am on Oct 7, 2016
I would keep the two elements of the heldBy field separate (heldByInstitution, heldByPerson).
Richard Light said
at 12:06 pm on Oct 7, 2016
Isn't it worth an attempt to parse out a machine-processible date for the publication date, to sit alongside the display date?
I'll go across to RDF Definition - Person to follow up on the discussion on places.
You don't have permission to comment on this page.