Property talk:P937

From Wikidata
Jump to navigation Jump to search

Documentation

work location
location where persons or organisations were actively participating in employment, business or other work
Representsworkplace (Q628858)
Data typeItem
Template parameterWork location in Commons:Template:Creator
Domainhuman (Q5), fictional character (Q95074), group of humans (Q16334295), notname (Q1747829), human whose existence is disputed (Q21070568), group of fictional characters (Q14514600), mythical character (Q4271324), job activity (Q192581), legendary figure (Q13002315), position (Q4164871), specialty (Q1047113), profession (Q28640), working animal (Q228534) or organization (Q43229)
ExampleFilippo Brunelleschi (Q174330)Florence (Q2044)
Joseph Stalin (Q855)Saint Petersburg (Q656)
Moscow (Q649)
Tracking: usageCategory:Pages using Wikidata property P937 (Q20117120)
See alsolocation of discovery (P189), floruit (P1317), work period (start) (P2031), work period (end) (P2032), location of creation (P1071), diplomatic mission sent (P531), headquarters location (P159), residence (P551)
Lists
Proposal discussionProposal discussion
Current uses
Total488,678
Main statement478,17997.9% of uses
Qualifier10,4552.1% of uses
Reference44<0.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “human (Q5), fictional character (Q95074), group of humans (Q16334295), notname (Q1747829), human whose existence is disputed (Q21070568), group of fictional characters (Q14514600), mythical character (Q4271324), job activity (Q192581), legendary figure (Q13002315), position (Q4164871), specialty (Q1047113), profession (Q28640), working animal (Q228534), organization (Q43229): item must contain property “instance of (P31)” with classes “human (Q5), fictional character (Q95074), group of humans (Q16334295), notname (Q1747829), human whose existence is disputed (Q21070568), group of fictional characters (Q14514600), mythical character (Q4271324), job activity (Q192581), legendary figure (Q13002315), position (Q4164871), specialty (Q1047113), profession (Q28640), working animal (Q228534), organization (Q43229)” 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/P937#Type Q5, Q95074, Q16334295, Q1747829, Q21070568, Q14514600, Q4271324, Q192581, Q13002315, Q4164871, Q1047113, Q28640, Q228534, Q43229, SPARQL
Contemporaries:
if [item A] has this property (work location (P937)) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history. (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/P937#Contemporary, 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/P937#Entity types
Scope is as main value (Q54828448), 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/P937#Scope, SPARQL
Not world value
(Help)
Violations query: SELECT ?item { ?item wdt:P937 wd:Q2. ?item wdt:P31 wd:Q5. }
List of this constraint violations: Database reports/Complex constraint violations/P937#Not world value

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

Untitled[edit]

should be used for all persons, group of persons, family, list of persons:

e.g. House of Este (Q677173) work location (P937) Este (Q34607)--Oursana (talk) 12:37, 25 July 2014 (UTC)[reply]

list of the bishops of Padua (Q1837310) work location (P937) Padua (Q617) --Oursana (talk) 09:31, 16 August 2014 (UTC)[reply]
I removed the mention the restriction to artists or creator in the English and French description. That does not have any use. Other languages should be changed too. --Zolo (talk) 16:17, 13 May 2015 (UTC)[reply]
I used it on "Jack the Ripper" .. somehow this seems odd. --- Jura 19:48, 28 October 2015 (UTC)[reply]

inverse[edit]

"location where objects were active" <-> "active objects (for this location)"? --Fractaler (talk) 13:49, 28 December 2016 (UTC)[reply]

jobs and positions[edit]

This property is meanwhile also used to indicate the work location of a job or position, e.g. librarian (Q182436)work location (P937)library (Q7075). This has a slightly different meaning than the originally proposed one to indicate the specific work location of a specific person. Should we extend the scope or delete those statements? --Pasleim (talk) 20:21, 5 March 2017 (UTC)[reply]

@Pasleim: extension is quite natural, please keep info d1g (talk) 18:15, 29 September 2017 (UTC)[reply]
 Comment this seems to mess up the constraint and the initial definition. > del
--- Jura 08:31, 1 October 2017 (UTC)[reply]
I agree with Jura1 (talkcontribslogs). Also, this sort of expansion can be dangerous, leading to situations like Marian the librarian working not in the library in River City, but in library. Peter F. Patel-Schneider (talk) 15:27, 12 November 2017 (UTC)[reply]

located in the administrative territorial entity[edit]

Requiring objects to be located in an administrative territorial entity seems bad. E.g., some people work at sea or Antarctica, like Louis Bernacchi (Q19999). Ghouston (talk) 02:49, 8 August 2018 (UTC)[reply]

Can we have instead an object constraint for class physical location (Q17334923)? Ghouston (talk) 03:41, 8 August 2018 (UTC)[reply]
May be it's better. See also this discussion: Property talk:P131#City: ATE or not ATE. --Infovarius (talk) 16:42, 9 August 2018 (UTC)[reply]
I can't even put Egypt (Q79) as a work location without the warning. OK, I'll change it. Ghouston (talk) 02:56, 2 November 2018 (UTC)[reply]
Let's try "instance or subclass of location". Ghouston (talk) 03:02, 2 November 2018 (UTC)[reply]

schools and such[edit]

Currently we have a constraint error when using a school, university or similar (including hospitals...) as 'workplace', because they are not considered as physical places. A workaround I have found is to state the school / university, etc. as the employer. However this is a bit unintuitive in some cases and even sometimes just wrong. In many countries people working in some public institutions are not considered employed by the institution ; their employer is the State, and the school / university / hospital, etc. is usually considerd as their workplace. I think a change should be introduced here. CaféBuzz (talk) 17:49, 11 July 2023 (UTC)[reply]

I can only agree with that. It should be possible for a professor to specify the university as their P937. Jan Mathys (talk) 17:11, 18 January 2024 (UTC)[reply]

Notability of a work location[edit]

How detailed is it useful to document work location? For example, many people go on official work trips, perhaps to a conference or to visit a client. Should all these be added? Or should it require some sort of permanency? If so, that would likely make most scientific field trips not fit. One way to think about it that just struck me, and which resembles how some tax authorities would look at it, would be, if the employee is expected to pay for the commute or will the company pay for it. If the first, then that is the person's work location. But if the employer pays for it, it is something out of the ordinary work location. Obviously, there could be some exceptions, as the world is complex. Perhaps a diplomat is expected to divide the work in an embassy in one city and a consulate in another, and be paid for the trips in between. Or a researcher has a regular office at the university campus in a city, but spends more time at a research facility elsewhere in the country. But should an archaeologist have each three-week excavation or a biologist every one-week excursion noted (both of which may have significant impacts on the research and the field)? And at the same time, if either of those starts turning into several months long projects, perhaps it should? What would be a good balance or rule of thumb? Ainali (talk) 07:10, 2 June 2024 (UTC)[reply]

Sabine von Mering (talk)
Ambrosia10 (talk) 12:55, 24 August 2023 (UTC) Daniel Mietchen (talk) 13:00, 24 August 2023 (UTC) Dag Endresen (talk) 13:10, 24 August 2023 (UTC) MNHNL pbraun (talk) 13:22, 24 August 2023 (UTC) AHendriksen-collecties (talk) 12:38, 25 August 2023 (UTC)[reply]
Notified participants of WikiProject Research expeditions, who may have thought on this. Ainali (talk) 07:25, 2 June 2024 (UTC)[reply]
WikiProject research expeditions has suggested using this property on research expedition items to show the locations where work has been undertaken during that expedition. See for example Q101428109 (this is currently the only research expedition item that uses the work location property in this way). The reasoning is that using this property helps distinguish these work locations from locations the expedition may just have stopped at. For example an expedition may call into a particular port to collect supplies but no research may have been undertaken at that location. The WikiProject has also used this property to give locations where a person has been collecting specimens but is NOT participating in a research expedition. Using the work location property in this way solves the issue of what to do with such data where the collecting trip is not regarded as a research expedition. The Donald Petrie Wikidata item Q5294994 has been used as an example of how to deal with this type of data. Scholarly articles about prolific collectors are often produced giving the locations and dates the collector has worked and having these work locations as well as the start and end dates of the time worked at that location as linked open data can help natural history institutions to improve data related to specimens collected by those collectors. - Ambrosia10 (talk) 08:32, 2 June 2024 (UTC)[reply]
I very much like using it on the expeditions themselves with high fidelity. I am less certain about persons. Donald Petrie (Q5294994) is interesting as it shows the potential of how much data could be added. I imagine that some scientists could have a lot of data. Or a science communicator like David Attenborough (Q183337), where we also easily could find sources of his work locations. Stepping outside of science, what do we do for politicians, who regularly travel and meet both the constituency and also other politicians? I am thinking that a general election campaign tour should not add tens of items, but perhaps City of Brussels (Q239) could be added to most prime ministers of EU member states as they are expected to do work in the European Council (Q8886)? How could we generalize what is worth adding to a person? Ainali (talk) 09:01, 2 June 2024 (UTC)[reply]
I think it comes down to whether such statements have a citation to support them and also whether someone is prepared to do this work. Taking Donald Petrie, his specimens are held in the four main herberia in New Zealand as well as multiple organisations around the world. Having this data in Wikidata can assist all these institutions in ensuring the specimen data they hold in their collection management systems is correct, this is particularly helpful if this type of data is shared with or linked to aggregators such as GBIF. The Wikidata item and its structured data can also help feed into the world wide digital extended specimen efforts. I'm thinking of the wider use cases here, and have been encouraging institutions to add this type of data to Wikidata where everyone can make use of it instead of closed, inaccessible systems, where each institution has to replicate the same effort into each of their databases. Ambrosia10 (talk) 09:33, 2 June 2024 (UTC)[reply]