Community Wishlist Survey 2023/Wikisource

Community Wishlist Survey 2023

Wikisource

6 proposals, 93 contributors, 171 support votes

The survey has closed. Thanks for your participation :)

Here are the Community Wishlist Survey 2023 results!

IIIF support

Edit proposal/discussion

Problem: Currently Commons does not have a mechanism to provide high-quality image support, and while there are high quality IIIF sources available there are concerns over user data privacy and loading of third-party content that limit the adoption of these sources.
Proposed solution: Provide/Implement a IIIF server either via Commons or as a ToolForge/WMcloud hosted tool that is able to provide IIIF support for the ProofreadPage zooming and panning interface via a gadget interface.
Who would benefit: Wikisource editors, GLAM partners
More comments: See also wikisource:User:Inductiveload/jump_to_file
Phabricator tickets:
Proposer: Sohom Datta (talk) 07:50, 1 February 2023 (UTC)[reply]

Discussion

I wonder what it'd take to implement this in Thumbor? It was requested once, in 2016. Sam Wilson 07:33, 3 February 2023 (UTC)[reply]
It would be very nice if we can get support for at least the base api, to provide tiling etc. Even for Support 360 photo viewing support for tiling is a requirement we probably cannot go without. Thumbor with an additional /iiif/ endpoint providing support for the Image API would in my opinion be very interesting. Implementing region/size/rotation/quality/format etc should all be relatively doable with existing thumbor and imagemagick functionality (even though we have not implemented any of those thumbor apis for our own plugins yet). I think it would bring lots of benefits to the movement at large and for Commons, GLAM and wikisource in particular. —TheDJ (talk • contribs) 14:18, 3 February 2023 (UTC)[reply]
For wikisource specifically, the presentation api might also be interesting, as it allows you to describe a book for instance. There is a nice api example in the specification of that. —TheDJ (talk • contribs) 14:25, 3 February 2023 (UTC)[reply]

Voting

Support Magnoliasouth (talk) 23:11, 10 February 2023 (UTC)[reply]
Support HHill (talk) 08:27, 11 February 2023 (UTC)[reply]
Support Shizhao (talk) 13:56, 11 February 2023 (UTC)[reply]
Support --NGC 54 (talk｜contribs) 01:14, 12 February 2023 (UTC)[reply]
Support Libcub (talk) 03:15, 14 February 2023 (UTC)[reply]
Support VIGNERON * ^discut. 19:47, 14 February 2023 (UTC)[reply]
Support Ruthven (msg) 15:46, 15 February 2023 (UTC)[reply]
Support Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:15, 15 February 2023 (UTC)[reply]
Support Sadads (talk) 01:25, 16 February 2023 (UTC)[reply]
Support Hey man im josh (talk) 14:59, 16 February 2023 (UTC)[reply]
Support Gillum (talk) 23:21, 16 February 2023 (UTC)[reply]
Support —TheDJ (talk • contribs) 13:24, 18 February 2023 (UTC)[reply]
Support Vulcan❯❯❯Sphere! 16:17, 18 February 2023 (UTC)[reply]
Support Zache (talk) 05:36, 19 February 2023 (UTC)[reply]
Support Nashona (talk) 18:19, 20 February 2023 (UTC)[reply]
Support cyrfaw (talk) 12:11, 21 February 2023 (UTC)[reply]
Support MartinPoulter (talk) 12:40, 21 February 2023 (UTC)[reply]

Allow Thumbor to generate images at higher DPI

Edit proposal/discussion

Problem: Currently Thumbor generates images at a fixed DPI which can cause blurry and artifacted images at higher image sizes such as the ones used by Openseadragon.
Proposed solution: Provide a method to control the DPI that Thumbor uses via the URL and integrate it into ProofreadPage + Openseadragon such that higher images sizes do not suffer from artifacting.
Who would benefit: Wikisource editors
More comments:
Phabricator tickets: T256959
Proposer: Sohom Datta (talk) 14:32, 31 January 2023 (UTC)[reply]

