Db-req

From DPWiki
Jump to: navigation, search
DP Official Documentation - Content Providing and Project Management


Contacting db-req

Send an email to db-req at pgdp dot net if you need any of the tasks listed in the ToC done. If you wish, you may also contact db-req via an internal DP form.

What is db-req

db-req is also the place to ask if you need any other changes made that can't be done by PFs and that you suspect involve changing the database.

Please include all the relevant information in the body of the email, not just in the subject line (projectID(s), PM username, PP username if appropriate, what needs to be done, and any additional information required in the sections below).

You can include several requests in a single email, so long as they are either the same type of request (e.g., several round skips) or to do with the same project. Please send separate emails for unrelated requests.

If you've got a project that's in really bad shape, and won't be able to fix it yourself, please put it into the Project hospital.

Although we do our best, requests may take some time to be handled, depending on the availability of volunteers. We would normally aim to handle straightforward requests within 2 to 3 days, although we often do better than that. If we have any technical problems with requests, we get back to the requester, so in most cases no reply simply means that nobody has been able to get to the request yet.

Important: Whatever the request, projects in PP/PPV status with outstanding db-req request(s) should not be uploaded to PG until db-req notifies you that the requests have been completed.

Add a PM queue

Your email should include your dp username and the round for which you want a PM queue. They are currently available for P1, P2, and P3. F2 PM queues are also available as a trial experiment (possibly becoming permanent).

A PM queue ensures that a PM always has one project available in that round (assuming they have a project that can be available, obviously).

Add or replace illustration images for a project

Your email should include your dp username, the name and projectid of the project for which you want to add or replace images, and the location of the images.

The images should be in a zip file, and that file located either in dpscans or in a publicly accessible location on the internet (your personal webspace, dropbox etc.) if you don't have dpscans access. Do not attach the zip file to your email, since db-req is not set up to handle email attachments.

Do not name any of the new illustrations in such a way that they will overwrite existing page-images or illustrations. (If you do want the new files to overwrite the old ones, specify that in the request.)

Delete illustration images from a project

Your email should include your dp username, the name and projectid of the project from which you want to delete images, and which images to delete.

Add music files to a project

Your email should include your dp username, the name and projectid of the project for which you want to add music files.

The music files should be in a zip file, ideally named projectIDxxxx_music.zip. The file should be located either in dpscans or in a publicly accessible location on the internet (your personal webspace, dropbox etc.) if you don't have dpscans access. Do not attach the zip file to your email, since db-req is not set up to handle email attachments.

For more detailed instructions, see the Music Guidelines.

Skip a round

If you plan to request a P3 or F2 skip, please remember to put a note prominently in the project comments, warning proofers and formatters that it's a possibility. This will avoid P2 proofers and F1 formatters getting upset because the pages that they worked on are not available for evaluation purposes. If it is unplanned, and a PPer request, make sure that the P2 or F1 pages were proofed long enough ago that they can't be used for evals.

Your email should include your dp username, the name and projectid of the project that will skip a round, and the round that should be skipped.

In order to skip a round, the project should be either unavailable or waiting, with no pages proofed, in that round. We can't take advance bookings for round skips.

When deciding whether a project can skip a round, the PM/PPer should consider the quality of the proofing (or formatting, as applicable) in the previous rounds. In order to skip a round, either there must be an assigned PPer, who is then committed to PPing the project, or the PM has done checks similar to those in P3 skip evaluation and is prepared to justify to db-req that this project has minimal defects.

A project can't be sent back through a skipped round.

The usual circumstances under which a project can skip P3 or F2 are these:

  • The project has an assigned PPer, who agrees to the skip and is committed to PPing the project (unless the project has been through P2 and is a retread), and the PPer has no more than five projects currently checked out for PPing and available to work on (i.e., not waiting for missing pages, clearance, etc.). This limit may be relaxed for PPers who have a track record of posting large numbers of projects, and is applied less rigidly for P3 skips than for F2 skips, or
  • To skip P3, the project has been through P2, and has been validated by the PM


The email can be sent by either the PM or the PP (if applicable), but should include the dp usernames of both, and confirmation that they've agreed to the round skip.

See also P3 skip evaluation.

Move back to P2 from P3

Your email should include your dp username, and the name and projectid of the project that you want to move back into P2.

