Property talk:P2804

Latest comment: 1 year ago by Yachty4000 in topic Sailor ID

Documentation

World Sailing member ID (archived)
member identifier for a sailor in the World Sailing database (use P11616 for the new website)
Associated itemWorld Sailing (Q381929)
Data typeExternal identifier
Corresponding templateTemplate:World Sailing (Q20638298)
Domainhuman (Q5) (note: this should be moved to the property statements)
Allowed values[1-9][0-9]+
ExampleHannah Mills (Q7836739)59279
Mathew Belcher (Q195281)42900
Sourcehttps://data-isaf.soticcloud.net/sailors/sailor_search.php
Formatter URLhttps://web.archive.org/web/1/https://data-isaf.soticcloud.net/biog.php?memberid=$1
Tracking: usageCategory:Pages using Wikidata property P2804 (Q26964509)
See alsoFFVoile sailor ID (P4261), World Sailing regatta ID (P4832), World Sailing sailor ID (P11616)
Lists
Proposal discussionProposal discussion
Current uses
Total1,337
Main statement1,32999.4% of uses
Qualifier20.1% of uses
Reference60.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)
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/P2804#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/P2804#Unique value, SPARQL (every item), SPARQL (by value)
Item “instance of (P31): human (Q5): Items with this property should also have “instance of (P31): human (Q5)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P2804#Item P31, hourly updated report, search, SPARQL
Format “[1-9][0-9]+: 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/P2804#Format, 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/P2804#Item P106, 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/P2804#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/P2804#Scope, SPARQL
Item “World Sailing sailor ID (P11616): Items with this property should also have “World Sailing sailor ID (P11616)”. (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/P2804#Item P11616, search, SPARQL
Item “sport (P641): Items with this property should also have “sport (P641)”. (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/P2804#Item P641, search, SPARQL

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

Discussion

edit

Sailor ID

edit

This template needs revising but I am not clever enough todo it. I am not sure why this is based on numerical Member ID when Sailor ID "GBRHM15" is the common reference used for all regatta registration, login, result and what is publicised on the individual pages. Member ID is a consequence of changing the website about a decade ago as the database table needs a numerical key. I suggest wikidata links to the ISAF Sailor ID and this template is adjusted to accept either. Yachty4000 01:14, 24 July 2021 (UTC)Reply

I agree that http://www.sailing.org/biog.php?ID=GBRHM15 would be a better agreement (see also User talk:Lymantria#World Sailing Member ID - P2804) but I don't know if transforming this property would be easy done. @Edgars2007:. Lymantria (talk) 15:28, 31 July 2021 (UTC)Reply
Proved correct website updated sailor ID remains the wikidata property is not used there primary identifier with redesign of website the URL pathway is now https://www.sailing.org/sailor?ref=GBRHM15 which should have been a simple update. How do we transition over to World Sailing Sailor ID Yachty4000 23:20, 14 June 2022 (UTC)Reply
The usual method on Wikidata to propose the creation a new property for a different identifier. For example, there are two properties for rowers in World Rowing athlete database (Q21008628). I just proposed a new property for the Sailor ID, see Wikidata:Property proposal/World Sailing sailor ID. -- Zyxw (talk) 05:19, 28 January 2023 (UTC)Reply
Why do we have two identifiers to get to the same place? This should be deleted the old website is accessible via the same alpha numerical code as the new one I am not sure why you would want to as they both look at the same database to populate the content. How do we go about proposing the deleteing of this property. We have a new property for the original identifier and this one serving no purpose. My issue with wikidata is it isn't community based. Yachty4000 22:55, 10 June 2023 (UTC)Reply
Return to "P2804" page.