Property talk:P1015

From Wikidata
Jump to navigation Jump to search

Documentation

NORAF ID
identifier in the Norwegian Authority File, formerly Bibsys Authority File
Associated itemUnit (Q55097783), National Library of Norway (Q924551)
Applicable "stated in" valueNorwegian Authority File: Persons and Corporate Bodies (Q16889143)
Has qualityVIAF component (Q26921380)
Data typeExternal identifier
Corresponding templateTemplate:Bibsys (Q6717525)
Template parameteren:Template:Authority control: "BIBSYS" - Template:Authority control (Q3907614)
Domain
According to this template: Organizations, persons, places...
According to statements in the property:
organization (Q43229), fictional organization (Q14623646), human (Q5), group of humans (Q16334295), house name (Q19913602), fictional character (Q95074), convention (Q625994), newspaper (Q11032), theatre building (Q24354), film (Q11424), literary work (Q7725634), park (Q22698), event (Q1656682), building (Q41176), document (Q49848), vehicle (Q42889), written work (Q47461344), legendary figure (Q13002315), human whose existence is disputed (Q21070568) or television series (Q5398426)
When possible, data should only be stored as statements
Allowed values[1-9]\d* (numeric string with one or more digits (leading "x" and "0"s should be removed))
ExampleRainer Maria Rilke (Q76483)90053126 (RDF)
Clint Eastwood (Q43203)90725834 (RDF)
International Labour Organization (Q54129)90098122 (RDF)
Sourcehttps://authority.bibsys.no/authority/
Formatter URLhttps://authority.bibsys.no/authority/rest/authorities/html/$1
Robot and gadget jobsDeltaBot does the following jobs: BIBSYS authority files are up to now only searchable through VIAF.
Tracking: usageCategory:Pages with BIBSYS identifiers (Q8709054)
Related to country Norway (Q20) (See 103 others)
See alsoBIBSYS work ID (P6211)
Lists
Proposal discussionProposal discussion
Current uses
Total226,936
Main statement222,56898.1% of uses
Qualifier3<0.1% of uses
Reference4,3651.9% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “organization (Q43229), fictional organization (Q14623646), human (Q5), group of humans (Q16334295), house name (Q19913602), fictional character (Q95074), convention (Q625994), newspaper (Q11032), theatre building (Q24354), film (Q11424), literary work (Q7725634), park (Q22698), event (Q1656682), building (Q41176), document (Q49848), vehicle (Q42889), written work (Q47461344), legendary figure (Q13002315), human whose existence is disputed (Q21070568), television series (Q5398426): item must contain property “instance of (P31)” with classes “organization (Q43229), fictional organization (Q14623646), human (Q5), group of humans (Q16334295), house name (Q19913602), fictional character (Q95074), convention (Q625994), newspaper (Q11032), theatre building (Q24354), film (Q11424), literary work (Q7725634), park (Q22698), event (Q1656682), building (Q41176), document (Q49848), vehicle (Q42889), written work (Q47461344), legendary figure (Q13002315), human whose existence is disputed (Q21070568), television series (Q5398426)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Titanic (Q25173)
List of violations of this constraint: Database reports/Constraint violations/P1015#Type Q43229, Q14623646, Q5, Q16334295, Q19913602, Q95074, Q625994, Q11032, Q24354, Q11424, Q7725634, Q22698, Q1656682, Q41176, Q49848, Q42889, Q47461344, Q13002315, Q21070568, Q5398426, SPARQL
Single value: this property generally contains a single value. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1015#Single value, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1015#Unique value, SPARQL (every item), SPARQL (by value)
Format “[1-9](\d{0,13}|\d{13}): value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1015#Format, SPARQL
Item “instance of (P31): Items with this property should also have “instance of (P31)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1015#Item P31, search, SPARQL
Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1015#Entity types
Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1015#Scope, SPARQL


Incomplete proposal

[edit]

Imho it would be wise first to complete the proposal before adding a new property:

  1. infobox parameter = ?
  2. domain = ?
  3. allowed values = ?
  4. suggested values = ?
  5. source = ?
  6. filter = ?

There seems to be no original source for BIBSYS, only it's mentioning in the collection of authority files VIAF. If we use VIAF ID (P214) as source, the values are redundant. (Please keep in mind that VIAF is helpful, but also outdated, faulty and full of pseudo numbers.) --Kolja21 (talk) 03:02, 10 November 2013 (UTC)[reply]

Formatter URL

[edit]

I changed the formatter URL to use https://tools.wmflabs.org/bsaut/ for now since the old one stopped working after a change to a new library system. The tool gets data from https://authority.bibsys.no/ , which is currently only a REST API, but should also provide HTML representations we can link to in the future. Danmichaelo (talk) 11:56, 14 December 2015 (UTC)[reply]

This tuns the tool-service into the authorative site for BIBSYS. This is wrong in so many ways. It's like a mirror site of Wikipedia should claim it has the authorative URI for Wikipedia. Jeblad (talk) 18:58, 14 December 2015 (UTC)[reply]
I sure see that the approach is problematic, but considered that it could still work until a better solution was found, since it provides a way to look up the identifier and get some data back (directly from the Bibsys API). Afaiks the only alternative right now is to just blank the field until Bibsys comes up with something we can use. We can do that though. Danmichaelo (talk) 19:09, 14 December 2015 (UTC)[reply]

Discrepancy between the 2 regex constraints

[edit]
  1. format as a regular expression (P1793) shows [1-9]\d*, yet
  2. format constraint (Q21502404) shows [1-9](\d{0,8}|\d{12})

Which one is it? —Tom.Reding (talk) 22:55, 21 June 2018 (UTC)[reply]

RDF formatter URI

[edit]

The current formatter URI for RDF resource (P1921)https://livedata.bibsys.no/authority/$1 seems problematic: the host livedata.bibsys.no currently refuses connections and doesn’t respond to pings, and something like “livedata” looks more like a data access point than the canonical URI anyways IMHO. The current examples on http://data.bibsys.no/autreg/index.html point to URLs like http://data.bibsys.no/data/notrbib/authorityentry/x90061718, which respond with RDF data that also identify that URI as the subject (rdf:about). --Lucas Werkmeister (WMDE) (talk) 12:51, 9 July 2018 (UTC)[reply]