Bean49 added a comment.
@Aklapper Why do you close it? No one addressed the reported issues. I don't
understand. Why would anyone report anything if you close it without answering?
Could you please clarify or answer my previous questions. Thanks.
TASK DETAIL
https
Bean49 reopened this task as "Open".
Bean49 added a comment.
Could someone with expertise state that understands the problem and indicate
which workaround is less worse?
1. make 1800 API requests instead of 4
2. use a very low percentage (1-15%) of downloaded data, increasi
Bean49 added a comment.
That's true, but you cannot get 500 entities at once, it remains the problem
that you have to do 1800 requests in my previous example instead of 4. Is this
not a problem?
TASK DETAIL
https://phabricator.wikimedia.org/T243138
EMAIL PREFERENCES
https
Bean49 added a comment.
What are the recommendations of stewards/maintainers/owners of the codebase
regarding the issues? Either workaround is not desirable.
TASK DETAIL
https://phabricator.wikimedia.org/T243138
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel
Bean49 reopened this task as "Open".
Bean49 added a comment.
I think this request was closed without addressing the issues reported in it.
TASK DETAIL
https://phabricator.wikimedia.org/T243138
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailp
Bean49 added a comment.
@Lydia_Pintscher It's not the case. How can you download the _P131 property
of 1800 items with only 4 requests? Either you have to do 1800 requests, or
download tons of data you use for nothing. This would not be for my
convenience, it would be better for Wikimedia
Bean49 changed the subtype of this task from "Task" to "Feature Request".
TASK DETAIL
https://phabricator.wikimedia.org/T243138
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Bean49
Cc: Bean49, Aklapper, Ralfhauser, D
Bean49 added projects: MediaWiki-extensions-WikibaseRepository, Performance
Issue.
Bean49 added a comment.
Restricted Application added a project: wmde-wikidata-tech.
Many Wikibase items have many statements. Many tasks deal with only one or
few properties. It would considerably improve
Bean49 added a comment.
You can see it here:
select * from page_props where pp_propname = 'wikibase_item' limit 100
https://quarry.wmcloud.org/query/77832
TASK DETAIL
https://phabricator.wikimedia.org/T141864
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel
Bean49 added a comment.
https://en.wikipedia.org/w/api.php?action=query=json=pageprops=Kofoworola%20Abeni%20Pratt=2
gives
{
"batchcomplete": true,
"query": {
"pages": [
{
"pageid&qu
Bean49 added a comment.
Magic words are not Wikibase client. This a Wikipedia pageprops. See T349571
<https://phabricator.wikimedia.org/T349571> for links. Could someone add the
right project and assign the task?
TASK DETAIL
https://phabricator.wikimedia.org/T141864
EMAIL PREFE
Bean49 added a subscriber: Pppery.
Bean49 added a comment.
@Pppery What would be the correct project? What project deals with the
`{{PAGEID}}` magic word? This is not about Wikidata, this is about magic words
and page properties on Wikipedia. No one seems to deal with this feature
request
Bean49 added projects: MediaWiki-Parser, ParserFunctions.
TASK DETAIL
https://phabricator.wikimedia.org/T141864
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Bean49
Cc: Bean49, Ainali, Nirmos, Bugreporter, Zppix, Steenth, Metalindustrien
Bean49 added a project: MediaWiki-extensions-Variables.
Bean49 changed the subtype of this task from "Task" to "Feature Request".
Bean49 added a comment.
I propose `{{WIKIBASEITEMID}}` magic word. Like `{{PAGEID}}`,
`{{PAGEID:`//page name//`}}`. See
14 matches
Mail list logo
