User talk:Zoeannl/Project guideline/Proofreader’s Guide

An effort to translate Distributed Proofreaders Guidelines into wiki. On the premise that DP is much more successful at retaining proofreaders, they must be doing something right; Wikisource help is atrocious; processes and procedures that mirror DP’s would support the transition of DP proofreaders to Wikisource.

DP Proofreading Guide DP Formatting Guide

Standardisation
Terminology:
 * The project includes the Index page, Project Discussion page (Index discussion page), the book (finished product) on Main_space, text (OCRd or edited) and scan on Page_space and annotations.
 * Project manager, Proofreader, Validator, Transcluder
 * "Someone" watching Project discussion, pages who is good at holding hands of newbies --> upskilling; Watchlist tag of (all?) "discussion pages"
 * Ellipsis from Style_guide; minus sign?; characters rather than templates for symbols etc
 * Refs: Help:Editing, Help:Formatting_conventions, Style_guide
 * Help/mentoring/go to guides: Separate pages for exemplars with option for people to add new/interesting examples and Help function for people who want their work checked.
 * colour of links i.e. make them grey?

TO DO

 * How to ask for help
 * Help, Tutorials, How do templates work; HTML; CCS
 * Help:Page_scans, w:Help:A_quick_guide_to_templates
 * Use template:x/doc to host instructions and exemplars


 * Glossary
 * Navigation
 * Wikisource philosophy
 * The process to a finished text
 * Relating to Distributed Proofreaders
 * the costs/benefits of standardization
 * project managers/proofreaders/formatters aligned.
 * post processing-how can working on wikisource scaffold people towards post processing? http://www.pgdp.net/wiki/Getting_your_PP_Project_Ready_for_PPV
 * image processing aligned
 * HTML & CCS familiarity; http://www.pgdp.org/~jana/best-practices/pages/best-practices/
 * familiarity with linking
 * familiarity with ASCII code, font codes
 * alignment, justification, spanning pages
 * tags
 * Printers' Errors and Transcriber's Note aligned
 * layout esp. front matter & contents, dropped initials images
 * how can Wikisource scaffold people into wiki-ing
 * wiki grades/qualifications?
 * automatic recognition of DP qualifications
 * code


 * Wiki Jargon Guide
 * Proofreading Summary

QUESTIONS

 * wiki mark-up vs templates vs

REQUESTS

 * fix broken line at bottom of page_space
 * Fix Loss of session message "Sorry! We could not process your edit due to a loss of session data. You may have timed out-try again. You might have been logged out. Please verify that you're still logged in and try again. If it still does not work, try logging out and logging back in, and check that your browser allows cookies from this site."
 * fix drop down menus: include ellipsis with em dash User talk:Zoeannl/Project guideline/Drop down menus
 * Create User wishlist (as per Watchlist tick box)-books to read, proofread, validate
 * Indication on Index page of "pages I have proofread". gadgets Development/Pages I can validate.
 * How to avoid: If two people work on the same page at the same time then a conflict arises on submission. Template:Inuse
 * Project management indication if one person is steering a project/book through. This works on DP, creates ownership. Needs to be explicit that there is a level of ownership by project manager re respect of standard layout etc. Enables project specific discussion, less intimidating than going to scriptorium.
 * most recent post on top for Discussions
 * Watchlist - ability to specify "get notification" for individual events e.g. other User activity on page/book/project. e.g. Greek request
 * User page templates; Privacy settings for User pages; "rating" system- self-rating; skill ticklist with 0-5:no skill to fully competent and -3 to 3: scared to fully confident. Feedback goes here. user can link request feedback for specific page then feedback can be individual. w:Wikipedia:User_page_design_center
 * ,     standardised to em length
 * Other fonts: antiqua (a variant of roman font) inside fraktur
 * Way to collate refs/links in books e.g. Hume referenced in Phil R; . Perhaps in Project discussion page. Bot to list all author links and main_page links incl red links
 * Red Author and Book refs gathered together as to do list-preference given to books and authors referenced in books already in wikisource.
 * Toggle Preview with Rendered text side by side with djvu and edit view

ANNOTATION
Where wouldn't I do annotations? Analytical interpretation of a work, especially where there is lots of this. Where the annotations detract from the author's intent, or overwhelm the author's work. If there is the call for such works, I am yet to be convinced that it is at WS, and one wonders if there was no WMF site, whether it should be enWB or enWS that should be first requested to adapt their position. — billinghurst sDrewth 14:34, 17 June 2011 (UTC)
 * How to link
 * Annotations
 * Help:Annotating
 * So those things that I do (ie. that I find acceptable) are 1) try to provide the main links in the headers of the works, where possible 2) link to works and authors in the body of a work, especially being the case where the works have internal references themselves 3) for words that are misspelt and people may wish to correct [sic], 4) for words that are uncommon in current English, or archaic, a link to Wiktionary, and v.v. 5) for a major theme, significant assistance in understanding an article, I will consider a link to Wikipedia. 5) for errors in works, ie. where we have 20-20 historical hindsight, I will consider the use of  , eg. The Times/1902/Obituary/Charles Kent 6) for certain works, I have also used some of the templates that utilise undefined , eg. where there is continued use of Latin in the text, and its understanding is useful for reading the work, eg. expected contemporary knowledge of that time, is definitely not today. I feel that for a specific additional text annotation that there should be a clear benefit for that to occur, rather than its appearance as a feature.