Property talk:P952

Latest comment: 1 year ago by Jheald in topic Change data type to identifier

Documentation

ISCO-88 occupation class
International Standard Classification of Occupations code according to the International Labour Organization (ILO) classification structure as of 1988
DescriptionStandard International Classification code for jobs. "ISCO is a tool for organizing jobs into a clearly defined set of groups according to the tasks and duties undertaken in the job."
RepresentsInternational Standard Classification of Occupations (Q1233766)
Data typeString
Domain
According to this template: profession (Q28640), occupation (Q12737077), jobs
According to statements in the property:
occupation (Q12737077)
When possible, data should only be stored as statements
Allowed values[0-9]{4}
Example
According to this template: value for librarian (Q182436) is: 2622 Librarians and related information professionals
According to statements in the property:
playwright (Q214917)2451
stonemason (Q328325)7122
lumberjack (Q1124183)6141
When possible, data should only be stored as statements
Sourcehttp://www.ilo.org/public/english/bureau/stat/isco/index.htm
Formatter URLhttps://www.ilo.org/public/english/bureau/stat/isco/isco88/$1.htm
Robot and gadget jobsCheck against the XLS complete structure: http://www.ilo.org/public/english/bureau/stat/isco/index.htm
Tracking: usageCategory:Pages using Wikidata property P952 (Q26206596)
See alsoISCO-08 occupation class (P8283)
Lists
Proposal discussionProposal discussion
Current uses
Total368
Main statement36498.9% of uses
Qualifier41.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “occupation (Q12737077): item must contain property “instance of (P31)” with classes “occupation (Q12737077)” or their subclasses (defined using subclass of (P279)). (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/P952#Type Q12737077, SPARQL
Format “[0-9]{4}: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P952#Format, hourly updated report, SPARQL
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P952#Scope, hourly updated report, SPARQL
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/P952#Single value, SPARQL

Mix'n'match redirect to dummy.org (domain for sale) edit

Hi,

The webpage http://tools.wmflabs.org/mix-n-match/visual_match.html#catalog=148 redirect to http://dummy.org/?redir=frame&uid=dummy5969b1e8e4fdd8.46051129

--Manu1400 (talk) 16:29, 19 July 2017 (UTC)Reply

I could not find a way to link to a relevant page based on the id. This property does not have a URL pattern either. I have removed the URLs, and thus the links, which are now plain text. If you know of a URL pattern I could use, please let me know. --Magnus Manske (talk) 15:15, 20 July 2017 (UTC)Reply

Standards edit

There are two different standards, with two different number series, ISCO08 from 2008 and ISCO-88 from 1988. This property does not say which one it follows. The example for librarian (Q182436) uses 2622 which matches ISCO-08, playwright (Q214917) uses 2451 which matches ISCO-88, stonemason (Q328325) uses 2452 but should be 7113 for ISCO-08 or 7122 for ISCO-88. In short it seems like a mess. Jeblad (talk) 11:22, 14 May 2020 (UTC)Reply

My intention is to change this property to cover ISCO-88 if/when Wikidata:Property proposal/ISCO-08 occupation code is accepted. Jeblad (talk) 13:31, 26 May 2020 (UTC)Reply
I've been working down the following query https://w.wiki/5dgM to check every item with an ISCO-88 value and make sure it also has an ISCO-08 value (and that both are correct), and checking the relationships against the official comparison tables available here (downloadable .dcx file).
Unfortunately Mix'n'match catalogue 148 had data for ISCO-08 but had been associated with this property instead. I hope that misalignment is now corrected, but it has left a lot of clean up to do. I've been finding maybe 50% of current P952 values should actually have been ISCO-08 occupation class (P8283) ones. -- Jheald (talk) 20:23, 29 August 2022 (UTC)Reply

Change data type to identifier edit

The data type of this property is currently "String", but IMO it should be "External identifier". Assuming this is correct, how can I request that change? /cc Teolemon, TomT0m, NMaia (fka Pikolas), and Danrok, from the property proposal discussion. --Waldyrious (talk) 14:40, 20 January 2022 (UTC)Reply

@Waldyrious: No. Per wikidata's current practices, it is correct that the type of this property is not "external identifier", and that it appears in the main section, not the external identifiers section.
The reason is that wikidata uses this property as a classification not an identifier. The difference is that (except in rare circumstances) an identifier should identify a single item; other items should not have the same value of the identifier.
But for P952 this is not the case: the way we use P952 we do not expect different items to have different values. Instead we use P952 as a classification. All items for different occupations in the same ISCO-88 group should have P952 statements with the same value. So potentially there may be many items, all with the same P952 value, and this is fully expected behaviour.
It is to try to be a clue to users to try to help flag this that P952 appears in the main section, not the external identifiers section; and that it has type 'string' rather than 'external identifier'. Hope this helps, Jheald (talk) 20:35, 29 August 2022 (UTC)Reply
Thanks for the response, Jheald. The rationale you've described makes sense to me, but perhaps we should use a name for the property that better describes its meaning — "occupation" is generally understood to represent a single profession, not a broad category of professions. Similarly, the "code" at the end of the name creates ambiguity as it's commonly used for identifier-type properties. I would find it more intuitive if this property was named "ISCO-88 occupation class", for example. WDYT? --Waldyrious (talk) 08:30, 30 August 2022 (UTC)Reply
Makes sense; & keep the existing label as an alias. Jheald (talk) 13:34, 30 August 2022 (UTC)Reply
Done. We can always revert it if people don't like it. Jheald (talk) 16:19, 30 August 2022 (UTC)Reply
Return to "P952" page.