Wikidata:Report a technical problem/Archive/2023/05
|
This page is an archive. Please do not modify it. Use the current page, even to continue an old discussion. |
Change datatype to external-id
- 2019-10-15 Property talk:P1461#Change datatype to external-id
- 2022-09-07 Property talk:P1815#Change datatype to external-id
- 2022-09-07 Property talk:P2410#Change datatype to external-id
GeoGQL (talk) 11:58, 2 April 2023 (UTC)
- @GeoGQL Thank you for your message. We do not see any blockers to changing P1461 and P1815 to external-id. As for P2410, I'd like to hear from Andra or Egon before moving forward with a ticket. - Mohammed Sadat (WMDE) (talk) 13:12, 4 April 2023 (UTC)
- Regarding the last sentence: Why? GeoGQL (talk) 15:45, 4 April 2023 (UTC)
- @LennardHofmann: since you were involved in the first and proposed the two from 2022-09-07 you might be interested. GeoGQL (talk) 15:50, 4 April 2023 (UTC)
- I replied about WikiPathways ID (P2410): yes, external-id but keeping it as P2410 seems a good way forward. About asking me (that last sentence), generally, asking people involved in the original proposal and/or external database is always a good way to do. That last sentence did not give me a decision right, but just asked for my contribution. --Egon Willighagen (talk) 07:30, 6 April 2023 (UTC)
- "asking people involved in the original proposal and/or external database is always a good way to do" - User:Mohammed Sadat (WMDE) didn't yet specify a reason and he didn't do what you desribe for the other two in the above list of three. But thanks, now his "blocker" for not fulfilling the request ("I'd like to hear from Andra or Egon before moving forward with a ticket.") is on the way to be removed. As he wrote "I'd like to hear ..." can you post directly on his user talk page, to ensure he did "hear" you? He didn't reply to my question from 2023-04-04 15:45 despite editing in Wikidata, even on this page, 2023-04-06 10:52 [1]. GeoGQL (talk) 21:49, 7 April 2023 (UTC)
- Thanks Egon.
- @GeoGQL: Sometimes, it may take a little time to respond to messages due to capacity. I did see Egon's update (and their response was what I had in mind) but I couldn't get to it before the holidays. I've created a ticket to move forward with changing the datatype. -Mohammed Sadat (WMDE) (talk) 08:37, 11 April 2023 (UTC)
- Thank you. GeoGQL (talk) 22:31, 12 April 2023 (UTC)
- @Mohammed Sadat (WMDE), Sarai Sánchez (WMDE): "Sarai-WMDE set the point value for this task to 2." - what does that mean? GeoGQL (talk) 16:24, 19 April 2023 (UTC)
- "asking people involved in the original proposal and/or external database is always a good way to do" - User:Mohammed Sadat (WMDE) didn't yet specify a reason and he didn't do what you desribe for the other two in the above list of three. But thanks, now his "blocker" for not fulfilling the request ("I'd like to hear from Andra or Egon before moving forward with a ticket.") is on the way to be removed. As he wrote "I'd like to hear ..." can you post directly on his user talk page, to ensure he did "hear" you? He didn't reply to my question from 2023-04-04 15:45 despite editing in Wikidata, even on this page, 2023-04-06 10:52 [1]. GeoGQL (talk) 21:49, 7 April 2023 (UTC)
Why does it take so long for these three
They were already in https://phabricator.wikimedia.org/T317635. As can be seen on that page only a one line command that calls a script needs to be executed.
In the case of INEP ID (P11704), proposed as string, the following things happened 2023-04-03:
- 16:57 creation of the property with type string (User:TiagoLubiana) [2],
- 17:14 message 'It was created as a String property, as outlined, but maybe it should have been a external ID. Not sure how to change it post-hoc.' (User:TiagoLubiana) [3]
- 17:51 conversion (User:Maintenance script) [4].
It took less than 40 minutes from the idea "maybe it should" to perform the conversion. User:TiagoLubiana, are you able to run the script or do you know who did it in your case? GeoGQL (talk) 16:57, 19 April 2023 (UTC)
- @GeoGQL, TiagoLubiana: The ticket is scheduled for the next sprint and may be completed sooner. The process takes time due to the need for specialized access that is not available to everyone. We want to use this ticket as a learning opportunity for a new colleague. Regarding the point value, it is an estimate of the task's complexity and helps with planning and resource allocation. -Mohammed Sadat (WMDE) (talk) 10:54, 20 April 2023 (UTC)
- What is "the next sprint"? GeoGQL (talk) 12:40, 25 April 2023 (UTC)
- We've got this task covered in our current sprint, which kicked off earlier this week and is scheduled to run for the next two weeks. -Mohammed Sadat (WMDE) (talk) 08:53, 4 May 2023 (UTC)
- What is "the next sprint"? GeoGQL (talk) 12:40, 25 April 2023 (UTC)
- @TiagoLubiana: can you answer? GeoGQL (talk) 12:39, 25 April 2023 (UTC)
2023-04 passed without conversion - additional five ready to be converted
- 2023-04-01 Property talk:P5878#Change datatype to external-id
- 2023-04-01 Property talk:P5910#Change datatype to external-id
- 2023-04-01 Property talk:P6280#Change datatype to external-id
- 2023-04-01 Property talk:P10502#Change datatype to external-id
- 2023-04-01 Property talk:P10464#Change datatype to external-id
GeoGQL (talk) 21:26, 5 May 2023 (UTC)
- The conversions are a priority for us this week. We've added the new properties to the list. -Mohammed Sadat (WMDE) (talk) 08:01, 9 May 2023 (UTC)
- @GeoGQL: Now it is all done. Apologies that it took so long. -Mohammed Sadat (WMDE) (talk) 14:07, 12 May 2023 (UTC)
- Thank you!!! GeoGQL (talk) 16:04, 12 May 2023 (UTC)
- @GeoGQL: Now it is all done. Apologies that it took so long. -Mohammed Sadat (WMDE) (talk) 14:07, 12 May 2023 (UTC)
Archiving properties
As of May 5, DeltaBot stopped archiving generated Wikidata properties in Wikidata:Property proposal/Archive/2023/05. Can you point out the reason for this? —MasterRus21thCentury (talk) 07:15, 9 May 2023 (UTC)
- @Pasleim @MisterSynergy Can you respond to this? You are the bot operators of DeltaBot. Mbch331 (talk) 09:28, 9 May 2023 (UTC)
- The corresponding job got stuck for some reason. I have restarted it. —MisterSynergy (talk) 14:15, 9 May 2023 (UTC)
Change data type from url to external-id
Please allow conversion from datatype URL to external-id. Several properties have been created with type URL but are related to one website and have the unique constraint, for those the regular form is to use external-id and create an URL formatter. Effect:
- save space in the DB
- better controlable, e.g. if base URL changes, a change of only one property statement can change the external links
- correct sorting in section external-ids
Examples:
#P7890 (8-bits.info URL) #P1348 (AlgaeBase URL) #P2488 (Belarus Globe URL) #P1713 (biography at the Bundestag of Germany URL) #P2649 (CQ Ranking men's team URL) #P9519 (Digital Atlas of Idaho URL) #P1421 (GRIN URL) #P9908 (Hardy's Guide to Marine Gastropods URL) #P7294 (itch.io URL) #P4001 (Latvian Protected Nature Territory URL) #P1991 (LPSN URL) #P7707 (PlayStation DataCenter URL) #P3268 (PORT organization URL) #P8606 (Stairway To Hell ID) #P2520 (UNESCO Biosphere Reserve URL) #P6107 (Winterthur Glossar URL (DEPRECATED)) #P6363 (WordLift URL)
GeoGQL (talk) 16:31, 12 May 2023 (UTC)
- Changing the data type makes sense when the values that were valid for the old data type are valid for the new one as well, e.g. from a string containing an identifier (without any URL formatting) to an external identifier. While changing from URL to external identifier should be technically possible (both have the value type string), it doesn’t make sense, because the values need to be updated anyway, resulting in temporarily broken values (if the property already has external identifier data type, but the value hasn’t been updated, the automatic links contain the domain name and path twice). It’s cleaner to create a new property with the new data type, and move the old values to the new property using a bot, appropriately transforming the value while moving it. —Tacsipacsi (talk) 10:03, 14 May 2023 (UTC)
- @temporarily broken values : Property talk:P7890 - 18 values. How long would "temporarily" last, if a bot or other tool updates the values? GeoGQL (talk) 11:45, 14 May 2023 (UTC)
- How long would it take to just create a new property and copy over the values instead of waiting for the developers to do the conversion? —Tacsipacsi (talk) 13:17, 16 May 2023 (UTC)
- There's probably a reason why these properties were created with datatype URL. itch.io URL (P7294) cannot be converted to external-id for example because the URLs are of the format
https://$DEV.itch.io/$GAME. So instead of inventing a string format from which the developer and game names can be extracted (using a delimiter perhaps), why not simply use the URLs, which have the bonus of being clickable? Dexxor (talk) 07:24, 17 May 2023 (UTC)- "There's probably a reason" - yes, for any bug there is probably one as is for any request to remove a bug. RE itch.io URL : that is a combination of two external identifiers. Regular conversion would not work, so this could be left out. GeoGQL (talk) 18:00, 18 May 2023 (UTC)
- Is that a useful style of discussion, to not answer a question for how long an issue you mentioned exists, and instead ask question? What is your answer to your own question, since it was your suggestion to go that way? Or are you just opposing because you decided "it doesn’t make sense"? GeoGQL (talk) 18:06, 18 May 2023 (UTC)
- There's probably a reason why these properties were created with datatype URL. itch.io URL (P7294) cannot be converted to external-id for example because the URLs are of the format
- How long would it take to just create a new property and copy over the values instead of waiting for the developers to do the conversion? —Tacsipacsi (talk) 13:17, 16 May 2023 (UTC)
- @temporarily broken values : Property talk:P7890 - 18 values. How long would "temporarily" last, if a bot or other tool updates the values? GeoGQL (talk) 11:45, 14 May 2023 (UTC)
- As mentioned by @Tacsipacsi these should not be converted but instead new Properties created as this would be a breaking change for reusers who rely on these being URLs. Lydia Pintscher (WMDE) (talk) 18:04, 18 May 2023 (UTC)
- Tacsipacsi didn't gave a sensible reason. GeoGQL (talk) 18:07, 18 May 2023 (UTC)
- Regarding re-users: they are not properly re-using if they don't take into account change on the property. GeoGQL (talk) 18:10, 18 May 2023 (UTC)
Page jumbled up in mobile view
I am getting entity pages as this on Wikidata. All jumbled up.
Please help. Gotitbro (talk) 16:21, 19 May 2023 (UTC)
- Certainly looks borked: https://m.wikidata.org/wiki/Q76190542 --Tagishsimon (talk) 21:27, 19 May 2023 (UTC)
Time limit on Special:Nuke
The mass delete function only seems to go back less than a month. The documentation suggests that $wgRCMaxAge defaults to 90 days. Are we using a non-default value? It sometimes takes us some discussion to decide to pull the trigger. Bovlb (talk) 16:43, 9 May 2023 (UTC)
- It is 30 days per [5]. In phab:T307328 it has even been discussed to shorten this period further since the recent changes table in Wikidata is pretty large and expensive. —MisterSynergy (talk) 18:01, 9 May 2023 (UTC)
- Thanks. I don't really understand why Special:Nuke is based on RecentChanges. Why can't it just use user contributions? Bovlb (talk) 19:04, 9 May 2023 (UTC)
As in English Wikipedia Aquatic sports redirects to List of water sports Category:Water sports templates (Q115051915) should be merges with Category:Aquatics templates (Q8258017) and so Category:Water sports templates with Category:Aquatics templates.
Category:Water sports templates (Q115051915) is a page that is just made by a robot. Shkuru Afshar (talk) 04:23, 24 May 2023 (UTC)
DB replica lag
https://replag.toolforge.org/ 53 hours, and there's no announced maintenance. Issues? Infrastruktur (talk) 10:54, 27 May 2023 (UTC)
- phab:T337446, I suppose. --Matěj Suchánek (talk) 16:47, 27 May 2023 (UTC)
Wikidata item Høgsteinen Lighthouse (Q1623402)
Can you fix link from Commons Category:Høgsteinen fyrstasjon to Wikidata item Høgsteinen Lighthouse (Q1623402)? Nothing I could do would link them. GRDN711 (talk) 19:32, 28 May 2023 (UTC)
