Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Publishing Fennica as Linked Data is a work in progress. Some parts of this document are marked TODO, to indicate that the modelling or implementation is not yet finished. For more detailed information about current issues, see the open issues on the bib-rdf-pipeline GitHub project that implements the conversion of data from MARC records and auxiliary sources into the published RDF.

...

The data set is currently available as:

  • a SPARQL endpoint on on http://linkeddata-kk.lib.helsinkidata.nationallibrary.fi/fennicabib/sparqlwith the following named graphs:
    • <http://data.nationallibrary.fi/bib/fennica> - Fennica
    data in the default graph
    • bibliographic data
    • <http://www.yso.fi/onto/yso/> - YSO concepts
    • <http://www.yso.fi/onto/yso-paikat/> - YSO places
  • downloadable data dumps at at http://linkeddata-kk.lib.helsinkidata.nationallibrary.fi/download/ in HDT and gzipped N-Triples formats
  • TODO Linked Data access (HTML, RDF/XML, JSON-LD, Turtle, N-Triples) via URI dereferencing
  • TODO Linked Data Fragments access

...

The URI patterns are in draft status and may still change. Some entities are currently represented only as blank nodes in the RDF graph, but may later be given URIs.

TODO the URIs in this data set are not yet resolvable. We plan to use the urn.fi resolver to manage identifiers, but it has not yet been set up to resolve this namespace.

Entity types

Overview

Image Added

This diagram shows the main entity types and their relationships as a UML class diagram.

 

Image Removed

Work

URI pattern: http://urn.fi/URN:NBN:fi:bib:me:Wnnnnnnnnnxx

...

Field nameRDF propertyExpected Value / RangeDefinitionCardinalityData Quality Notes
Typerdf:typeClassType of resource. Always both schema:CreativeWork and bf:Work. May also have the more specific types schema:CreativeWorkSeries and schema:Periodical (see below).2..* 
Titleschema:nameLiteralTitle of work1..* 
Subjectschema:aboutskos:Concept, Work, Person, Organization or LiteralSubject matter of the work0..*YSO concepts are used whenever possible. Literal values are used in cases where no entity was found matching the label.
Has instanceschema:workExampleInstanceExample/instance/realization/derivation of the concept of this work. eg. The paperback edition, first edition, or eBook.0..* 
Languageschema:inLanguageLiteral (language code)Language of the work, expressed as a language code following BCP 47 rules (i.e. ISO 639-1 or 639-3 code)0..*Needs cleanup. There are a few bad values such as numeric values
Authorschema:authorPerson or OrganizationThe main author of this work0..1 
Contributorschema:contributorPerson or OrganizationA secondary contributor to the work0..* 
Content typerdau:P60049skos:Concept from RDA Content Type vocabulary 0..1Should generally be available for most Works, but in practice, missing for some of them.
Is part of (series)schema:isPartOfSeriesThe series which this work is a part of.0..* 
Is translation ofschema:translationOfWorkWorkThe work that this work has been translated from. Inverse of "Has translation"0..* 
Has translationschema:workTranslationWorkA work that is a translation of the content of this work. Inverse of "Is translation of"0..* 

...

Periodical

The Series Periodical entity type is a sub-type of Work and represents a publication series.

(instance) 
Field nameRDF propertyExpected Value / RangeDefinitionCardinalityData Quality Notes
Typerdf:typeClassAlways schema:CreativeWorkSeriesPeriodical1 
Has partschema:hasPartInstanceWorkA work that is included in this series1..* 

Periodical

The Series sub-type Periodical is used for more formally established series that may have ISSNs and/or a specific sequence of volumes.

Class
Field nameRDF propertyExpected Value / RangeDefinitionCardinalityData Quality Notes
Typerdf:typeAlways schema:Periodical1 
ISSNschema:issnLiteral (ISSN code)The International Standard Serial Number (ISSN) that identifies this periodical0..1 

...

Field nameRDF propertyExpected Value / RangeDefinitionCardinalityData Quality Notes
Typerdf:typeClassAlways schema:Person1 
Nameschema:nameLiteralThe name of the person1May contain birth and death years. These should be moved to a separate field or removed 
Birth dateschema:birthDateLiteralThe year of birth of the person0..1Available only for deceased persons due to privacy concerns.
Death dateschema:deathDateLiteralThe year of death of the person0..1Available only for deceased persons.

Organization

URI pattern: http://urn.fi/URN:NBN:fi:bib:me:Onnnnnnnnnxx or blank node or CN identifier (TBD)

...