Discussion

This is specifically about thumbnails for PDF/Djvu right ? Perhaps we should amend the proposal to make that more clear. —TheDJ (talk • contribs) 15:18, 5 February 2023 (UTC)[reply]
Yes, this is only wrt to thumbnails to PDF and Djvu files used by ProofreadPage. Sohom Datta (talk) 20:23, 6 February 2023 (UTC)[reply]

Voting

Support Seboloidus (talk) 18:18, 10 February 2023 (UTC)[reply]
Support عُثمان (talk) 23:38, 10 February 2023 (UTC)[reply]
Support EpicPupper (talk) 05:35, 11 February 2023 (UTC)[reply]
Support I have often have had to open the original file separately when transcribing pages, because the low resolution combined with the artifacts make the actual text ambiguous. This feature would have saved me a lot of time in aggregate. Waldyrious (talk) 09:53, 11 February 2023 (UTC)[reply]
Support Nehaoua (talk) 16:04, 11 February 2023 (UTC)[reply]
Support --NGC 54 (talk｜contribs) 01:13, 12 February 2023 (UTC)[reply]
Support Mauricio V. Genta (talk) 08:01, 12 February 2023 (UTC)[reply]
Support Thomas Kinz (talk) 01:09, 13 February 2023 (UTC)[reply]
Support Libcub (talk) 03:17, 14 February 2023 (UTC)[reply]
Support VIGNERON * ^discut. 19:49, 14 February 2023 (UTC)[reply]
Support Nux (talk) 08:34, 15 February 2023 (UTC)[reply]
Support Gillum (talk) 23:21, 16 February 2023 (UTC)[reply]
Support —TheDJ (talk • contribs) 13:24, 18 February 2023 (UTC)[reply]
Support Vulcan❯❯❯Sphere! 16:17, 18 February 2023 (UTC)[reply]
Support · · · Peter (Southwood) ^(talk): 17:29, 18 February 2023 (UTC)[reply]
Support Sgvijayakumar (talk) 01:17, 19 February 2023 (UTC)[reply]
Support cyrfaw (talk) 12:15, 21 February 2023 (UTC)[reply]
Support MartinPoulter (talk) 12:38, 21 February 2023 (UTC)[reply]
Support Kcat37 (talk) 13:35, 21 February 2023 (UTC)[reply]

Automatically detect blank pages

Edit proposal/discussion

Problem: Currently, a user must individually mark a specific page as a blank page in a book
Proposed solution: Create a mechanism (maybe via the Wikisource extension?) via which the software will auto-mark specific pages as blank pages for the user without the user having to actually go to those specific pages.
Who would benefit: Wikisource editors
More comments:
Phabricator tickets:
Proposer: Sohom Datta (talk) 11:10, 27 January 2023 (UTC)[reply]

Discussion

Good idea, or no text (image only for exemple) --Nehaoua (talk) 17:58, 28 January 2023 (UTC)[reply]
Additonally, there is impossible to use Special:Shortestpages on Wikisources, because are full of "empty" pages. JAn Dudík (talk) 13:49, 30 January 2023 (UTC)[reply]
See also wikisource:Wikisource:Scriptorium/Archives/2022-07#Lots of blank pages. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:46, 2 February 2023 (UTC)[reply]
Your link incorrect Proeksad (talk) 22:52, 10 February 2023 (UTC)[reply]
Apologies; fixed. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:01, 15 February 2023 (UTC)[reply]
I'm not sure about this. Are the pages numbered? If so a reader may wonder why pages are missing. Most blank pages are not numbered but some are. It needs to be consistent. I think that at the bottom of the page before the blank, something should say "The next page was blank, so we removed it," which would be better. Anyone disagree?

Magnoliasouth (talk) 23:20, 10 February 2023 (UTC)[reply]

