Property talk:P1015
Contents
Documentation
identifier in the Norwegian information system BIBSYS
|
Type “organization (Q43229), fictional organization (Q14623646), human (Q5), group of humans (Q16334295), house name (Q19913602), fictional character (Q95074), convention (Q625994), newspaper (Q11032), theatre (Q24354), film (Q11424), literary work (Q7725634), park (Q22698)”: element 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 (Q24354), film (Q11424), literary work (Q7725634), park (Q22698)” or their subclasses (defined using subclass of (P279)). (Help) Exceptions are possible as rare values may exist. List of this constraint violations: Database reports/Constraint violations/P1015#type Q43229, Q14623646, Q5, Q16334295, Q19913602, Q95074, Q625994, Q11032, Q24354, Q11424, Q7725634, Q22698, SPARQL, SPARQL (new) |
|
Single value: this property generally contains a single value. (Help) Exceptions are possible as rare values may exist. List of this constraint violations: Database reports/Constraint violations/P1015#Single value, SPARQL, SPARQL (new) |
|
Distinct values: this property likely contains a value that is different from all other items. (Help) Exceptions are possible as rare values may exist. List of this constraint violations: Database reports/Constraint violations/P1015#Unique value, SPARQL (every item), SPARQL (by value), SPARQL (new) |
|
Format “[1-9](\d{0,8}|\d{12})”: value must be formatted using this pattern (PCRE syntax). (Help)Exceptions are possible as rare values may exist. List of this constraint violations: Database reports/Constraint violations/P1015#Format, SPARQL, SPARQL (new) |
|
|
Item “instance of (P31)”: Items with this property should also have “instance of (P31)”. (Help) Exceptions are possible as rare values may exist. List of this constraint violations: Database reports/Constraint violations/P1015#Item P31, search, SPARQL, SPARQL (new) |
|
This property is being used by: Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Incomplete proposalEdit
Imho it would be wise first to complete the proposal before adding a new property:
- infobox parameter = ?
- domain = ?
- allowed values = ?
- suggested values = ?
- source = ?
- 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)
Formatter URLEdit
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)
- 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)
- 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)
Discrepancy between the 2 regex constraintsEdit
- format as a regular expression (P1793) shows
[1-9]\d*, yet - format constraint (Q21502404) shows
[1-9](\d{0,8}|\d{12})
Which one is it? —Tom.Reding (talk) 22:55, 21 June 2018 (UTC)
RDF formatter URIEdit
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)