The project should be either unavailable, or waiting in P3 with no pages proofed in P3. It should have skipped P2, either explicitly or because it didn't go through P2alt.

Moving back to P2 from P3 is especially suitable for projects that might then be able to skip P3.

Repeat a round or go back to a round

The PM (or PPer with PM agreement) can ask for a project to repeat any round. The requester should be aware that all existing proofer information will disappear from the diffs page, and the username->page association will only be available via the project snapshot.

The requester's email should include their dp username, the name and projectid of the project concerned, the round the project should be moved back to, and the round whose output should be used as the input text. The project should be Unavailable for a round following the round to be repeated.

The input text will be put into the OCR slot, and the project moved into the round that you've requested. The project will have a tag added to its project title of the form {Xn->Ym}, where Xn and Ym are the rounds from which the text was taken and into which the project has gone. Proofer information for the previous pass through the rounds will no longer be visible on the project page, but will have been backed up and is accessible here.

Example: For a P1 repeat, the project should be in P2 Unavailable; the round to take the proofed text from would be P1 and the round that the project will be moved to is P1.

Retread a project

When a project that's currently in PP is sent back, it's called "retreading" the project. The PPer (it's obviously a good idea to get the agreement of the PM, too) may request that a project that's in PP goes back to any round.

Projects that were retreaded when we changed from 2 to 4 rounds have {R} in their names, and not all prior proofer information was retained.

Change PM

Your email should include the dp usernames of the old and new project managers, the name and projectid of the project concerned, and the reason for the change.

Delete a project

Your email should include your dp username, the name, projectid and current state of the project that you want deleted, and the reason for the deletion.

If the deletion is because it's a duplicate project, or has some other relationship to another project, we need the projectid of that other project, too.

Merge projects

Your email should include your dp username, and the names and projectids of the projects to be merged. The projects must all be in the same round, and have been through the same rounds. See also the section on adding missing pages.

There are two common situations in which projects need to be merged: projects that were split into parts to go through the rounds, and missing pages projects.

Projects that were split into parts to go through the rounds are typically BEGIN or Qual projects. They should be merged before they are PPed.

Replace page scans

Your email should include your dp username, the name and projectid of the project, and the location of the new scans.

The new scans should be in a zip file, and that file located either in dpscans or in a publicly accessible location on the internet (your personal webspace, dropbox etc.) if you don't have dpscans access. Do not attach the zip file to your email, since db-req is not set up to handle email attachments.

If there are only a few scans to replace, it's easier to do it yourself (if you are the PM) or get a friendly PF to do it, using the "Fix" option on detail level 4 of the project page.

Split a project

This is usually only done for BEGIN, Qual, or Newcomer only projects. Your email should include your dp username, the name and projectid of the project, and the reason for splitting.

If you are a PM, you can help this process a lot by creating the extra new projects that will be needed, and telling us which pages in the old project need to go into which new project. In this case, also tell us if the new projects should belong to a PM other than yourself.

Splitting projects is probably the most time-consuming db-req task at the moment, and often leads to a project merge down the line. Merging projects is the second most time-consuming task. So please only request project splits if they are necessary; for example, if the resulting projects will be posted to PG separately.

Missing pages

If there are blank pages missing, please provide a list of the proofing images that those blanks follow. For example: “Please add missing blank pages following 003.png and 004.png.” If the only pages that are missing are blank, there is no need for an MP project, just a list of where the blank pages should go.

For PMs

To add non-blank missing pages to a project that has left P1, you need to make a new project for the missing pages. The new project should have the same author, clearance, etc. as the main project. The title should be the same, with the addition of "[missing pages]", but without any status information (such as rounds skipped or {P3 Qual} or indeed anything in {}). E.g., the MP project for "An Interesting Book {R} {P3 skipped}" would be "An Interesting Book [missing pages]".

If you are the PM for the main project, the easiest way to create the new project is to use the "Clone this project" link on the project page. If you aren't a PM, and can't make the new project yourself, just email db-req with the details and we'll handle it for you.

  • Number the missing pages so that they will end up in the correct place in the main project after a lexical sort: for example, if there are two pages missing between current pngs 012 and 013, call the missing pages 012a and 012b.
  • Leave the new MP project in the "New Project" state, or put it into "P1 Unavailable." Do NOT release it yourself!
  • Send email to db-req including your dp username, the project name and projectid of the missing pages project, and the project name and projectid of the project into which they are to be merged. It's also useful if you say what state the main project is currently in. Here's a template you can use for your Email:
 Subject: MP project: <number of pages> pp. Needs <rounds needed>
 
 projectID############# - <Project Name> [missing pages]
   to be merged into
 projectID############# - <full Project Name>
   current state: <state of original project>
 
 Thanks,
 
 <yourname> (<dp-username>)

Example:

 Subject: MP project: 3 pp. Needs P1, P2, F1
 
 projectID123abc3456yoi - An Interesting Book [missing pages]
   to be merged into
 projectID543sdfig456rt - An Interesting Book {R} {P3 skipped}
   current state: F2 Unavailable
 
 Thanks,
 
 not a squirrel (notasquirrel)

You can also send this information via an internal DP form.

  • Db-req will push the MP project through until it is in a compatible state, and then merge the missing pages into the main project.

Please do not try to push the project through yourself.

Db-req can push the MP project through exactly the same rounds as the main project, which simplifies the merge steps required, especially if the main project skipped any rounds, or is too old to have been through P2.

Note that the MP project has to go through the rounds, even if you don't need the proofed output.

If there are illustrations missing (for example, the MP project is for the purpose of proofing the text of captions for missing illustrations and/or you need to add additional high quality illustrations to the original project) please zip the high quality illustrations together, upload it to your dpscans folder separately, and include that information in your email to db-req. Please do not include them in the MP project.

For PPers

If you discover, as you are PPing a project, that it has pages missing, and get no response from the PM, please send an email to db-req specifying the title, the projectID, and your username. If you have attempted to contact the PM and had no response (usually, giving the PM two weeks is generally a good idea), please mention that in the email.

Reorder pages

If proofing images and text get loaded out of order, and it isn't discovered until after proofreading has started, please don't use the "Fix" link from the page details page to rearrange images and text. Please contact db-req with the details and ask for the images to be reordered. If you use the "Fix" link you create a disconnect between the round for which you changed the text and previous rounds' text, thereby creating unnecessary diffs.

Note that if the project is still in P1, and proofreading hasn't been done on those pages, it's okay to reload those pages that haven't already been proofread.

Upload large project to PPV

The page to upload projects to PPV sometimes chokes on zip files that are more than a few MB in size, throwing the error "Don't know how to handle stage=".

As long as your zip file is too large for good reasons (i.e. the images are all well processed, but there are simply a lot of them) then you can use the following method to upload to PPV. Note that the zip should contain all of the files you want the PPVer to be able to download.

  • If you have a dpscans directory, upload the zip there. If you are not a PM and don't have dpscans access, make the zip file publicly available on the internet somewhere (can be your personal webspace, dropbox etc.). Do not send the zip as an attachment to db-req.
  • Make a text file called placeholder.txt and containing something like this
This is a placeholder. The zip file was too big to upload by the usual method. 
Awaiting squirrel intervention.
  • Zip this file and upload it to PPV as if it were your zipped PP project, including your comments for the project as normal.
  • Email db-req, providing your username, the project name and project ID, and the location of the zip file

Example:

Subject: Large upload for PPV

I've tried and failed to upload this to PPV
projectID543sdfig456rt - An Interesting Book {R} {P3 skipped}
so I've uploaded it to dpscans/johnd1234/interesting.zip (or link to public web location)
Could you replace the file in PPV with this?

Thanks,

John Doe (johnd1234)

Non-PM access to dpscans

See Remote File Manager for more information.

To request access, please send an email to db-req -at- pgdp -dot- net, with your username, the type of access you're requesting, and your reason for requesting access.

If you wish, you may also contact db-req via an internal DP form. Reply will be made by email using the email from your user prefs.

Test server

From your member details page on the test server (because it is a test server), you can grant yourself access to P2, P3, F1, F2, PP and PPV; if you need to be a PM on the test server, drop us a note in db-req. Be sure to say what your username is on the test server, as well as your username on the main site. If you don't have PM access on the main site, and are requesting it on the test site, it would be helpful if you said why you want it on the test site.

To comment or request edits to this page, please contact Monicas wicked stepmother or DACSoft.

Return to DP Official Documentation Menu