Page MenuHomePhabricator

Make it easier to cite different pages from a book as one reference
Closed, DuplicatePublic

Description

See also T100645: Efficient way to refer to different pages of the same work when adding references to an article (#17) and T15127: Page number attribute for <ref> tags, which may overlap/duplicate.

When I cite different pages from a book within an article, I have to cite the book separately multiple times. We have a "reuse citation" functionality that also works very well in VisualEditor but not for different pages from the same book. See Phabricator tasks phab:T100645 and phab:T15127. Thanks,

--Gnom (talk) 10:07, 12 November 2015 (UTC)

This card tracks a proposal from the 2015 Community Wishlist Survey: https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey

This proposal received 40 support votes, and was ranked #24 out of 107 proposals. https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Editing#Make_it_easier_to_cite_different_pages_from_a_book_as_one_reference

Event Timeline

DannyH created this task.Dec 5 2015, 12:15 AM
DannyH raised the priority of this task from to Needs Triage.
DannyH updated the task description. (Show Details)
DannyH moved this task to Wishlist 51-on on the Community-Wishlist-Survey-2015 board.
DannyH added a subscriber: DannyH.
Restricted Application added subscribers: StudiesWorld, Aklapper. · View Herald TranscriptDec 5 2015, 12:15 AM
IMPORTANT: If you are a community developer interested in working on this task: The Wikimedia Hackathon 2016 (Jerusalem, March 31 - April 3) focuses on #Community-Wishlist-Survey projects. There is some budget for sponsoring volunteer developers. THE DEADLINE TO REQUEST TRAVEL SPONSORSHIP IS TODAY, JANUARY 21. Exceptions can be made for developers focusing on Community Wishlist projects until the end of Sunday 24, but not beyond. If you or someone you know is interested, please REGISTER NOW.
Restricted Application added a subscriber: JEumerus. · View Herald TranscriptJan 21 2016, 2:52 PM
Tarrow added a subscriber: Tarrow.Jan 21 2016, 3:20 PM
DannyH updated the task description. (Show Details)Feb 5 2016, 11:56 PM
DannyH set Security to None.
01tonythomas added a subscriber: 01tonythomas.
NOTE: This task is a proposed project for Google-Summer-of-Code (2016) and Outreachy-Round-12 : GSoC 2016 and Outreachy round 12 is around the corner, and this task is listed as a Possible-Tech-Projects for the same. Projects listed for the internship programs should have a well-defined scope within the timeline of the event, minimum of two mentors, and should take about 2 weeks for a senior developer to complete. Interested in mentoring? Please add your details to the task description. Prospective interns should go through Life of a successful project doc to find out how to come up with a strong proposal for the same.

I've been asked to look at this task for a quick assessment of difficulty.

Though there could be a number of superficially-appealing ways to hack this in (including with an additional parameter on <ref> tags for multiply-used sources), I think at this point adding more complexity to the inline referencing model would be a mis-use of resources, and they could be more effectively used as part of the larger work on creating a structured references mostly being pioneered by @Daniel_Mietchen. Daniel, do you have any thoughts?

This looks like an interesting project to work on for GSoc. Is anyone willing to mentor this project?

For clarity, I think this would be a very very bad idea for a GSoC project.

I find this report extremely unclear as regards the requirements, so I'm merging it to the previous one which is clearer to understand and has less clutter.

Elitre added a subscriber: Elitre.Feb 26 2016, 1:15 PM