Uzume added a comment.
This seems like a more generalized version of T99899.TASK DETAILhttps://phabricator.wikimedia.org/T185313EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: UzumeCc: Uzume, Aklapper, Ghuron, Lahi, Gq86, GoranSMilovanovic, QZanden
Uzume added a comment.
@Tacsipacsi It sounds like you want: mw.wikibase.getEntityIdForTitle(mw.title.getCurrentTitle().subjectPageTitle.prefixedText)
Is there some reason why that does not work for you?TASK DETAILhttps://phabricator.wikimedia.org/T123196EMAIL PREFERENCEShttps
Uzume added a comment.
We need a resolveEntityId(eid) that returns nil when there is no such entity. It should also handle redirects from merged items, etc. (also solving T157868). It could also potentially work like resolvePropertyId and return a valid entity ID when given an unambiguous label
Uzume added a comment.
In T182147#3815415, @thiemowmde wrote:
A boolean entityExists (T143970).
Use case: Currently, I see a lot of code that does if getEntity( … ) then, which is super-expensive for no reason. The cheapest workaround that currently exists is getEntityUrl, but thats awkward
Uzume added a comment.
I have no issue with discussion and I believe this an adequate forum for such a discussion. My point was your requests are significantly lacking (and need discussion and focus) before they can be considered for possible implementation.
We already have many of the facilities
Uzume added a comment.
I agree. This request is poorly specified. For one, labels, descriptions, and sitelinks are not properties. Also how should these property values be handled? There are many property data types where the data is not necessarily a single scalar value. Also property claims can
Uzume added a comment.
In T185313#3916435, @Ghuron wrote:
Well, although I can some similarities between this one and T99899, I believe there are different use cases involved. Lookup for external identifier is mostly needed in _javascript_ (e.g. notify user that wikidata instance with the same
Uzume added a comment.
Does entityExists properly handle redirects (e.g., merged entities) and if so how do we get the entity ID we are redirected to?
For example, what does mw.wikibase.entityExists(Q404) yield? and how do I find out that refers to Q395?
ThanksTASK DETAILhttps
Uzume added a comment.
T143970 seems like it was recently closed but I still think we need a resolveEntityId(eid) that returns nil when there is no such entity but redirects for merged items, etc. It could also potentially work like resolvePropertyId and return a valid entity ID when given
Uzume added a comment.
This seems partially redundant with T157868, however I am not sure about mw.wikibase.entity.formatPropertyValues. I agree that Wikibase parser functions like {{#property:…}} should probably properly redirect, however, from Scribunto I would rather see mw.wikibase.getEntity
Uzume added a comment.
Perhaps this ticket is old but it seems to me we already have such filters with mw.wikibase.getBestStatements and mw.wikibase.getAllStatements. Of course those do not pull multiple properties in a single execution but they do filter to a single property without pulling
Uzume added a comment.
This might get resolved by T112658.TASK DETAILhttps://phabricator.wikimedia.org/T157868EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: UzumeCc: Uzume, Salgo60, Larske, hoo, matej_suchanek, Aklapper, Lahi, Gq86, GoranSMilovanovic
Uzume added a comment.
This should probably be handled more generally along the lines of T157868 and T127169. This is exactly why I felt it was better to implement a mw.wikibase.resolveEntityId that returns the resolved eid or nil if it does not exist rather than just the true or false
Uzume added a comment.
The might get resolved by T112658, at least for the parser function.TASK DETAILhttps://phabricator.wikimedia.org/T127169EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: UzumeCc: Uzume, Laddo, TomT0m, aude, Aklapper, Lydia_Pintscher
Uzume added a comment.
FYI: I made a comment on T185313: mw.wikibase.entity:getBacklinks (lua API in
wikibase client) <https://phabricator.wikimedia.org/T185313> about the
possibility creating a query service that stores results in Tabular Data (which
is available at page render ti
Uzume added a comment.
I agree that Special:WhatLinksHere is probably not the right semantics for
this request, `haswbstatement` might be better semantics, however, those need
to be well defined so people know if in fact they would address this request.
For example, I assume this would
Uzume added a comment.
I disagree. The availability of ones password does not fall into "security by
obscurity" because it is, in general, not obscurely available from other
sources (and if it is, that is an entirely different type of security issue).
The point being, secur
Uzume added a comment.
I do not think this is a good idea. This amounts to security through
obscurity <https://www.wikidata.org/wiki/Q133735> and in general is not a good
practice. The same data could be found in a number of other ways (e.g., api.php
which would be even more
Uzume added a comment.
@jeblad: This seems like a problem:
- https://gerrit.wikimedia.org/r/51826 Merged rEWBA0e1ead00bb01: (Bug 45607)
Add a callback for the hook for reordering of special pages
<https://phabricator.wikimedia.org/rEWBA0e1ead00bb01d1438d87f05cb93212a5d7c0412c>
-
Uzume added a comment.
The issue becomes how to represent multiple edition links in Mediawiki
toolbars across multiple WMF wikis across their projects. Currently, as
implemented via WD sitelinks, we only allow one link per wiki per project per
WD item. This is in part owning to the limited
Uzume added a comment.
HomePhabricator
No notifications.
Account Menu
Favorites Menu
Create Task
Maniphest
T138332 <https://phabricator.wikimedia.org/T138332>
interwiki links to/from Multilingual Wikisource
Open, MediumPublic
Edit Task
Edit Related
Uzume added a comment.
@beleg_tal: I agree with your statements, especially "interwiki system needs
to be flexible enough to accommodate different data models", however, I do not
think this is an inherently Wikidata issue.
For example: Wikitionary has a very different m
Uzume added a comment.
I am against having multiple site links per wiki per WD item. On the other
hand, I am not against having a translation system for these sitelinks and it
might be good to have some method to automatically prefix item sitelink links
to multilingual wikis using something
Uzume raised the priority of this task from "Low" to "Medium".
Uzume updated the task description.
TASK DETAIL
https://phabricator.wikimedia.org/T138332
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Uzume
Cc: beleg_tal, H
Uzume updated the task description.
TASK DETAIL
https://phabricator.wikimedia.org/T138332
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Uzume
Cc: Uzume, beleg_tal, Hsarrazin, Ankry, MJL, Lea_Lacroix_WMDE, Jarekt,
Ash_Crow, jhsoby, PokestarFan
Uzume added a comment.
I think we can remove OldWikisource from this task as concepts from this task
that apply to it are now adequately covered by:
- T138332: interwiki links to/from Multilingual Wikisource
<https://phabricator.wikimedia.org/T138332>
- T206426: Storing mu
Uzume added a comment.
I am not sure this is a good idea or not (its seems like there maybe a few
proposals) and I am against implementing this in Wikidata beyond how it already
implements things (multiple linked records with one sitelink per wiki per
item). That said, I see no issue
Uzume added a comment.
In T192462#5461691 <https://phabricator.wikimedia.org/T192462#5461691>,
@Ladsgroup wrote:
> So quick question from people who need this (ping @Uzume and @eranroz):
Should mw.wikibase.entityExists('Q123') return true in case Q123 is redirect
all the tim
28 matches
Mail list logo