@Sohom Datta: What do you mean by auto-mark? At what level - index NS or Page NS? Automatic status change to "Without text"? What about scans containing, for example, illustrations, scores, notes, ..., which we mark "Without text", but also add other required data. Zdzislaw (talk) 14:53, 12 February 2023 (UTC)[reply]
@Zdzislaw By auto-mark, I mean changing the status to "without text" for a specific page.

The way I picture this working is via a prompt in the Pagelist Widget/Index edit screen (at the Index: level) or at the top of a Page: page (at a Pgae: namespace level) that you can click on to automark a page/a set of pages as "Without text". For now, I think it makes sense to include only pages that are blank or are wholely composed of illustrations, however, we can looking into encompassing other types of "without text" pages as well later. Sohom Datta (talk) 16:16, 13 February 2023 (UTC)[reply]

Voting

Support Nmarshall25 (talk) 20:03, 10 February 2023 (UTC)[reply]
Support NMaia (talk) 00:06, 11 February 2023 (UTC)[reply]
Support Poslovitch (talk) 00:25, 11 February 2023 (UTC)[reply]
Support Klein Muçi (talk) 00:51, 11 February 2023 (UTC)[reply]
Support ··· 🌸 Rachmat04 · ☕ 02:36, 11 February 2023 (UTC)[reply]
Support EpicPupper (talk) 05:37, 11 February 2023 (UTC)[reply]
Support Muted Red Tulip (talk) 08:16, 11 February 2023 (UTC)[reply]
Support Szymonel (talk) 08:46, 11 February 2023 (UTC)[reply]
Support Exilexi (talk) 09:16, 11 February 2023 (UTC)[reply]
Support Mike bzh (talk) 15:39, 11 February 2023 (UTC)[reply]
Support FinixFighter (talk) 15:50, 11 February 2023 (UTC)[reply]
Support Nehaoua (talk) 16:03, 11 February 2023 (UTC)[reply]
Support Novak Watchmen (talk) 18:24, 11 February 2023 (UTC)[reply]
Support VastV0idInSpace0 (talk) 20:03, 11 February 2023 (UTC)[reply]
Support --NGC 54 (talk｜contribs) 01:13, 12 February 2023 (UTC)[reply]
Support JAn Dudík (talk) 21:55, 13 February 2023 (UTC)[reply]
Support Libcub (talk) 03:11, 14 February 2023 (UTC)[reply]
Support Jayantanth (talk) 08:05, 14 February 2023 (UTC)[reply]
Support PMenon-WMF (talk) 06:41, 15 February 2023 (UTC)[reply]
Support Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:02, 15 February 2023 (UTC)[reply]
Support Gillum (talk) 23:21, 16 February 2023 (UTC)[reply]
Support Dankowski (talk) 22:49, 17 February 2023 (UTC)[reply]
Support DoublePendulumAttractor (talk) 06:00, 18 February 2023 (UTC)[reply]
Support Bicolino34 (talk) 08:19, 18 February 2023 (UTC)[reply]
Support This should be added. Thingofme (talk) 16:28, 18 February 2023 (UTC)[reply]
Support cyrfaw (talk) 12:40, 21 February 2023 (UTC)[reply]
Support Kcat37 (talk) 13:37, 21 February 2023 (UTC)[reply]
Support Morten Haan (talk) 18:51, 22 February 2023 (UTC)[reply]

Implement Extension:ProofreadPage functionality for Parsiod (aka native support of tag:pages to Parsoid)

Edit proposal/discussion

