Property talk:P3064
Jump to navigation
Jump to search
Documentation
LepIndex ID
identifier for a Lepidoptera taxon, in the UK Natural History Museum's 'Global Lepidoptera Names Index'
identifier for a Lepidoptera taxon, in the UK Natural History Museum's 'Global Lepidoptera Names Index'
[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/P3064#Single value, hourly updated report, SPARQLDistinct 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/P3064#Unique value, SPARQL (every item), SPARQL (by value)
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/P3064#Item P225, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3064#Item P225, search, SPARQL
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/P3064#Item P105, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3064#Item P105, search, SPARQL
Item “taxon rank (P105): genus (Q34740), species (Q7432), subspecies (Q68947)”: Items with this property should also have “taxon rank (P105): genus (Q34740), species (Q7432), subspecies (Q68947)”. (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/P3064#Item P105, search
List of violations of this constraint: Database reports/Constraint violations/P3064#Format, 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/P3064#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/P3064#Scope, SPARQL
Pattern ^(\d+)\.0$ will be automatically replaced to \1. Testing: TODO list |
This property is being used by: Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
|
URL format change at LepIndex
[edit]I've noticed that the format of URLs used by LepIndex has changed. That means that many of our links (I think all species links) no longer work. I'm not sure what is involved in fixing this, but I've started a discussion at en:Wikipedia talk:WikiProject Lepidoptera#LepIndex. Thank you.SchreiberBike (talk) 21:26, 14 April 2018 (UTC)
http://www.nhm.ac.uk/our-science/data/lepindex/search/detail.dsml?TaxonNo=257131.0
becomeshttp://www.nhm.ac.uk/our-science/data/lepindex/detail/?taxonno=257131
- So we have to change the formatter URL and to remove the version information ".0". My bot can do the latter. --Succu (talk) 21:44, 14 April 2018 (UTC)
- @Succu: it's not just remove the ".0" there is also the "lepindex/search/detail.dsml?TaxonNo" shortened in "lepindex/detail/?taxonno". I can do it too with QuickStatements but for 200,000 items, it would be better by bot, could you do it ? Cdlt, VIGNERON (talk) 06:45, 25 April 2018 (UTC)
- Should be done. --Succu (talk) 21:20, 27 May 2018 (UTC)
- @Succu: it's not just remove the ".0" there is also the "lepindex/search/detail.dsml?TaxonNo" shortened in "lepindex/detail/?taxonno". I can do it too with QuickStatements but for 200,000 items, it would be better by bot, could you do it ? Cdlt, VIGNERON (talk) 06:45, 25 April 2018 (UTC)
- @User:Shyamal: your change will cause over 200,000 constraint violation. I will remove the format constraint until the issue is fixed. --Succu (talk) 06:22, 15 April 2018 (UTC)
Categories:
- United Kingdom-related properties
- All Properties
- Properties with external-id-datatype
- Properties used on 100000+ items
- Properties with single value constraints
- Properties with unique value constraints
- Properties with constraints on items using them
- Properties with format constraints
- Properties with entity type constraints
- Properties with scope constraints
- Taxonomy properties