Community Wishlist Survey 2023/Wikisource

Wikisource
6 proposals, 93 contributors, 171 support votes
The survey has closed. Thanks for your participation :)



IIIF support

  • 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 (talkcontribs) 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 (talkcontribs) 14:25, 3 February 2023 (UTC)[reply]

Voting

Allow Thumbor to generate images at higher DPI

  • 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

Voting

Automatically detect blank pages

  • 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

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

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

  • 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

Integrate PageImages with Wikisource

  • 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

Remember OCR column/region profiles

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