Scope is as qualifier (Q54828449): the property must be used by specified way only (Help)

List of violations of this constraint: Database reports/Constraint violations/P2241#Scope, hourly updated report, SPARQL

Tipo valore "Wikibase reason for deprecated rank (Q27949697)": This property should use items as value that contain property “instance of (P31)”. On these, the value for instance of (P31) should be an item that uses subclass of (P279) with value Wikibase reason for deprecated rank (Q27949697) (or a subclass thereof). (Help)

List of violations of this constraint: Database reports/Constraint violations/P2241#Value type Q27949697, hourly updated report, SPARQL

Allowed entity types are Wikibase item (Q29934200), Wikibase property (Q29934218), Wikibase lexeme (Q51885771), Wikibase form (Q54285143), Wikibase sense (Q54285715), Wikibase MediaInfo (Q59712033): the property may only be used on a certain entity type (Help)

List of violations of this constraint: Database reports/Constraint violations/P2241#Entity types, hourly updated report

None of account suspension (Q87406427), banned subreddit (Q65697924): value must not be any of the specified items.
Replacement property: end cause (P1534)
Replacement values: (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/P2241#none of, SPARQL

Value withdrawal of an award (Q106849510) will be automatically replaced to value withdrawn award (Q24629887). Testing: TODO list

Non-deprecated statements
Items with statements qualified by reason for deprecated rank (P2241) that are not deprecated (Help)
Violations query: SELECT ?item WHERE { hint:Query hint:optimizer "None" . ?statement pq:P2241 ?value; wikibase:rank ?rank . FILTER(?rank != wikibase:DeprecatedRank) . ?item ?p ?statement . [] wikibase:claim ?p }
List of this constraint violations: [[Wikidata:Database reports/Complex constraint violations/P2241#Non-deprecated statements|Database reports/Complex constraint violations/P2241#Non-deprecated statements]]

• Query for most common values: tinyurl.com/p5x5ug8
• Query giving the deprecated statements, too :tinyurl.com/pznls6x

Jheald (talk) 12:35, 10 November 2015 (UTC)[reply]

I added them to the list parameter in the template above, but could we convert them to URLs? --- Jura 12:38, 10 November 2015 (UTC)[reply]

Then you need a trustworthy URL-shortener. Not one that is blacklisted. Mbch331 (talk) 12:43, 10 November 2015 (UTC)[reply]

We could add the full URLs? --- Jura 12:45, 10 November 2015 (UTC)[reply]

You can do that, but it looks awful. Mbch331 (talk) 12:47, 10 November 2015 (UTC)[reply]

Awful, but searchable: https://www.wikidata.org/w/index.php?target=query.wikidata.org%2F%23&title=Special%3ALinkSearch --- Jura 12:48, 10 November 2015 (UTC)[reply]

 Done - Mbch331 (talk) 12:50, 10 November 2015 (UTC)[reply]

If you use "code>", I don't think it's searchable. I converted it to URL (feel free to revert if you really prefer). I think the template solution you once mentioned works well too. We could make a single page of them and just call one. BTW, at P569, I replaced the standard one with yours as it gives accurate results. --- Jura 12:56, 10 November 2015 (UTC)[reply]

I've created templates for the two queries. If desired, these could also be added to any other qualifier page. Jheald (talk) 13:14, 10 November 2015 (UTC)[reply]

I followed Zolo's sample and added some to Module:Property_documentation. Matěj Suchánek made a better formatted draft at Module:Property documentation/sandbox. If we could query the constraints, we could more specific ones. --- Jura 13:20, 10 November 2015 (UTC)[reply]

I have just created not been able to confirm this claim (Q21655367) to use with this property. If you are aware of a simlair item, feel free to merge them! -- Innocent bystander (talk) 09:13, 5 December 2015 (UTC)[reply]

Nice. Seems fairly generic in its wording. The main issue with values for this property seems to be that people are tempted to relate it to the item not the statement. --- Jura 09:12, 8 December 2015 (UTC)[reply]

To be clear about how and why I used it. The item about Gothenburg urban area had a claim that Rostock was it's "sister city". Since urban areas do not have sister citys, I tried to relocate that statement to Gothenburg municipality (which have sister citys). But the list on the homepage of Gothenburg municipality did not include Rostock. It is possible that the sister city-agreement has ended (not a reason to remove a statement) or the list only included Scandinavian citys (also not a reason to remove a statement). But it is also possible that it was a mistype somewhere (which could be a reason to remove the statement). I do not know which, so I deprecated it after I moved it to Gothenburg municipality. -- Innocent bystander (talk) 09:52, 8 December 2015 (UTC)[reply]

See the subclasses of this item: Wikibase reason for deprecated rank (Q27949697) (query). Tubezlob (🙋) 13:58, 11 March 2017 (UTC)[reply]

Just a easy-link. To search all items using reason for deprecated rank (P2241):

SELECT ?item ?itemLabel WHERE {
  ?item wdt:P31 wd:Q27949697.
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
}

--Kanashimi (talk) 09:21, 25 January 2022 (UTC)[reply]

Items and subclasses from a product classification. The classification includes "n.e.c." or "other" subclasses:

• Stuff
  • Stuff, type A
  • Stuff, type B
  • Stuff, the other types

Using those subclasses in Wikidata makes the output of "Wikidata generic tree" less useful, because that tool simply prefers deeper levels and can't see which one has a useful meaning, and which one is just metadata. In the original classifications, the class groups its subclasses because the classification has a limited amount of levels available and the levels themselves have a meaning (some items have multiple codes seemingly just to reach the deepest level). In Wikidata (that imports from multiple classifications), that item simply holds the imported stuff together to make skips to the parent item less confusing (you can't just say it's according to the source classification).

So I started giving the "subclass: Other" statements a deprecated rank. How should the reason be named?

--AVRS (talk) 09:12, 16 November 2016 (UTC)[reply]

@AVRS: If the goal is to make Wikidata generic tree more efficient, the solution might be to make a feature request to be able to filter classes by classifying them into Metaclasses. Just an idea. author  TomT0m / talk page 10:51, 16 November 2016 (UTC)[reply]

There is some discussion about the use of this qualifier at [1] (notably). It starts out on some other issue.
--- Jura 15:57, 14 August 2016 (UTC)[reply]

Please weigh in there. Thanks! Swpb (talk) 20:13, 12 December 2019 (UTC)[reply]

From the discussion at Wikidata:Property_proposal/reason_for_normal_rank, I take it that we should probably use "deprecated rank" instead of "deprecation" in label and description.

This especially as the one for preferred rank is called "reason for preferred rank" (P7452). --- Jura 14:03, 17 December 2020 (UTC)[reply]

It seems counterintuitive to have Wikidata property example for properties (P2271) as reason for preferred rank (P7452). When adding reason for preferred rank (P7452) by typing, "Reason for pref...", one always get the reason for deprecation which is the opposite of the intent. Is there value is adding this property example to the reason for deprecation? Trilotat (talk) 18:07, 13 February 2022 (UTC)[reply]

@Gymel, Gymnicus, HvW, H005, Mbch331, Succu: Momentan heißt diese Eigenschaft „Grund für die Zurückweisung“, Wikibase reason for deprecated rank (Q27949697) beinhaltet in seiner Bezeichnung momentan ebenfalls „Zurückweisung“, aber in der Benutzerschnittstelle lautet es „Deprecated rank“ und in Help:Ranking/de „Aussage hat missbilligten Rang“. Sollte das nicht angeglichen werden, um Verwirrung zu vermeiden? Nw520 (talk) 23:57, 4 December 2023 (UTC)[reply]

Mir gefällt ja "missbilligter Rang" bei der Werteinstufung schon nicht, das wäre aber eine noch weitreichendere Änderung. Sieht aus wie eine "Wörterbuch-Übersetzung" ohne Sinnverständnis. Bevor noch jemand Lust bekommt, daran zu rütteln, wäre eine Vereinheitlichung auf "missbilligt" vielleicht ganz gut. Da hängt übrigens auch noch die list of Wikidata reasons for deprecation (Q52105174) dran. Gruß -- HvW (talk) 00:33, 5 December 2023 (UTC)[reply]

Ich bin mit den derzeitigen deutschen Bezeichnungen auch überhaupt nicht glücklich. Es ist allerdings auch schwierig, eine passende Übersetzung für das englische "deprecated" zu finden. "Zurückweisung" oder "Ablehnung" halte ich auf jeden Fall für unglücklich, denn wenn etwas zurückgewiesen würde, dann sollte es gar nicht mehr auftauchen. Es soll aber ja gerade für Aussagen dienen, die man nicht komplett zurückweist, sondern nur für weniger verlässlich/glaubwürdig hält. Auch "Missbilligung" trifft es nicht. Aus meiner Sicht wären "Herabstufung" oder "Herabsetzung" besser geeignete Übersetzungen. Wäre sehr dafür, das in allen relevanten Eigenschaften und Listen einheitlich so zu benennen. -- H005 (talk) 17:17, 5 December 2023 (UTC)[reply]

 HvW: Ändern ließe sich die Bezeichnung in der Benutzerschnittstelle über das TranslateWiki; sollte dann aber noch einmal mindestens im Forum zur Debatte gestellt werden. Nw520 (talk) 21:19, 5 December 2023 (UTC)[reply]

Ich bin mit der aktuellen Bezeichnung. Also ich finde „Zurückweisungsgrund“ und „Grund für die Zurückweisung“ deutlich besser als „Grund für die Missbilligung“. --Gymnicus (talk) 09:40, 6 December 2023 (UTC)[reply]