Property talk:P866

Active discussions

Documentation

Perlentaucher ID
identifier in Perlentaucher (Q2071388)
RepresentsPerlentaucher (Q2071388)
Applicable "stated in" valuePerlentaucher (Q2071388)
Data typeExternal identifier
Template parameterde:Vorlage:Perlentaucher
Domain
According to this template: person
According to statements in the property:
human (Q5) or duo (Q10648343)
When possible, data should only be stored as statements
Allowed values(([a-z]+|39)\-?)+([1-9][0-9]*|[a-z]+|[1-9][a-z0-9]\-?[a-z0-9])(\-[a-z]+)?
ExampleJames D. Watson (Q83333)james-d-watson
Umberto Eco (Q12807)umberto-eco
Sourcehttps://www.perlentaucher.de/autoren/
Formatter URLhttps://www.perlentaucher.de/autor/$1.html
Tracking: usageCategory:Pages using Wikidata property P866 (Q61035015)
Related to country  Germany (Q183) (See 142 others)
Lists
Proposal discussionProposal discussion
Current uses
Total11,107
Main statement11,096>99.9% of uses
Qualifier2<0.1% of uses
Reference9<0.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
 
Format “(([a-z]+|39)\-?)+([1-9][0-9]*|[a-z]+|[1-9][a-z0-9]\-?[a-z0-9])(\-[a-z]+)?: value must be formatted using this pattern (PCRE syntax). (Help)
List of this constraint violations: Database reports/Constraint violations/P866#Format, hourly updated report, SPARQL, SPARQL (new)
 
Single value: this property generally contains a single value. (Help)
Exceptions are possible as rare values may exist. Known exceptions: Q2494, Q35064, Q43736, Q47152, Q91463, Q96128, Q99307, Q100443, Q102418, Q104133, Q109363, Q115630, Q124519, Q124911, Q186326, Q313077, Q316213, Q354371, Q532848, Q548162, Q944894, Q958557, Q1344849, Q2287418, Q5365550, Q101727
List of this constraint violations: Database reports/Constraint violations/P866#Single value, SPARQL, SPARQL (new)
 
Distinct values: this property likely contains a value that is different from all other items. (Help)
List of this constraint violations: Database reports/Constraint violations/P866#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value), SPARQL (new)
 
Item “VIAF ID (P214): Items with this property should also have “VIAF ID (P214)”. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P866#Item P214, search, SPARQL, SPARQL (new)
 
Item “GND ID (P227): Items with this property should also have “GND ID (P227)”. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P866#Item P227, search, SPARQL, SPARQL (new)
 
Type “human (Q5), duo (Q10648343): element must contain property “instance of (P31)” with classes “human (Q5), duo (Q10648343)” 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/P866#type Q5, Q10648343, SPARQL, SPARQL (new)
 
Conflicts with “instance of (P31): Wikimedia disambiguation page (Q4167410): this property must not be used with the listed properties and values. (Help)
List of this constraint violations: Database reports/Constraint violations/P866#Conflicts with P31, hourly updated report, search, SPARQL, SPARQL (new)
 
Item “instance of (P31): Items with this property should also have “instance of (P31)”. (Help)
List of this constraint violations: Database reports/Constraint violations/P866#Item P31, hourly updated report, search, SPARQL, SPARQL (new)
 
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.
List of this constraint violations: Database reports/Constraint violations/P866#allowed entity types, SPARQL (new)
 
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.
List of this constraint violations: Database reports/Constraint violations/P866#scope, 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.)


List of authorsEdit

List of authors by name: de:Portal:Literatur/Perlentaucher. --Kolja21 (talk) 00:50, 16 September 2013 (UTC)

Einzelner Wert / single valueEdit

Die Einschränkung "Einzelner Wert" sollten wir eventuell streichen. Zum einen ist es kein Fehler, wenn die numerische ID (z.B. "12293" aus der franz. Wikipedia) und die Namens-ID ("james-d-watson" aus der lateinschen WP) parallel eingetragen werden, zum anderen hat Perlentaucher für Autoren, die unter Pseudonym schreiben, in einigen Fällen auch unterschiedliche Seiten. --Kolja21 (talk) 23:19, 24 September 2013 (UTC)

"Single value" is wrong, see Ernst Jandl (Q44775) or Canan Topçu (Q84508). --Tibeton (talk) 02:13, 25 September 2013 (UTC)
Is there a possibility to divide this ID through qualifiers? P866 = a) numeric ID, b) name ID, c) pseudonym. --Kolja21 (talk) 17:52, 25 September 2013 (UTC)
Update: For case "c" there is pseudonym (P742). Any idea what property could be used to divide between numeric and name IDs? --Kolja21 (talk) 14:08, 19 January 2014 (UTC)
Text ID "ernst-jandl" is equal to numeric ID "2990". So double identifier format looks redundant. I suggest to convert all text values to numeric or visa verse. This will make data uniform and robust. This will allow to verify data using {{Constraint:Unique value}}, {{Constraint:Format}}, {{Constraint:Single value}}. This simplify data usage. — Ivan A. Krestinin (talk) 07:11, 4 November 2014 (UTC)
@Ivan A. Krestinin: Sounds reasonable. I've added "preferred value" for the numeric ID. --Kolja21 (talk) 12:50, 3 February 2015 (UTC)
I can schedule task that will convert current and future text IDs to numeric. Ok? — Ivan A. Krestinin (talk) 18:58, 3 February 2015 (UTC)
@Ivan A. Krestinin: This would be awesome. Can you also import the data from German WP (de:Vorlage:Perlentaucher = about 2.000 mixed IDs)? Unfortunately many articles still use the URL instead of the template. --Kolja21 (talk) 22:59, 3 February 2015 (UTC)
de:Vorlage:Perlentaucher states that the numeric identifiers are legacy data used until 2012. Given the care the website spends on avoiding to leak numeric identifiers they might as well being phased out. -- Gymel (talk) 07:31, 4 February 2015 (UTC)
The numbers are still in use (even if they are not shown in the URL any more), they are unique and they prove at what time an author was added to Perlentaucher. It would be a loss of information if we delete them. --Kolja21 (talk) 16:45, 4 February 2015 (UTC)
But you declared the numeric ids as "preferred" and @Ivan A. Krestinin: understood that all text URLs should be converted into the corresponding numeric value (probably by scraping it from the HTML/Javascript content of the Perlentaucher displays. We only can tell that perlentaucher.de itself "prefers" (promotes) the textual URIs and we have absolutely no information whatsoever which of the two forms will be more persistent. -- Gymel (talk) 17:37, 4 February 2015 (UTC)
@Gymel: At least you could list them as exceptions here above in the contraint violation template. Steak (talk) 20:18, 18 January 2017 (UTC)

Numerische ID funktioniert nicht mehrEdit

See de:Vorlage Diskussion:Perlentaucher#Numerische ID funktioniert nicht mehr. --Kolja21 (talk) 12:02, 7 May 2017 (UTC)

Return to "P866" page.