Property talk:P1661

From Wikidata
Jump to navigation Jump to search

Documentation

Alexa rank
the website's Alexa ranking with "point in time" (P585) as a qualifier for each value
[create Create a translatable help page (preferably in English) for this property to be included here]
Units: “novalue”: value unit must be one of listed. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1661#Units, hourly updated report
Range from “1” to “20000000”: values should be in the range from “1” to “20000000”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1661#Range, hourly updated report
Required qualifier “point in time (P585): this property should be used with the listed qualifier. (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/P1661#mandatory qualifier, SPARQL
Item “official website (P856): Items with this property should also have “official website (P856)”. (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/P1661#Item P856, SPARQL
Type “website (Q35127): item must contain property “instance of (P31)” with classes “website (Q35127)” 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/P1661#Type Q35127, SPARQL
Allowed entity types are Wikibase MediaInfo (Q59712033), 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/P1661#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/P1661#Scope, SPARQL

Discussion[edit]

Not just for the current alexa rating[edit]

This property should have point in time (P585) as a qualifier for each value. Many different Alexa ratings can be recorded, each with a date. The current rating (and only the current rating) should be marked as preferred. Description changed to match this. 86.6.111.107 22:30, 9 January 2015 (UTC)[reply]

Which Alexa rank to use?[edit]

While impelementing a bot for automatically retrieving the Alexa rank I came across the question which rank/value from Alexa to use. First there is the Alexa ranking i.e. https://www.alexa.com/siteinfo/imdb.com which displays two main pieces of information/data to be considered: "Global Rank" (57) and "Rank in United States" (29). Intuitively I would take the "Global Rank" value. [[File:Alexa imdb ranking.jpg|thumb|Alexa rank for imdb.com]]

Second there is the Alexa XML API i.e. http://data.alexa.com/data?cli=10&url=imdb.com which returns the following XML

<ALEXA VER="0.9" URL="imdb.com/" HOME="0" AID="=" IDN="imdb.com/">
 <SD>
  <POPULARITY URL="imdb.com/" TEXT="57" SOURCE="panel"/>
  <REACH RANK="64"/>
  <RANK DELTA="+0"/>
  <COUNTRY CODE="US" NAME="United States" RANK="29"/>
 </SD>
</ALEXA>

Asides from the corresponding "Global Rank" (TEXT="57") as well as the "United States" (RANK="29") the API also returns the value "REACH RANK="64" and "RANK DELTA="+0".

My questions here are:

1. Which value from the API response matches the one expected to be associated with {P|1661}?

2. Would it make sense to define/create subproperties for the other values, i.e. "Alexa Rank for United States" or something similar?

Thanks for your input. --Tozibb (talk) 21:44, 17 October 2017 (UTC)[reply]

@Tozibb: I think this should only deal with the Global Rank/Popularity measure (57) (and possibly the country-specific ones with qualifiers, but I don't think they're used as much in Wikipedia articles), since this is the meaning of the Wikidata property. The other ones are probably out of the scope of this property and new ones should be made if they are to be added, although if you think they're useful (I don't think they are, but others might) you could save them for later in an offline database so they can be uploaded if a new property is made. Jc86035 (talk) 07:34, 18 October 2017 (UTC)[reply]
@Tozibb:, hello! How is the situation with Alexa-updating bot? Wikisaurus (talk) 18:55, 10 October 2018 (UTC)[reply]

Reason for remove type constraint "website"[edit]

@Palotabarát:An operator system ,a brand ,a department of government could have their own website, and the site will get its Alexa rank if it is popular enough. But these website seldom have their own wikidata entry . --Jingkaimori (talk) 08:45, 7 October 2020 (UTC)[reply]

Hello Jingkaimori! If it is not a website, you do not need to indicate the Alexa rank, as Alexa does not refer to a brand or system, but only to the website. So the type constraint is correct, stay with the property. Thanks for the message! Palotabarát (talk) 08:58, 7 October 2020 (UTC)[reply]

similar values[edit]

point in time (P585) and archive date (P2960) seem to have similar values, which should be used?

Alexa to be retired 2022-05-01[edit]

See Alexa end of Service Notice. Should Alexa (P1661) be replaced by some new property, for example based on Similarweb? See Wikidata:Property_proposal/Similar_web_ranking. Tomastvivlaren (talk) 17:02, 30 March 2022 (UTC)[reply]

Property could probably be deprecated. HapHaxion (talk / contribs) 16:13, 2 April 2024 (UTC)[reply]

Sources from archive.org[edit]

Thanks to Internet Archive (Q461) we have backups of top sites:

Jklamo (talk) 18:17, 21 December 2022 (UTC)[reply]