Tpt created this task.
Tpt claimed this task.
Tpt added a subscriber: Tpt.
Tpt added a project: MediaWiki-extensions-WikidataClient.
Tpt changed Security from none to none.
TASK DESCRIPTION
If there is a link to Wikidata in the item linked to the page, it should be
displayed in the other
Tpt claimed this task.
Tpt set Security to none.
TASK DETAIL
https://phabricator.wikimedia.org/T73344
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign
username.
To: Tpt
Cc: wikidata-bugs, Lydia_Pintscher, Jaredzimmerman-WMF, Tpt, Wikidata
Tpt claimed this task.
Tpt set Security to none.
TASK DETAIL
https://phabricator.wikimedia.org/T73344
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign
username.
To: Tpt
Cc: wikidata-bugs, Lydia_Pintscher, Jaredzimmerman-WMF, Tpt, Wikidata
Tpt created this task.
Tpt added a subscriber: Tpt.
Tpt added projects: MediaWiki-extensions-WikibaseRepository, Wikidata.
Tpt changed Security from none to none.
TASK DESCRIPTION
It would be nice to be able to input today in the time edit interface in
order to get today date. It would
Tpt created this task.
Tpt added a subscriber: Tpt.
Tpt added a project: MediaWiki-extensions-WikibaseRepository.
TASK DESCRIPTION
A lot of people use URLs like http://www.wikidata.org/wiki/Q42 as URI of
Wikidata entities instead of http://www.wikidata.org/entity/Q42 because they
are used
Tpt added a subscriber: Tpt.
TASK DETAIL
https://phabricator.wikimedia.org/T73992
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign
username.
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Tpt
Cc
Tpt added a subscriber: Tpt.
Tpt added a comment.
Some Wikipedias and Wikisources already use a Lua module for Authority Control
template. Using it also in Commons may be interesting:
https://en.wikipedia.org/wiki/Module:Authority_control
TASK DETAIL
https://phabricator.wikimedia.org/T89598
Tpt added a subscriber: Tpt.
TASK DETAIL
https://phabricator.wikimedia.org/T85181
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign
username.
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: GWicke
Tpt added a subscriber: Tpt.
TASK DETAIL
https://phabricator.wikimedia.org/T73406
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign
username.
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Tpt
Cc
Tpt added a subscriber: Tpt.
TASK DETAIL
https://phabricator.wikimedia.org/T67397
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign
username.
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Tpt
Cc
Tpt created this task.
Tpt added a subscriber: Tpt.
Tpt added projects: MediaWiki-extensions-WikibaseRepository, Wikidata.
Herald added a subscriber: Aklapper.
TASK DESCRIPTION
The URLs managed by the URL datatype should be normalized in order to allow
to compare them easily. For example, http
Tpt closed this task as Invalid.
Tpt claimed this task.
Tpt added a comment.
Issue created on GitHub: https://github.com/google/primarysources/issues/52
TASK DETAIL
https://phabricator.wikimedia.org/T107080
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences
Tpt added a comment.
I am myself not against a move of all these libs to Gerrit or Phabricator as I
already have to use these tools. But I believe that if we move some of these
libs out of GitHub we will maybe miss contributions of external users that may
use this libs for other use cases than
Tpt added a subscriber: Tpt.
TASK DETAIL
https://phabricator.wikimedia.org/T99895
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Lucie, Tpt
Cc: Tpt, Lydia_Pintscher, Bugreporter, Aklapper, daniel, Wikidata-bugs, aude,
Malyacko, P.Copp
Tpt created this task.
Tpt added a subscriber: Tpt.
Tpt added projects: Wikidata, MediaWiki-extensions-WikibaseClient.
Herald added a subscriber: Aklapper.
TASK DESCRIPTION
On multilingual wikis like commons or Wikidata, link to wikis in the user
language instead of linking to English wikis
Tpt added a comment.
> This is already done by the wikis with their own JS/CSS, right?
I was not aware of it. Could you link to an example, please?
TASK DETAIL
https://phabricator.wikimedia.org/T73887
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferen
Tpt added a comment.
@Romaine You could maybe do just like Russian Wikipedia or the French
Wikisource and use the Wikibase other project sidebar as a basic and add your
additional links to it. With that nlwiki would have a basic sidebar for without
JavaScript readers and you would be able
Tpt added a comment.
> So basically: opt-in or opt-out?
What we could do is a middle way: notify the projects that if they do not ask
to opt-out before this specific date the other project sidebar will be enable
by default for all user.
We should also make clear that the beta feat
Tpt created this task.Tpt added projects: MediaWiki-extensions-WikibaseRepository, Wikidata, Wikibase-DataModel-Serialization.Herald added subscribers: Zppix, Aklapper.
TASK DESCRIPTIONEmpty containers like the ones for descriptions/aliases should be serialized as empty object "{}" and
Tpt edited the task description. (Show Details)
EDIT DETAILSEmpty containers like the ones for descriptions/aliases should be serialized as empty object "{}" and not empty array "[]" in order to ease the deserialization process.Empty containers like the ones for descrip
Tpt created this task.
Herald added a subscriber: Aklapper.
Herald added projects: Wikidata, Discovery.
TASK DESCRIPTION
When an ASK query is done no output is displayed and the "Running query..."
banner stays even if the query succeed
Examples:
- true: http://tinyurl.c
Tpt created this task.Tpt added projects: Wikidata, MediaWiki-extensions-WikibaseClient.Herald added a subscriber: Aklapper.
TASK DESCRIPTIONIt would be nice to have a function that allows to retrieve an entity (or just its id) for given page in the current wiki (and maybe also from pages from
Tpt added a comment.
This is not impossible but will need further investigation, finding the IDs of the Index: namespace on all Wikisources, changing the database structure and repopulating it, before finally deploying Cognate.
An other possible way of solving this issue is to move forward
Tpt added a comment.
To summary the current state of the work on this task:
The plan is to have at least one function mw.wikibase.getEntityIdForTitle( pageTitle ) -> string|null that returns the entity id of the item related to the page on the current wiki with for title pageTi
Tpt added a comment.
No the syntax should not be tied to "current wiki", as this makes it of little use for Commons, Wikisource, etc. There should be alternative syntax mw.wikibase.getEntityIdForTitle( pageTitle, globalSiteId ) -> string|null with globalSi
Tpt added projects: Wikisource, Wikidata.
TASK DETAILhttps://phabricator.wikimedia.org/T180304EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: TptCc: Aklapper, Tpt, Lahi, GoranSMilovanovic, QZanden, Bodhisattwa, Samwilson, Yann, Wikidata-bugs, aude, jayvdb
Tpt updated the task description. (Show Details)
CHANGES TO TASK DESCRIPTION...It could be implemented using the OtherProjectsSidebarHook inside of the "Wikisource" extension that is not yet deployed or inside of the WikimediaBadges extension (just like what is done for Commons categor
Tpt created this task.Tpt added projects: Wikidata, Wikisource.Herald added a subscriber: Aklapper.
TASK DESCRIPTIONWikisources pages are connected using sitelinks to the edition items of Wikidata and Wikipedia articles to the work items. The edition item is connected with P629 to the work item
Tpt added a comment.
I'm fine with doing this and I believe it should be done in the same way as Commons so we have consistency.
Yes, it should be implemented the same way. About the location, are you more in favor of doing it in the WikimediaBadges extension and not in a "Wikisource"
Tpt added a comment.
To summary, currently mw.wikibase.getEntityIdForTitle allows to retrieve the id of the item connected to a page of the current wiki from its title as a string.
The improvement paths I see are:
Allow the parameter to be a mw.title.Title object
Allow to retrieve the item id
Tpt added a comment.
A hacky way to do it is maybe to create fake "sites" per languages. We would for example have amiincubatorwiki would be a fake site that could be used for sitelink that have exactly the same configuration as the one of incubatorwikiTASK DETAILhttps://phabricator.wik
Tpt added a subtask: T195043: [Task] Implement RDF serialization for lexemes.
TASK DETAILhttps://phabricator.wikimedia.org/T160259EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: TptCc: Lucas_Werkmeister_WMDE, Aklapper, Ladsgroup, Lahi, Gq86, GoranSMilovanovic
Tpt renamed this task from "[Task] Implement RDF serialization for lexemes" to "[Task] Implement RDF serialization for lexemes and forms".
TASK DETAILhttps://phabricator.wikimedia.org/T195043EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To:
Tpt added a parent task: T160259: [Story] RDF for Lexemes, Forms and Senses.
TASK DETAILhttps://phabricator.wikimedia.org/T195043EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: TptCc: Aklapper, Tpt, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer
Tpt created this task.Tpt added a project: Lexicographical data.Herald added a subscriber: Aklapper.Herald added a project: Wikidata.
TASK DESCRIPTIONRDF serialization should be implemented in WikibaseLexeme in LexemeRdfBuilderTASK DETAILhttps://phabricator.wikimedia.org/T195043EMAIL
Tpt created this task.Tpt added projects: DataValues, Wikidata.Herald added a subscriber: Aklapper.
TASK DESCRIPTIONManipulating Wikidata complex values (GlobeCoordinates, Times, Quantities...) in Lua modules is painful. It would be nice to provide a good Lua library making easy to parse
Tpt added a comment.
I have made some prototypes here:
GlobeCoordinate: https://test2.wikipedia.org/wiki/Module:GlobeCoordinate
Time: https://test2.wikipedia.org/wiki/Module:Time
TASK DETAILhttps://phabricator.wikimedia.org/T195070EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel
Tpt created this task.Tpt added a project: MediaWiki-extensions-WikibaseClient.Herald added a subscriber: Aklapper.Herald added a project: Wikidata.
TASK DESCRIPTIONIf Kartographer is available Wikibase Client should use the tag to do globe coordinates rendering if the globe is earth.TASK
Tpt created this task.Tpt added a project: Lexicographical data.Herald added a subscriber: Aklapper.Herald added a project: Wikidata.
TASK DESCRIPTIONCalls to Special:EntityData are failing when called with form id. See e.g. https://wikidata-lexeme.wmflabs.org/index.php/Special:EntityData/L15-F1
Tpt added a subscriber: daniel.Tpt added a comment.
@daniel Do you think that the ontology terms specific to lexemes should live in the same namespace and ontology definition file as the other Wikibase terms or should we create a new namespace?TASK DETAILhttps://phabricator.wikimedia.org
Tpt created this task.Tpt added projects: Wikidata, Wikidata-Query-Service.Herald added a subscriber: Aklapper.Herald added a project: Discovery.
TASK DESCRIPTIONNow that the Wikibase ontology is stable we should drop the "-beta" component inside of the URIs. The vocabulary prefix shoul
Tpt added a project: Wikidata-Query-Service.Tpt added a comment.Herald added a project: Discovery.
why not just http://wikiba.se/ontology# ?
If we do that it raises multiple concerns:
It does not solve the name clash problem you mentioned earlier if two extensions want to create the same class
Tpt added a comment.
The full list of terms we have to define is:
Classes:
wikibase:Lexeme
wikibase:Form
wikibase:Sense
These 3 classes are direct mapping of the entity types so they should not cause name clash with other Wikibase extensions.
Properties:
wikibase:lexicalCategory
Tpt added a comment.
Not sure if you are proposing prefix as http://wikiba.se/lexeme/ontology/ or as http://wikiba.se/lexeme/ontology#.
Sorry, I was also thinking of http://wikiba.se/lexeme/ontology# but forgot the #.
Well, since wikiba.se site is not related to any specific Wikidata install
Tpt added a comment.
I have updated the draft of RDF implementation change: https://gerrit.wikimedia.org/r/c/433953
It uses the existing namespace for Lexemes specific terms but provides a new ontology file which URI is http://wikiba.se/lexeme/ontology# (but it could be easily changed)TASK
Tpt added a comment.
Ok for the file. For the canonical namespace URI should we use something like "http://wikiba.se/ontology-lexeme#" to have something similar to "http://wikiba.se/ontology-beta#"? Or maybe "http://wikiba.se/lexeme/ontology#"? Should we also use
Tpt added a comment.
There is still to implement output of forms statements when the RDF representation of a lexeme is requested (i.e. Special:EntityData/L42.ttl) and the schema:inLanguage relation for lexemes.TASK DETAILhttps://phabricator.wikimedia.org/T195043EMAIL PREFERENCEShttps
Tpt added a comment.
I have started a draft of mapping of the Lexeme DataModel to RDF: https://www.mediawiki.org/wiki/Extension:WikibaseLexeme/RDF_mapping
I have left some comments for different possible mappings of each element of the data model. I have focused on matching when relevant
Tpt added a comment.
I don't agree with the goal of this ticket: it is useful to have buttons on claims for two use cases:
When the claim is good but references come from a not authoritative website and, so, the user prefers not to add it. I believe it would be better add it back in order
Tpt added a comment.
@Rical
Erreur Lua dans Module:Central-s-fr à la ligne 1709 : attempt to index global 'wikibase' (a nil value).
I do not see the relation between this error and the topic of this task. The function getEntityIdForTitle is in the mw.wikibase table and not the wikibase table
Tpt added a comment.
I just started to implement a simple GraphQL wrapper on top of the Wikibase API in order to see how it could be implemented in practice. It currently maps most of the PHP DataModel structures with an interface similar to the one of the JSON API and provides some demo queries
Tpt added a comment.
There is still one feature missing: outputting statements on form and senses when the RDF representation of a lexeme is required (e.g. on Special:EntityData/L12.nt).TASK DETAILhttps://phabricator.wikimedia.org/T195043EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings
Tpt added a comment.
Is https://gerrit.wikimedia.org/r/449718 covering this?
Yes, I put the wrong task id in the commit message.TASK DETAILhttps://phabricator.wikimedia.org/T200901EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: TptCc: gerritbot
Tpt added a comment.
Also, I understand it's still disabled on both wikidata and test.wikidata.
It seems to be enabled now : https://www.wikidata.org/entity/L42.ntTASK DETAILhttps://phabricator.wikimedia.org/T195043EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences
Tpt added a subtask: T200901: [Task] Implement RDF serialization for senses.
TASK DETAILhttps://phabricator.wikimedia.org/T160259EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: TptCc: Smalyshev, Lucas_Werkmeister_WMDE, Aklapper, Ladsgroup, Mringgaard, Lahi
Tpt added a parent task: T160259: [Story] RDF for Lexemes, Forms and Senses.
TASK DETAILhttps://phabricator.wikimedia.org/T200901EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: TptCc: Tpt, Mringgaard, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer
Tpt created this task.Tpt added projects: Wikidata, Lexicographical data.
TASK DESCRIPTIONRDF serialization of senses should be implemented as specified in https://www.mediawiki.org/wiki/Extension:WikibaseLexeme/RDF_mapping#SenseTASK DETAILhttps://phabricator.wikimedia.org/T200901EMAIL
Tpt added a comment.
Indeed the set of property and their datatypes is very static and cachable so we could use them as keys of a StatementByProperty object and then have StringStatement, StringSnak... types. The object would just be huge and maybe raise some performance problems of the various
Tpt added a comment.
@dbarratt Thank you for planning to work on Wikibase+GraphQL.
The performance problem we face seems very standard, I believe it is the N+1 problem.
The standard way to solve it is to use the DataLoader utility. The original Facebook implementation is here: https://github.com
Tpt added a comment.
In T173214#4511651, @dbarratt wrote:
In T173214#4457079, @Tpt wrote:
For statement filtering by qualifier a good solution is maybe to add an extra parameter "hasStatement" to the statements field and give to it a value of type SnakInput (a GraphQL input type
Tpt added a comment.
With that.. I think it would be best if we moved your code to a new "graphql" repo, host the GraphQL server on a Cloud VPS, and then rewrite it in _javascript_ (node.js) so it's as fast as it can be. If it gets enough usage we can talk about moving it onto productio
Tpt added a comment.
I would wait for addition of proper statement serialization that is tracked by T195043.TASK DETAILhttps://phabricator.wikimedia.org/T200901EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: TptCc: gerritbot, Lydia_Pintscher, Tpt, Mringgaard
Tpt added a comment.
@Tpt so it looks like right now you can't get a datavalue or recursively call item from a statement. I added a sample query to the task description.
It's actually possible:
Example with the string data type: https://tools.wmflabs.org/tptools/wdql.html?query=%7B%0A%20
Tpt added a comment.
Thank you!
Is there any reason this can't be used where it is for now? (I mean ideally it would be in production somewhere).
It could definitely be used now but without any stability guaranties. The GraphQL query resolution is a bit heavy because it makes a lot of requests
Tpt added a comment.
I just did a quick computation of such ratios: https://docs.google.com/spreadsheets/d/1o4zNWLesoe4OSLmfQsILW0ChprIqoP8ISVS3k3vTc-E/edit?usp=sharing
There are two spreadsheets: one talking only about claims (i.e. without taking care of references) and one only about statements
Tpt added a comment.
I have made a change for the Wikisource extension (the CI is currently broken because the dependency on Wikibase is not setup yet). Having this feature there has two advantages:
Do not require a configuration parameter to enable/disable this feature. We probably want it only
Tpt added a project: Wikisource.
TASK DETAILhttps://phabricator.wikimedia.org/T207142EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: TptCc: Amire80, Aklapper, Nandana, JKSTNK, Lahi, PDrouin-WMF, Gq86, E1presidente, Ramsey-WMF, Cparle, Anooprao, SandraF_WMF
Tpt added a comment.
So you're not really asking for a change in the JSON-LD, you're asking for wikidata to only emit a single entity on the /entity/* endpoint -- and that would/could apply to all the different representations using the purtle backend. That's not a JSON-LD specific request
Tpt added a comment.
Not a problem but a cosmetic proposal: Instead of having the structure:
{
"@graph": [
{
"@id": "wdata:Q64",
"@type": "schema:Dataset",
"about": "wd:Q64&q
Tpt added a comment.
@daniel We could do something similar for stubs. with structures like:
{
"property": {
"@id": "wd:Q64",
"label": { "@value": "Foo", "@language": "en"}
...
}
instead of
{
"
Tpt added a comment.
I just had a quick review of the current GraphQL structure for Wikibase entities. It looks great! Thank you!
I would switch the Entity type to an interface and have Item, Property, Lexeme... implementations
type, datatype and snaktype fields values should probably
Tpt closed this task as "Resolved".Tpt claimed this task.Tpt added a comment.
YesTASK DETAILhttps://phabricator.wikimedia.org/T200901EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: TptCc: Smalyshev, gerritbot, Lydia_Pintscher, Tpt, Mringgaard
Tpt closed subtask T200901: [Task] Implement RDF serialization for senses as "Resolved".
TASK DETAILhttps://phabricator.wikimedia.org/T160259EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: TptCc: Smalyshev, Lucas_Werkmeister_WMDE, Aklapper,
Tpt added a comment.
It seems to me that the only thing missing in the implementation compared to https://www.mediawiki.org/wiki/Extension:WikibaseLexeme/RDF_mapping is the addition of schema:inLanguage for Lexemes. But it is derived data so it should not block the deployment
Tpt added a comment.
Thank you @Pintoch for raising this idea. For my fixing constraints violations project, I can mine violations from history offline so I do not really need this feature.
About the vandalism detection (and maybe diffs) use case, what we could do and seems quite reasonable to me
Tpt merged a task: T180304: Uses P629 (edition of) to improve language links between Wikisources.
TASK DETAILhttps://phabricator.wikimedia.org/T128173EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: TptCc: Tpt, PokestarFan, Hsarrazin, srishakatux, Bodhisattwa
Tpt added subscribers: Micru, PokestarFan, srishakatux, Bodhisattwa, Billinghurst, MF-Warburg, Purodha, Ankry, Gymel, StudiesWorld.Tpt merged a task: T128173: Represent editions as interwiki links on Wikisource.
TASK DETAILhttps://phabricator.wikimedia.org/T180304EMAIL PREFERENCEShttps
Tpt closed this task as a duplicate of T180304: Uses P629 (edition of) to improve language links between Wikisources.Restricted Application removed a subscriber: Liuxinyu970226.
TASK DETAILhttps://phabricator.wikimedia.org/T128173EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel
Tpt reopened subtask T128173: Represent editions as interwiki links on Wikisource as "Open".
TASK DETAILhttps://phabricator.wikimedia.org/T109579EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: TptCc: PokestarFan, Superchilum, Micru, intracer,
Tpt closed this task as a duplicate of T128173: Represent editions as interwiki links on Wikisource.Restricted Application removed a subscriber: Liuxinyu970226.
TASK DETAILhttps://phabricator.wikimedia.org/T180304EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences
Tpt reopened this task as "Open".Tpt added a comment.
I should close the other task, sorryTASK DETAILhttps://phabricator.wikimedia.org/T128173EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: TptCc: Tpt, PokestarFan, Hsarrazin, srishakatux, B
Tpt updated the task description. (Show Details)
CHANGES TO TASK DESCRIPTION...{F28001743}
The same problem seemsTASK DETAILhttps://phabricator.wikimedia.org/T214465EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: TptCc: Aklapper, Tpt, Nandana, Lahi, Gq86
Tpt created this task.Tpt added projects: Wikidata, MediaWiki-extensions-WikibaseView.Restricted Application added a subscriber: Aklapper.
TASK DESCRIPTIONWith Firefox 64 and the Adwaita Dark GTK+ skin the term box editing fields are white text on white background (see screenshot).
This is caused
Tpt added a comment.
@Lydia_Pintscher Maybe review https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wikisource/+/408365 and try to push the security review of the Wikisource extension to get it deployed on beta then production cluster.TASK DETAILhttps://phabricator.wikimedia.org/T180303EMAIL
Tpt added a comment.
For this task to be done, the extension should be deployed on Wikisource: T210174TASK DETAILhttps://phabricator.wikimedia.org/T180303EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: TptCc: Samwilson, Candalua, gerritbot, hoo, Hsarrazin
Tpt created this task.Restricted Application added a subscriber: Aklapper.
TASK DESCRIPTIONIt is probably not something we want possible on CommonsTASK DETAILhttps://phabricator.wikimedia.org/T213485EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: TptCc
Tpt added a project: StructuredDataOnCommons.
TASK DETAILhttps://phabricator.wikimedia.org/T149410EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: TptCc: matthiasmullie, Aklapper, Ladsgroup, aude, Lydia_Pintscher, thiemowmde, daniel, hoo, Nandana, JKSTNK, Lahi
Tpt added a comment.
Sorry everyone for the troubles. I was experimenting with a tool that tries to find corrections for constraint violations.
I have modified it to send a proper User-Agent for all its requests to the Wikidata API but not restarted it.
@Wikidata team: what would be an ok request
Tpt added a comment.
@Jonas Thank you for your feedback.
is it necessary for your tool to run the constraint checks in parallel?
No, I am going to switch to a sequential processing. Thanks for the idea!
Using WDQS instead would be a good idea, because then only your tool would get throttled
Tpt added a comment.
I have just made an attempt to map what I understood of MediaInfo data model
to RDF:
https://www.mediawiki.org/wiki/User:Tpt/WikibaseMediaInfo_RDF_Dump_Format
TASK DETAIL
https://phabricator.wikimedia.org/T215341
EMAIL PREFERENCES
https://phabricator.wikimedia.org
Tpt created this task.
Tpt added projects: MediaWiki-extensions-WikibaseClient, Wikidata.
TASK DESCRIPTION
The configuration variable useKartographerMaplinkInWikitext should be enabled
on production server to roll out T210926
<https://phabricator.wikimedia.org/T210926>.
TASK DETAIL
Tpt updated the task description.
TASK DETAIL
https://phabricator.wikimedia.org/T217442
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Tpt
Cc: hoo, Aklapper, Lydia_Pintscher, Tpt, Nandana, Lahi, Gq86,
GoranSMilovanovic, QZanden, LawExplorer
Tpt added a comment.
@Lydia_Pintscher I have created a change that enables on production
servers. Is it fine for you if I ask for scheduling the deployment of this
change during a SWAT window next week? Do you prefer to enable it on labs wiki
first?
TASK DETAIL
https
Tpt renamed this task from "Deploy mapframe for geocoordinate statements on
production" to "Deploy maplink for geocoordinate statements on production".
TASK DETAIL
https://phabricator.wikimedia.org/T217442
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/pa
Tpt added a comment.
@Lydia_Pintscher Great! I have schedule a SWAT for this evening.
TASK DETAIL
https://phabricator.wikimedia.org/T217442
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Tpt
Cc: gerritbot, hoo, Aklapper, Lydia_Pintscher, Tpt
Tpt added a comment.
@alaa_wmde Thanks! It's fine for me
TASK DETAIL
https://phabricator.wikimedia.org/T216842
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Tpt
Cc: alaa_wmde, Tpt, Ladsgroup, gerritbot, Lydia_Pintscher, daniel, Denny
Tpt closed subtask T217442: Deploy maplink for geocoordinate statements on
production as Resolved.
TASK DETAIL
https://phabricator.wikimedia.org/T210926
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Tpt
Cc: Lea_Lacroix_WMDE, Lydia_Pintscher
Tpt closed this task as "Resolved".
Tpt added a comment.
Done
TASK DETAIL
https://phabricator.wikimedia.org/T217442
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Tpt
Cc: gerritbot, hoo, Aklapper, Lydia_Pintscher, Tpt, alaa_wmde
Tpt added a comment.
The deployment have been done.
There is a small bug that may affect some modules: calls
`mw.wikibase.entity:formatStatements().value` using Lua may need to be passed
to frame:preprocess to be properly display the table. I have already
fixed Module:Databox
Tpt added a comment.
The feature is behind a configuration variable disabled by default. This change uses instead of so the output is still a textual display of the coordinates, but now with a link that opens a Kartographer map. So, nothing should break except if some modules parses the output
1 - 100 of 135 matches
Mail list logo
