Property talk:P5143

From Wikidata
Jump to navigation Jump to search

Documentation

amateur radio callsign
callsign assigned to licensed Amateur Radio operator, station or satellite
Representsamateur radio call sign (Q455644)
Data typeExternal identifier
Domainhuman (Q5), amateur radio station (Q455654), amateur radio club (Q11740286), amateur radio satellite (Q455647) or DX-pedition (Q5206574)
Allowed values^[A-Z0-9]{3,7}$
ExampleJames Martel Reneau (Q51763981)N4REN
Imre Ferenczy (Q1000565)HA1UD
Formatter URLhttps://www.qrzcq.com/call/$1
https://qrzcq.com/call/$1
https://amatpres.anfr.fr/annuaire.do?reqCode=filtrer&indicatif=$1
See alsocall sign (P2317)
Lists
Proposal discussionProposal discussion
Current uses
Total241
Main statement217 out of 12,536 (2% complete)90% of uses
Qualifier135.4% of uses
Reference114.6% 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/P5143#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/P5143#Unique value, SPARQL (every item), SPARQL (by value)
Format “^[A-Z0-9]{3,7}$: 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/P5143#Format, SPARQL
Item “instance of (P31): Items with this property should also have “instance of (P31)”. (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/P5143#Item P31, 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/P5143#Entity types
Scope is as main value (Q54828448), as reference (Q54828450), as qualifier (Q54828449): 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/P5143#Scope, SPARQL

Occupation constraint

[edit]

Is there a good reason to have an occupation constraint on this field? Amateur radio is by definition (legally and by P31) a "hobby" and while it could be put under occupation, it's not an occupation per se. While a person who has a ham radio callsign will likely have had an occupation at some point in their life, it's not something required to be a ham. Ruthbrarian (talk) 19:45, 26 March 2021 (UTC)[reply]

Updating to add that as I'm reviewing people who do not have that value added, it seems inappropriate to add "occupation: amateur radio operator" to Hassan II (Q69103), Qaboos bin Said Al Said (Q57331), Walter Cronkite (Q31073), Helen Sharman (Q237473) (who states in the interview I used for her reference that she only used it while aboard Mir), Priscilla Presley (Q234773), etc. In many cases it's an interesting data point about a person who's noteworthy for other things but not a significant enough part of their life to seem to merit an "occupation" statement. Ruthbrarian (talk)

@Ruthbrarian: I agree completely. If someone wants to show that a person's hobby is amateur radio, you could add a stament Samantha Cristoforetti (Q379039)interested in (P2650)amateur radio (Q185727)object of statement has role (P3831)hobby (Q47728). In addition, this property should be used in items about DX-pedition (Q5206574), amateur radio club (Q11740286), amateur radio satellite (Q455647) and amateur radio station (Q455654), where having occupation (P106) does not even make sense since they are not human. I will make these changes to the constraints soon if no one opposes. –Samoasambia 20:44, 19 January 2024 (UTC)[reply]

Single-value constraint

[edit]

I wouldn't consider it exceptionally rare that people have more than one callsign during their lifetime, or even simultaneously, for various reasons. They may have alternating residence in different countries, or emigrate altogether. Participants of DXpeditions get temporary (sometimes personal) callsigns at their destination. At the annual (except for epidemic years …) "Ham Radio" fair in Friedrichshafen at Lake Constance, regularly an opportunity is offered to take the test for a USA-based license (with correspondig callsign) to European hams additionally to their existing ones. In Germany, if you upgrade your license from basic to advanced level, your callsign has to change from DO* to something else. Even if you do nothing of the above, the systematics of callsigns where you live may change (in the de-WP there is a long article about the history of amateur radio callsigns in Germany), requiring operators to get new ones. --DK2EO (talk) 17:10, 23 October 2021 (UTC)[reply]

@DK2EO: Yes that is very much true. Maybe we should consider removing the single-value constraint (and possibly distinct-values constraint as well)? I changed both to be suggestion constraints, so that the warnings on items are just suggestions and users may ignore them. There's now the possibility to separate callsigns with applies to jurisdiction (P1001) added by IagoQnsi, and that probably solves most of the possible cases together with the dates. –Samoasambia 13:14, 7 August 2024 (UTC)[reply]

Data type from external ID to string

[edit]

I propose that we change the data type of this property from external identifier (Q21754218) to Wikibase string datatype (Q29934246) because there is no global database for amateur radio callsigns, and persons/organizations may share the same callsign over time, which means they are not unique identifiers. Currently we link to QRZCQ.com which is essensially a website where people can create profiles for their callsigns and where the developers of the site have scraped some callsigns (but definitely not all) to create default profiles. For example, early radioamateurs Lelia Constanța Băjenescu (Q50885476) and Ioan Băjenescu (Q59143024) that shared the callsign CV5BI results in nothing on QRZCQ.com but the link is visible on the items anyways. In my opinion this is as if we linked property name in native language (P1559) to Facebook search, which doesn't make any sense. If a wiki wants to use this property to link to QRZCQ.com (or any other service) they can still define that locally with a template.

I asked about the possibility to changed the data type of a property, and I got an answer that this could be done easily via Maintenance scripts if we have a consensus about it, so creating a new property is not necessary. –Samoasambia 12:55, 7 August 2024 (UTC)[reply]

@Pintoch @DK2EO @Ruthbrarian. –Samoasambia 12:58, 7 August 2024 (UTC)[reply]
@Samoasambia: assuming that there is consensus for the move (I have no opinion), it looks like the way to get it done would be to file a Phabricator ticket similar to phab:T367174. − Pintoch (talk) 16:47, 8 August 2024 (UTC)[reply]