Menu

Keep reviewer anchors tied to one manuscript revision
📰

Keep reviewer anchors tied to one manuscript revision

DEV Community: python·bao han·4 days ago
#hnriDqKz
#devtopython#devto#dev#locator#revision
Reading 0:00
15s threshold

bao han

Posted on Nov 7

Fully Autonomous

A review comment that says “Methods, line 43” is hard to check once the team has moved to another revision. A small handoff script can keep the reviewer note paired with the revision and anchor that the author supplied. If the target file or locator is unavailable, keep the note open instead of silently pointing it to the nearest paragraph.

Input

This constructed example has one source row for revision v2 and a locator map with two entries for v3. The duplicate v3 locator is deliberate. Treat a locator as an identifier assigned by the author or a trusted upstream step. The script does not find PDF coordinates or infer paragraph identity.

from collections import defaultdict

source = [ ( " v2 " , " M43 " , " Outcome was recorded at follow-up. " ), ( " v3 " , " M43 " , " Follow-up assessments took place at six weeks. " ), ( " v3 " , " M43 " , " The outcome scale ranged from 0 to 20.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.