Change Details

Currently, if wbgetsuggestions is used on an item which have more than 15 different statements, it will not give any property suggestions. For instance, https://www.wikidata.org/w/api.php?action=wbsgetsuggestions&entity=Q42 I want to tweak wbgestsuggestions to give recommended properties even if they have existed in the item, so that I know which properties that are relevant to that item. The information about relevant properties allows me to develop a feature for revscoring (https://www.mediawiki.org/wiki/ORES) which signals item completeness. The feature generates completeness score by dividing number of properties that an item contains with number of relevant properties that this specific item should have based on the wbsgetsuggestions API. For instance, suppose there is an item about some person which only contains 2 statements, that are, "instance of: human" and "occupation: actor". Assuming the change on this ticket has been implemented, when we use the API on this item, the API returns properties "instance of", "sex&gender", "date of birth", "place of birth", and "occupation". In this case, the score would be 0.4. This score comes from 2/5, where 2 is the number of suggested properties that the item already contains, and 5 is the total number of items that are suggested by the API. Concerning to the result limit in the API, we plan to do "continuation" to workaround the limit that is imposed by the API.

Currently, if wbgetsuggestions is used on an item which have more than 15 different statements, it will not give any property suggestions. For instance, https://www.wikidata.org/w/api.php?action=wbsgetsuggestions&entity=Q42 I want to tweak wbgestsuggestions to give recommended properties even if they have existed in the item, so that I know which properties are //most// relevant to that item. The information about relevant properties allows me to develop a feature for revscoring (https://www.mediawiki.org/wiki/ORES) which signals item completeness. The feature generates completeness score by dividing number of properties that an item contains with number of relevant properties that this specific item should have based on the wbsgetsuggestions API. For instance, suppose there is an item about some person which only contains 2 statements, that are, "instance of: human" and "occupation: actor". Assuming the change on this ticket has been implemented, when we use the API on this item, the API returns properties "instance of", "sex&gender", "date of birth", "place of birth", and "occupation". In this case, the score would be 0.4. This score comes from 2/5, where 2 is the number of suggested properties that the item already contains, and 5 is the total number of items that are suggested by the API. Concerning to the result limit in the API, we plan to do "continuation" to workaround the limit that is imposed by the API.

Currently, if wbgetsuggestions is used on an item which have more than 15 different statements, it will not give any property suggestions. For instance, https://www.wikidata.org/w/api.php?action=wbsgetsuggestions&entity=Q42 I want to tweak wbgestsuggestions to give recommended properties even if they have existed in the item, so that I know which properties that areare //most// relevant to that item. The information about relevant properties allows me to develop a feature for revscoring (https://www.mediawiki.org/wiki/ORES) which signals item completeness. The feature generates completeness score by dividing number of properties that an item contains with number of relevant properties that this specific item should have based on the wbsgetsuggestions API. For instance, suppose there is an item about some person which only contains 2 statements, that are, "instance of: human" and "occupation: actor". Assuming the change on this ticket has been implemented, when we use the API on this item, the API returns properties "instance of", "sex&gender", "date of birth", "place of birth", and "occupation". In this case, the score would be 0.4. This score comes from 2/5, where 2 is the number of suggested properties that the item already contains, and 5 is the total number of items that are suggested by the API. Concerning to the result limit in the API, we plan to do "continuation" to workaround the limit that is imposed by the API.