Wikidata:Property proposal/job title
Jump to navigation
Jump to search
job title
[edit]Originally proposed at Wikidata:Property proposal/Person
Not done
| Description | person's official job title |
|---|---|
| Data type | Monolingual text |
| Domain | Q5 |
| Example |
|
Motivation
[edit]People such as those in the examples often have job titles that are unique, and not suitable for labels of Wikidata items about the more generic name for the role. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:37, 9 April 2019 (UTC)
Discussion
[edit]
Question Why should it be monolingual? They may be titles, but they are generic enough to be translated across languages, as they frequently are. NMaia (talk) 07:25, 10 April 2019 (UTC)
- For which we have the qualifier literal translation (P2441). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:35, 10 April 2019 (UTC)
Oppose An alternative approach would be to use position held (P39) in the usual way, together with the qualifier object named as (P1932) to give the exact job title. If the position really can't be matched to anything we have an item for, then position held (P39) = somevalueis a possibility, with the qualifier giving the exact title. Keeping all this sort of information together in P39 statements helps in eg allowing them to be sorted into date order, and ensuring uniform application of constraints and qualifiers. Jheald (talk) 15:57, 15 April 2019 (UTC)- Oppose I'm with Jheald on this question - keep the information in position held (P39) using qualifiers. Job titles are often puffed up or even silly. One company I worked with had a "Vice President in charge of Cookies", and that was on his business card. --WiseWoman (talk) 21:02, 24 April 2019 (UTC)
- Oppose per above -Theklan (talk) 14:50, 22 May 2019 (UTC)
- Oppose per Jheald --DannyS712 (talk) 21:08, 6 June 2019 (UTC)
- Oppose 1Veertje (talk) 10:03, 7 June 2019 (UTC)