Problem: Since the migration to Parsoid, rest_v1 api placed references at the end of each transcluded <pages ... /> section instead of in the <references/> tag location. It breaks WS-Export, which relies on this api. This causes works exported from the Wikisources to be generated incorrectly.
Proposed solution: Implement Extension:ProofreadPage functionality for Parsiod
Who would benefit: Wikisource readers downloading tens of thousands of Wikisource texts per month via WS-Export (https://ws-export.wmcloud.org/statistics)
More comments:
Phabricator tickets: phab:T319258
Proposer: Zdzislaw (talk) 14:12, 28 January 2023 (UTC)[reply]

Discussion

Voting

Support Seboloidus (talk) 18:15, 10 February 2023 (UTC)[reply]
Support ━ ALBERTOLEONCIO Who, me? 18:55, 10 February 2023 (UTC)[reply]
Support * Pppery * _{it has begun} 04:04, 11 February 2023 (UTC)[reply]
Support Really need it! Wieralee (talk) 12:34, 11 February 2023 (UTC)[reply]
Support Msz2001 (talk) 12:46, 11 February 2023 (UTC)[reply]
Strong support Correct ebook generation is critical for Wikisource. Ankry (talk) 13:20, 11 February 2023 (UTC)[reply]
Strong support Critical for the Wikisource project Draco flavus (talk) 13:45, 11 February 2023 (UTC)[reply]
Support odder (talk) 14:23, 11 February 2023 (UTC)[reply]
Support Wolan (talk) 16:14, 11 February 2023 (UTC)[reply]
Support Peter Bowman (talk) 23:29, 11 February 2023 (UTC)[reply]
Support Mauricio V. Genta (talk) 08:01, 12 February 2023 (UTC)[reply]
Support Essential for proper e-book support. Rdrozd (talk) 23:50, 13 February 2023 (UTC)[reply]
Support Libcub (talk) 03:13, 14 February 2023 (UTC)[reply]
Support Subvisser5 (talk) 14:23, 14 February 2023 (UTC)[reply]
Support Vätte (talk) 15:38, 14 February 2023 (UTC)[reply]
Support VIGNERON * ^discut. 19:48, 14 February 2023 (UTC)[reply]
Support Nux (talk) 08:31, 15 February 2023 (UTC)[reply]
Support Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:58, 15 February 2023 (UTC)[reply]
Support Matma Rex (talk) 22:34, 15 February 2023 (UTC)[reply]
Support Sadads (talk) 01:25, 16 February 2023 (UTC)[reply]
Support Gillum (talk) 23:21, 16 February 2023 (UTC)[reply]
Support Dankowski (talk) 22:51, 17 February 2023 (UTC)[reply]
Support Bicolino34 (talk) 08:21, 18 February 2023 (UTC)[reply]
Support Fabius Lector (talk) 10:34, 18 February 2023 (UTC)[reply]
Support —TheDJ (talk • contribs) 13:47, 18 February 2023 (UTC)[reply]
Support ysjbserver (talk) 15:47, 18 February 2023 (UTC)[reply]
Support There should have ebooks in Wikisource project. Thingofme (talk) 16:24, 18 February 2023 (UTC)[reply]
Support Matlin (talk) 13:34, 19 February 2023 (UTC)[reply]
Support cyrfaw (talk) 12:42, 21 February 2023 (UTC)[reply]
Support Kcat37 (talk) 13:35, 21 February 2023 (UTC)[reply]
Support Bonvol (talk) 13:25, 23 February 2023 (UTC)[reply]
Support Drogosław^TALK 13:42, 23 February 2023 (UTC)[reply]
Support Tom Ja (talk) 13:43, 23 February 2023 (UTC)[reply]
Support tsca (talk) 14:09, 23 February 2023 (UTC)[reply]
Support masti <talk> 14:22, 23 February 2023 (UTC)[reply]
Support Zetzecik (talk) 14:27, 23 February 2023 (UTC)[reply]
Support Gytha (talk) 14:47, 23 February 2023 (UTC)[reply]
Support PMG (talk) 14:54, 23 February 2023 (UTC)[reply]
Support SkrzydlatyMuflon (talk) 16:02, 23 February 2023 (UTC)[reply]
Support Wargo (talk) 22:59, 23 February 2023 (UTC)[reply]
Support Maire ♣ 16:54, 24 February 2023 (UTC)[reply]

Integrate PageImages with Wikisource

Edit proposal/discussion

Problem: Currently when searching for a book (or linking to a book on social media), only the default image shows up (on-wiki it is the OOUI article icon, on social media it is the wikimedia logo)
Proposed solution: Integrate the PageImage extension into Wikisource so that when a article is searched or linked, the user is able to see a preview of the book and maybe read a brief blurb of the book (when linked).
Who would benefit: Wikisource readers, anyone who shares Wikisource texts on social media
More comments:
Phabricator tickets: T323570
Proposer: Sohom Datta (talk) 11:21, 27 January 2023 (UTC)[reply]

Discussion

Voting

Support ━ ALBERTOLEONCIO Who, me? 18:57, 10 February 2023 (UTC)[reply]
Support --Ignacio Rodríguez (talk) 19:21, 10 February 2023 (UTC)[reply]
Support Sicarov (talk) 20:52, 10 February 2023 (UTC)[reply]
Support Tol (talk | contribs) @ 21:13, 10 February 2023 (UTC)[reply]
Support --Proeksad (talk) 22:56, 10 February 2023 (UTC)[reply]
Support Excellent idea! Magnoliasouth (talk) 23:24, 10 February 2023 (UTC)[reply]
Support عُثمان (talk) 23:37, 10 February 2023 (UTC)[reply]
Support * Pppery * _{it has begun} 04:04, 11 February 2023 (UTC)[reply]
Support EpicPupper (talk) 05:35, 11 February 2023 (UTC)[reply]
Support Gohan 07:19, 11 February 2023 (UTC)[reply]
Support Muted Red Tulip (talk) 08:19, 11 February 2023 (UTC)[reply]
Support Nice idea, this would go a long way in facilitating the organic promotion of Wikisource as a project. Waldyrious (talk) 09:58, 11 February 2023 (UTC)[reply]
Support Nehaoua (talk) 16:03, 11 February 2023 (UTC)[reply]
Support VastV0idInSpace0 (talk) 20:04, 11 February 2023 (UTC)[reply]
Support Cantons-de-l'Est (talk) 20:30, 11 February 2023 (UTC)[reply]
Support --NGC 54 (talk｜contribs) 01:14, 12 February 2023 (UTC)[reply]
Support Mauricio V. Genta (talk) 08:01, 12 February 2023 (UTC)[reply]
Support Thomas Kinz (talk) 01:12, 13 February 2023 (UTC)[reply]
Support Izno (talk) 08:09, 13 February 2023 (UTC)[reply]
Support dobre Spetroff (talk) 22:30, 13 February 2023 (UTC)[reply]
Support Libcub (talk) 03:18, 14 February 2023 (UTC)[reply]
Support Vätte (talk) 15:39, 14 February 2023 (UTC)[reply]
Support VIGNERON * ^discut. 19:49, 14 February 2023 (UTC)[reply]
Support Nux (talk) 08:33, 15 February 2023 (UTC)[reply]
Support Matma Rex (talk) 22:37, 15 February 2023 (UTC)[reply]
Support Gillum (talk) 23:21, 16 February 2023 (UTC)[reply]
Support this is great idea Agus Damanik (talk) 07:50, 17 February 2023 (UTC)[reply]
Support Proposed solution will look better. Dankowski (talk) 22:50, 17 February 2023 (UTC)[reply]
Support DoublePendulumAttractor (talk) 06:00, 18 February 2023 (UTC)[reply]
Support —TheDJ (talk • contribs) 13:28, 18 February 2023 (UTC)[reply]
Support ysjbserver (talk) 15:48, 18 February 2023 (UTC)[reply]
Support Sgvijayakumar (talk) 01:17, 19 February 2023 (UTC)[reply]
Support cyrfaw (talk) 11:58, 21 February 2023 (UTC)[reply]
Support Kcat37 (talk) 13:34, 21 February 2023 (UTC)[reply]

Remember OCR column/region profiles

Edit proposal/discussion

Problem: Currently, using OCR to extract text from books is bad at detecting irregular features such as notes and columns (see OCR output for wikisource:Page:Login_USENIX_Newsletter_feb1983.djvu/2, and the same page in the OCR tool where rectangular regions can be selected).
Proposed solution: Provide a mechanism (Gadget or via Wikimedia OCR) that will allow users to demarcate columns and specific areas that need to be OCRed together, and store these areas against the Index page so they don't need to be repeated for every page.
Who would benefit: Wikisource editors
More comments:
Phabricator tickets:
1. T294903 ProofreadPage: Implement region selection UI for the OCR tool directly in the PRP page editor
2. T288389 OCR support should recognise and process mutliple regions, with user assisted selection , where a work does not have a 'linear' layout.
Proposer: Sohom Datta (talk) 12:37, 30 January 2023 (UTC)[reply]

Discussion

@Sohom data: Just to clarify: the 'profile' here would be e.g. an index-page level store of rectangular page regions that could then be used on all pages to do the OCR, without users having to re-select the same regions over and over again on each page (as they can currently do, and what's more they do it via the Advanced options form and then have to copy and paste the text). Is that right? SWilson (WMF) (talk) 00:50, 1 February 2023 (UTC)[reply]
Yep, that is what I meant by profiles :) Sohom Datta (talk) 05:35, 1 February 2023 (UTC)[reply]

Voting

Support --Ignacio Rodríguez (talk) 19:22, 10 February 2023 (UTC)[reply]
Support ━ Sicarov (talk) 20:48, 10 February 2023 (UTC)[reply]
Support Magnoliasouth (talk) 23:24, 10 February 2023 (UTC)[reply]
Support عُثمان (talk) 23:38, 10 February 2023 (UTC)[reply]
Support Yes! This would be very helpful for works containing manual annotations as well, or older books where the margins are tight and can confuse the ORC. Waldyrious (talk) 09:55, 11 February 2023 (UTC)[reply]
Support Nehaoua (talk) 16:02, 11 February 2023 (UTC)[reply]
Support VastV0idInSpace0 (talk) 20:03, 11 February 2023 (UTC)[reply]
Support Kaviraf (talk) 11:46, 12 February 2023 (UTC)[reply]
Support JAn Dudík (talk) 21:54, 13 February 2023 (UTC)[reply]
Support Libcub (talk) 03:12, 14 February 2023 (UTC)[reply]
Support must needed Jayantanth (talk) 07:57, 14 February 2023 (UTC)[reply]
Support VIGNERON * ^discut. 19:48, 14 February 2023 (UTC)[reply]
Support PMenon-WMF (talk) 06:40, 15 February 2023 (UTC)[reply]
Support Ruthven (msg) 15:46, 15 February 2023 (UTC)[reply]
Support Aishik Rehman (talk) 08:47, 16 February 2023 (UTC)[reply]
Support Gillum (talk) 23:21, 16 February 2023 (UTC)[reply]
Support Dankowski (talk) 22:48, 17 February 2023 (UTC)[reply]
Support Bicolino34 (talk) 08:17, 18 February 2023 (UTC)[reply]
Support Fabius Lector (talk) 10:35, 18 February 2023 (UTC)[reply]
Support ysjbserver (talk) 15:46, 18 February 2023 (UTC)[reply]
Support Vulcan❯❯❯Sphere! 16:15, 18 February 2023 (UTC)[reply]
Support This should be added by users. Thingofme (talk) 16:23, 18 February 2023 (UTC)[reply]
Support Looks useful · · · Peter (Southwood) ^(talk): 17:27, 18 February 2023 (UTC)[reply]
Support cyrfaw (talk) 11:47, 21 February 2023 (UTC)[reply]
Support Fcastillo (talk) 22:12, 22 February 2023 (UTC)[reply]
Support Bonvol (talk) 13:26, 23 February 2023 (UTC)[reply]