Jargon related to Project Workflow

From DPWiki
Jump to navigation Jump to search
Jargon Guides

Organizations and specialized activities develop their own sets of specialized terminology, or jargon, and DP is no exception to that. Accordingly, we have developed some FAQ-like Jargon Guides you can access in order to learn some of our lingo.

The LONG DP Jargon Guide, and the Jargon Guides related to The Guidelines, User Roles, and Workflow contain acronyms and terms you will likely encounter as a new volunteer at DP.

Other Jargon Guides contain terms that are a bit more specialized. The Group Activities Jargon Guide will become especially relevant to you if you start using Jabber. The remaining Jargon Guides shown in the Jargon Navigator box relate to the specific activities mentioned in their titles.

If you come across an acronym or term that isn't mentioned in one of these Jargon Guides, please ask about it in one of the DP forums.

Detailed suggestions on how best to add and edit Jargon-related information can be found at Help:Jargon.

The General Workflow Diagram provides a graphical representation of DP's method of preparing and processing e-texts.

Activity Hub

The Activity Hub is a main entry page for the Distributed Proofreaders (DP) website, containing links to all the rounds and other workflow stages. It provides a progress overview for the various stages of e-book production since midnight of the current day and shows which stages you can work in.

For more information about the Activity Hub, see the complete Activity Hub article.


Content Providing/Provision (CP) is the process of providing the page images used in proofreading, either by scanning a book or harvesting the images from an online source.

Also a person who does such work (Content Provider, or CPer).

If you are interested in becoming a CPer, visit Access Requirements.

You can automate some content providing tasks by using guiprep and guiguts. For more information you can see the Content Providing FAQ.


See optical character recognition.

optical character recognition

Optical character recognition (OCR) is the electronic translation of scanned images of printed text into editable text.

At Distributed Proofreaders, the abbreviation OCR is used in various contexts (and tenses/forms) to refer to:

  • OCR software - the software that performs optical character recognition,
  • the process of using optical character recognition software,
  • the person using optical character recognition software, and
  • OCR text - the editable text produced by optical character recognition software.
  • For more information about optical character recognition, see this DP article.


A project is a book (or book-like thing) that Distributed Proofreaders is converting to an e-text.

beginners only project

A beginners only (also knows as a BEGIN) project is an EASY project set aside to be proofed in the P1 round by Distributed Proofreaders's newest volunteers.

Formatting Fast Track

Formatting Fast Track (FFT) projects are released into F2 immediately after completing F1. Formatting Fast Track allows F1s trying to qualify for F2 to work on projects with a variety of formatting needs that will get through F2 quickly so that they can be included in an F2 evaluation. Other F1s can also benefit from Fast Track by getting faster diffs.

FFT projects have {FFT} in their title.

P3 Quals

Some projects in P2 have (P3 Qual) after their titles. After finishing P2, these projects will move quickly into P3, skipping the release queue, and will be proofed quickly once there. They are a way for proofers who have requested (or will request) P3 access to get diffs on their pages without having to wait a long time due to the length of the P3 queues. See more information at P3 qualification.


A "retread" is a project which has gone through one or more DP rounds and then was re-proofed through the same round or rounds. This may happen for several reasons, the most common of which is to bring a project up to the current proofreading guidelines.

In 2005, many projects were "retreaded" as part of the major updates to the DP site when moving from a two-round process to a four-round process, i.e., "The Change".

Retread projects are marked with an "{R}" [previously, an "(R)"] in the project title for easy recognition and automatic detection by the site software.

type-in project

A type-in project is a Distributed Proofreaders (DP) project that does not have an OCR text when it is made available for proofing in P1.


An uberproject is large-scale, multi-volume Distributed Proofreaders project.


The Project Manager (PM) is the person in charge of a project and its progress through the rounds. The ultimate goal of the PM is to help the project be as consistently proofed and formatted as possible for the PPer. One way the PM (usually) does this is by writing Project Comments.

Different PMs have different styles. Some provide a handful of books that they pre-process themselves, then during proofreading monitor the project threads closely, and finally post-process the project themselves; others provide large quantities of books and rely on others to PP them. Other PMs fall somewhere between, perhaps closely following some books, while only glancing in on others, as questions are asked in the project thread.

If you are interested in becoming a PM, visit Access Requirements. If you are a new PM, see the Project Managing FAQ.

Project Page

Each project going through DP has a sort of "home page," called its Project Page, which serves as a nexus to the various resources on the DP site related to the project. The Project Page provides basic information about each project, including its PM, PPer (if assigned), difficulty level, genre, Special Days (if any), its current stage (round, etc.), the date it was last worked on, its Project Comments, a link to its project thread, and other information. The page can be displayed in four different levels of detail.

