Property talk:P4602

Type “human (Q5), fictional character (Q95074), animal (Q729), human head (Q3409626)”: item must contain property “instance of (P31)” with classes “human (Q5), fictional character (Q95074), animal (Q729), human head (Q3409626)” or their subclasses (defined using subclass of (P279)). (Help)

List of violations of this constraint: Database reports/Constraint violations/P4602#Type Q5, Q95074, Q729, Q3409626, hourly updated report, SPARQL

Item “sex or gender (P21)”: Items with this property should also have “sex or gender (P21)”. (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/P4602#Item P21, SPARQL

Difference with “date of birth (P569)” within range [0, 150]: the difference with property “date of birth (P569)” should be in the range from “0” to “150”. (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/P4602#Diff within range

Difference with “date of death (P570)” within range [0, 1]: the difference with property “date of death (P570)” should be in the range from “0” to “1”. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Jeanne Madden Cibroski (Q95883685), Archduke Karl Albrecht of Austria (Q79054), Peter Dodge (Q130480130)
List of violations of this constraint: Database reports/Constraint violations/P4602#Diff within range

Single best value: this property generally contains a single value. If there are several, one would have preferred rank (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/P4602#single best value, SPARQL

Qualifiers “location (P276), sourcing circumstances (P1480), age of subject at event (P3629), earliest date (P1319), latest date (P1326), reason for deprecated rank (P2241), determination method or standard (P459), refine date (P4241), time index (P4895), nature of statement (P5102), located in time zone (P421), reason for preferred rank (P7452), statement is subject of (P805), applies to part, aspect, or form (P518), object named as (P1932), object stated in reference as (P5997), agent of action (P12995)”: this property should be used only with the listed qualifiers. (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/P4602#allowed qualifiers, SPARQL

Range from “-5000-00-00T00:00:00Z” to “now”: values should be in the range from “-5000-00-00T00:00:00Z” to “now”. (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/P4602#Range

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/P4602#Scope, 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/P4602#Entity types

Citation needed: the property must have at least one reference (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/P4602#citation needed

This property is being used by: nl:Sjabloon:Infobox persoon Wikidata Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Hi @Thierry Caro:

I tried this new property on Louise de Quengo (Q20751710) who was buried in 1656, discovered and re-buried in 2015 but it cause a violation of the constraint « Difference with “date of birth (P569)” within range [0 year, 150 year] ».

What would be best: add an exception or remove this constraint? (it's not common but it's not that unusual to be re-buried and nothing forbid to have).

Cdlt, VIGNERON (talk) 17:54, 3 December 2017 (UTC)[reply]

I'd remove the constraint. It's quite common to be reburied, as you said. Thierry Caro (talk) 17:56, 3 December 2017 (UTC)[reply]

Thank you. Cdlt, VIGNERON (talk) 15:38, 4 December 2017 (UTC)[reply]

I would prefer to keep the constraint. Date of burial is often used as a proxy for date of death, if date of death is not known. date of baptism (P1636) serves similar role, as proxy for date of birth, so we have "in early childhood" part. May be this should be "date of burial or cremation soon after death", or maybe we can keep the property label shorter and just agree to use it that way. In case of Louise de Quengo (Q20751710) I would just ignore second (3rd, 4th, etc.) burial. --Jarekt (talk) 15:26, 17 January 2018 (UTC)[reply]

@Mormegil: After you changed, I get all sorts of warnings, even if they are not warranted, e.g. Hans Liebl (Q98907926). Do have an idea why that is? Thank you! --Emu (talk) 10:08, 8 January 2021 (UTC)[reply]

Before I changed it, I got warnings about mismatched units (0 years vs 18 months), so I hoped it might be fixed by unifying it to months. However, now I found months are basically not supported at all. (The implementation is too simplistic; see also a different problem with it at phab:T168379.) I’ll change the range to 550 days instead which should help, I hope. (I’d rather have 1 year there, but User:Esquilo changed that for some good reason, I hope. (Even though if it was for a single exceptional case, an exception for the constraint might be a better solution, I guess.)) --Mormegil (talk) 10:45, 8 January 2021 (UTC)[reply]

I also hope it was for a good reason, because now seven months later I have no idea what it could have been. ;-)

But I think you are right. Even if there are cases when there have been more than 12 months between death and burial, 12 months interval is reasonable. More than 12 months could just as well being be a year typo. /ℇsquilo 14:08, 8 January 2021 (UTC)[reply]

The difference affects 8 items. I’d say let’s reset the constraint to 1 year and let those 8 items show constraint violations. There are currently 34 items with even greater difference, so if somebody is going to check all those and find some part of those is correct, they can add them to the exceptions instead. --Mormegil (talk) 15:31, 8 January 2021 (UTC)[reply]

The reason must have been Göran Göransson Gyllenstierna (Q5779466) then. I have not touched any of the other objects. /ℇsquilo 16:37, 8 January 2021 (UTC)[reply]

I changed the property to allow as a qualifier, since we have entries for cemetery plots that contain multiple interments each at a different time. One tomb may contain a dozen bodies each buried at at a different time. See for example: Gould family mausoleum (Q87386922) --RAN (talk) 22:56, 18 January 2021 (UTC)[reply]

Hello, I think the properties for date of cremation should be another property. Because you often also bury after you did the cremation and the cremation is unknown than but just the date of the urn burial is known. Or how should I specify this - what is meant by the date I specify? If I now use applies to part, aspect, or form (P518) but only know the date of the urn burial and don't add an unknown date entry for the cremation-part, this leads to a false conclusion about the type of burial. I think this needs to be addressed somehow, right now this leads to diffuse data.

Best regards, Fundriver (talk) 13:38, 18 March 2021 (UTC)[reply]

Person Q109762594 died on June 9th, 1759. She was buried in June 1759, no exact date is known. I get the error message that both dates should be between 0 and 1 years. The same month is not? Since when? Roelof Hendrickx (talk) 23:18, 26 November 2021 (UTC)[reply]

Yeah, that’s the problem with the simplistic implementation of the constraint checker unable to properly handle lower precision, as I mentioned above, see phab:T168379. There is a workaround of modifying the date value so that it refers to a later part of the month (modifying just the undisplayed part of the low-precision value), keeping the precision, see my edit there. It’s definitely not a good solution, but it makes the warning go away. --Mormegil (talk) 09:18, 27 November 2021 (UTC)[reply]

Thanks very much! Roelof Hendrickx (talk) 11:06, 27 November 2021 (UTC)[reply]

Date may be in the future for fictional characters. Date may be in the future even for the real persons: once the person died, the date of the burial is announced and it is in the (near) future. That shouldn't throw a constraint warning. — Draceane ^talk_contrib. 13:52, 21 October 2024 (UTC)[reply]

So it will show a constraint warning for a couple of days. Doesn’t matter. I don’t think there is currently a way to encode a constraint of “date in the past or up to a month in the future“. IIANM. --Mormegil (talk) 14:02, 21 October 2024 (UTC)[reply]