Property talk:P865

From Wikidata
Jump to navigation Jump to search

Documentation

BMLO ID
identifier of Bayerisches Musiker-Lexikon Online
Associated itemBayerisches Musiker-Lexikon Online (Q47191)
Applicable "stated in" valueBayerisches Musiker-Lexikon Online (Q47191)
Data typeExternal identifier
Template parameterde:Vorlage:BMLO
Domain
According to this template: person
According to statements in the property:
human (Q5)
When possible, data should only be stored as statements
Allowed values[a-z][0-9]{4} (string of 1 lowercase letter, followed by 4 digits)
ExampleLorenz Hauslaib (Q11933906)h1795
Amy Winehouse (Q15897)w1883
Sourcehttps://www.bmlo.uni-muenchen.de/
Formatter URLhttps://bmlo.de/$1
Tracking: usageCategory:Pages using Wikidata property P865 (Q53977382)
Lists
Proposal discussionProposal discussion
Current uses
Total7,255
Main statement7,15298.6% of uses
Qualifier2<0.1% of uses
Reference1011.4% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Single value: this property generally contains a single value. (Help)
List of violations of this constraint: Database reports/Constraint violations/P865#Single value, hourly updated report, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (Help)
List of violations of this constraint: Database reports/Constraint violations/P865#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)
Format “[a-z][0-9]{4}: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P865#Format, hourly updated report, SPARQL
Item “sex or gender (P21): Items with this property should also have “sex or gender (P21)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P865#Item P21, hourly updated report, search, SPARQL
Item “date of birth (P569): Items with this property should also have “date of birth (P569)”. (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/P865#Item P569, SPARQL
Item “given name (P735): Items with this property should also have “given name (P735)”. (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/P865#Item P735, search, SPARQL
Item “occupation (P106): Items with this property should also have “occupation (P106)”. (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/P865#Item P106, search, SPARQL
Item “GND ID (P227): Items with this property should also have “GND ID (P227)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P865#Item P227, hourly updated report, search, SPARQL
Item “Deutsche Biographie (GND) ID (P7902): Items with this property should also have “Deutsche Biographie (GND) ID (P7902)”. (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/P865#Item P7902, search, SPARQL
Type “human (Q5): item must contain property “instance of (P31)” with classes “human (Q5)” or their subclasses (defined using subclass of (P279)). (Help)
List of violations of this constraint: Database reports/Constraint violations/P865#Type Q5, hourly updated report, 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/P865#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/P865#Scope, SPARQL
This property is being used by:

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

6 years BMLO ID on disambiguation page[edit]

https://www.wikidata.org/w/index.php?title=Q2172812&diff=100417092&oldid=87152527 MrProperLawAndOrder (talk) 16:39, 13 May 2020 (UTC)[reply]

Without GND[edit]

Without GND with VIAF[edit]


Copy from my talk, for future reference


@Bargioni: said me to tell you that he acted as follows:

  • saved the first two columns of https://w.wiki/QmY in a file named missing_GND.tsv
  • he launched
perl -lne 'use JSON; chomp; ($q,$v)=split/\t/; $js=`curl -s $v/justlinks.json`; $j=from_json($js); print $q."\t$v\t". join ", ",@{$j->{DNB}}; sleep 1' missing_GND.tsv > gnd.qs

If you understand it better than me, it might be useful. Good evening, --Epìdosis 17:44, 14 May 2020 (UTC)[reply]

@Bargioni, Epìdosis, Kolja21: - this is great news guys! Great it can be done via commandline and no need to download whole VIAF DB. I cannot write such perl stuff, but maybe one day can at least read and understand. MrProperLawAndOrder (talk) 17:48, 14 May 2020 (UTC)[reply]

Without GND without VIAF[edit]

GND beacon[edit]

@Kolja21: The beacon currently has 25803 GNDs. WD has 6237 BMLO IDs. The highest number is not in DtBio https://www.deutsche-biographie.de/1209449145.html , so maybe it is quite new. BMLO also offers permalinks via GND. ... So, they actively support GND and have more GND than WD has BMLO IDs. I think it would be easier for completeness management if WD could store the BMLO GND IDs. Then it would be like Sächsische Bio and DtBio. MrProperLawAndOrder (talk) 14:12, 14 May 2020 (UTC)[reply]

GND type name in BMLO[edit]

http://bmlo.de/s4058 - GND 103946535 type name, it is also in the beacon. So, maybe one should wait until at least the type-Tn bugs are gone in BMLO. Also, I don't know what they do if a GND gets redirected, do they keep the old or replace. DtBio as aggregator hopefully switches to the redirect targets. MrProperLawAndOrder (talk) 19:51, 14 May 2020 (UTC)[reply]

GND type family in BMLO[edit]

http://bmlo.de/h0479 lists 123458633 as secondary GND, but this has type family Q94443119. @Kolja21: beacon lists secondary GNDs of type not matching with type of primary GND. So, their GND management/presentation is not matching the standards of Wikidata. MrProperLawAndOrder (talk) 21:51, 14 May 2020 (UTC)[reply]

Difficult for bots, but works well. BMLO/GND 123458633 = 3 members of Hauser family (Q94443119). --Kolja21 (talk) 22:10, 14 May 2020 (UTC)[reply]
@Kolja21: difficult for humans - the presentation with putting a GND from another item on the page of a human without any statement why it is there is just weird. (Like their 9-digit ISNI) MrProperLawAndOrder (talk) 01:32, 15 May 2020 (UTC)[reply]

GND type person in BMLO - two permanent on one human[edit]

http://bmlo.de/g0200 Q15858520 - http://d-nb.info/gnd/131597825 Geissler AND http://d-nb.info/gnd/136357946 Geißler. MrProperLawAndOrder (talk) 03:02, 15 May 2020 (UTC)[reply]

Type constraint human only[edit]

It seems BMLO only has type=human. I added a constraint. I found this via sex/gender required and each that has no sex was either deleted in BMLO or was a group of people in WD and should be on a person item. MrProperLawAndOrder (talk) 14:16, 14 May 2020 (UTC)[reply]

Indeed. Bayerisches Musiker-Lexikon Online (Q47191) is a biographical dictionary = GND, Typ p. Good idea. --Kolja21 (talk) 19:28, 14 May 2020 (UTC)[reply]
They could also store other types to describe the humans. E.g. the instruments, or the occupations. MrProperLawAndOrder (talk) 03:05, 15 May 2020 (UTC)[reply]