Project Pages are customized for each individual DPer, providing easy access to the last five pages that each proofreader has started but not completed, and the last five pages each proofreader has finished processing in that project's current round. Access can also be gained to other pages in the project, including the "diffs" for the project, via the Page Details.

Detail Levels

A Project Page can be shown in four different Detail Levels.

The Detail Levels pertain only to how much, and what type, of information is presented on the Project Page.

  • Detail Level 1 of the Project Page shows just the basic project identifying information (name, author, genre, PM, etc.) and the Project Comments.
  • Detail Level 2 shows the Detail Level 1 information plus the "Start Proofreading" button, access to the project's Concatenated Text Files, and the project's Event Subscription options.
  • Detail Level 3 adds the list of "Extra" Files in the project's file directory (the majority of which are mostly high-resolution copies of any illustrations), the project's "Transition" History, and the project's Page Summary information (number of pages saved, number of pages available).
  • Detail Level 4 adds the table of Page Details to the page so you can access your diffs directly from the Project Page.

The Detail Level you see by default when you open a Project Page depends on where you are immediately before you click a link to view the Project Page.

If you are in the Proofing Interface, and click the button to see the Project Comments (to double-check some special instruction while you are proofing, for example), then you will automatically see the Detail Level 1 project page (which is the Detail Level with no "Start Proofreading" button, so you don't accidentally start a second instance of the Proofreading Interface). You will also see the Detail Level 1 Project Page if you click on the link in the first post in the project thread.

If you are on a round's "home" page, say looking at the list of projects on the P1 page, then clicking on a project title will take you to the Project Page showing Detail Level 2. That is the one that most proofers will see most frequently.

If you are looking at a list of projects resulting from the Project Search tool, and then click on a project name to open the Project Page, it will open in Detail Level 3. (This is because the Project Search tool also feeds data into the PM interface, and PMs often need to see some of that extra info on the Level 3 page that you don't really need to see if you're just proofing, and not managing, a project.)

Pretty much the only time Detail Level 4 appears by default is when PMs (and PFs) load pages into projects, so proofreaders will only ever see that by explicitly choosing that detail option.

Again, the above lays out what Detail Level you will automatically see when. But you can always choose to change the information detail from the default/automatic to something else if and when you want to. That is all your personal choice, depending on how much detailed information about the project YOU happen to want to see at that particular moment.

PC or PCs

The Project Comments (PCs or PC) is a section in a Project Page, containing information specific to that project. These comments should be read before you start proofreading or formatting in that project. If the Project Manager (PM) wants any exceptions to be made to the regular Proofing Guidelines or Formatting Guidelines for the project, they will be noted here; instructions in the Project Comments override the rules contained in the Guidelines.

This is also where the Project Manager (PM) may give you interesting tidbits of information about the project or its author.

project discussion

See project thread.

project forum

See project thread.

project thread

A project thread (also project discussion, project forum) is a thread in the DP forum dedicated to a specific Distributed Proofreaders project.

Page Details

A table of information about all the individual pages in a project is referred to as the project's Page Details.

The Page Details information for a project can be viewed by clicking on one of these links on the Project Page:

  • Images, Pages Proofread, & Differences: shows details for all the pages in the project
  • Just my pages: shows only your DONE and IN PROGRESS pages in the project (useful for projects with lots of pages)
  • Detail Level 4 (link at the top and bottom of the Project Page): shows the project's Page Details below the Project Comments on the Project Page


See release queue.

release queue

A release queue (also queue) is a holding area for Distributed Proofreaders projects to be released into the rounds for proofing or formatting.


  1. In a specific sense, proofreading is the process of carefully correcting the OCR text's characters to match the text shown on the scanned pages of a project. This is often called "proofing", and is normally performed in rounds P1, P2, and P3. Compare to formatting.
  2. When used in a more generic sense, proofreading can refer to the entire process of getting a project ready for posting to the PG site. This is the sense in which the term is used in the name Distributed Proofreaders.


P1 refers to Proofreading round 1, which is the first of two or three rounds of proofing that each project goes through at DP. The initial OCR text is checked and corrected (except in the relatively infrequent type-in projects).

See also P2, P3, and formatting.


P2 refers to Proofreading round 2, which is the second round of proofing. The page-texts have already been proofread, and now need to have the text spellchecked and carefully compared to the image.

Because P2 proofreaders are more experienced than most P1 proofreaders, P2 is expected to fix a variety of mistakes and oversights common in the P1 round. During P2 proofing, proofers can mentor P1 proofers by providing encouraging, helpful feedback via a PM.

To see how you can qualify to work in P2, see the Access requirements article and the P2 round page.

See also P1, P3 and formatting, and a discussion of the differences between the rounds.

(From April through June 2006, when we formally changed from two to three rounds of proofing, this round was called P2alt.)


P3 refers to Proofing Round 3, which is the optional third round of proofing, in which the version of the page text produced in P2 is checked and corrected. See also P1 and formatting.

If you want to work in P3, you must satisfy the numerical requirements, and then apply for P3 qualification.

There is a team, P3 Diehards, dedicated to moving projects through P3 towards completion more efficiently by concentrating their efforts on a few projects.

(Prior to June 2006, when we formally changed from two to three rounds for proofing, this round was called "P2". See also a summary of recent changes to the DP process.)

What P3 can do.

P3 proofers examines the pages of projects in P3 for small errors. They are the last formal round for inspection of the characters on each page. Interestingly, this group of the most experienced proofers ask the most proofing questions about the project in the Forums.

P3 proofers proof the pages submitted for P3 qualification. The diffs they produce are inspected by a very small team to determine how many changes the P3 applicant missed. Only serious changes are counted. Not all diffs are errors and P3 should avoid unneeded diffs.

P3 can proof pages in P2 that were edited in P1 by relatively new proofers. These are labeled "Rapid Review". Feedback is provided to the P1 new proofer automatically based on the diffs generated. Again P3 should avoid unneeded diffs.


Formatting is the process of adding markup for italics, boldface, SMALL CAPITALS, chapter and section headers, footnotes, etc., to a project. Formatting of a project's individual pages is performed in rounds F1 and F2. Other, more project-wide, formatting is done in the PP stage.

See also foofing, and compare to proofreading.


F1 refers to Formatting round 1, the first round of formatting, in which markup for italics, boldface, SMALL CAPITALS, chapter and section headers, footnotes, etc., is added to individual pages in a project.

To see how you can qualify to work in F1, see the Access requirements article and the F1 round page.

See also F2, proofreading, DP-feedback, and Formatting Mentoring.


F2 refers to Formatting round 2, the second round of formatting, in which F1 markup is checked and corrected.

To see how you can qualify to work in F2, see the Access requirements article, the F2 round page, and this forum post.

There is a team, F2 Fanatics, dedicated to moving projects through F2 towards completion more efficiently by concentrating efforts on a few projects. The F2 Fanatics project list shows the team's current and previous projects.


Each round has a Daily Goal (DG) which is the number of pages DP is aiming to proofread or format in that round for the given day. The daily goal for each round is visible in the top right corner of each round's page. It's labeled "Today's Goal" (just to confuse you!).


Post-Processing (PP) is the process of formatting and reassembling the pages of a project after it has completed the rounds of proofing and formatting. (Also called Post-Proofing.)

Also, a person who does such work (also Post-Proofer, or PPer).

If you are interested in becoming a PPer, visit Access requirements.

See also the Post-Processing FAQ, and Hands-on PPer. For more PPing resources in the DP wiki, see Post-Processing Advice. For LaTeX projects, see LaTeX postprocessing guidelines.


The goal of Smooth Reading (SR) is to read a post-processed text attentively, as for pleasure, with just a little more attention than usual to punctuation, etc. This is not full-scale proofreading, and comparison with the project's scans is not needed. Just read it as your normal, sensitized-to-proofing-errors self, and report any problem that disrupts the sense or the flow of the e-text.

Smooth Reading: also referred to as Smooth-Reading, SRing, smooth-reading, smooth reading, Smoothreading, smoothying, and many other variations.

Smooth Reader: person who Smooth Reads e-texts; also affectionately known as an SRer, smooth-reader, smoothier, smoothyer, smoothie, smoothy, etc.

For more information, see the Smooth Reading FAQ and visit the Smooth Reading Pool.


Post-Processing Verification (PPV) is the process of final checking a post-processed text, done by a very experienced PPer. This is the last stage a project goes through at DP before being sent to the PG Whitewashers.

Also, a person who does such work (also PPVer).

Related Resources


Direct Uploading


Jargon Guides

You know: that place where all of the finished DP projects go.

Project Gutenberg (PG) is DP's "parent site," which hosts a growing online archive of public domain electronic texts available freely to all. See gutenberg.org.


Whitewashers (often abbreviated as WW) is the widely-used nickname given to the Project Gutenberg (PG) Posting Team. This name is in honor of the famous scene from Tom Sawyer and helps remind everyone of their tireless tasks. Their work is also usually referred to as whitewashing.

The actual posting of an e-text to Project Gutenberg is done by the Whitewashers. As described in Project Gutenberg FAQ, their main job is to verify copyright clearance for a potential e-text has been obtained, follows the standards, is basically correct, add the PG headers, and, finally, copy the text to the two PG servers.