Project Registration Reviewer’s Guide

Project registration reviewers are responsible for reviewing all project registrations within their organization. They will typically have a management role in the translation department of an organization and will know about the translation projects that are being undertaken.

Page Contents

Project Registration Reviewer Webinar

Watch the webinar about Project Registration Reviewers here, or read the written instructions below.

Email Notifications

Reviewers will receive periodic emails with the subject: Project Registration Report for [name of organization]

At the top of the email, there will be a link to an online version of the list of recently registered projects.

Note that the contents of that list will only be visible if you are logged in to the registry with the account that has the role of Registration Reviewer.

Using this webpage is actually preferable to reviewing the list in a static email, because the online version will have the most current results.  The email should serve primarily as a reminder for you to review your organization’s recent projects list here in the registry. It may be best to bookmark the page above and review it on a regular schedule.

Internal Project Registration Review

Newly registered projects go through a 4 week period of internal review to give your organization the opportunity to check and, if necessary, to amend the information about the project. Registration information must be accurate, and as complete as possible. Only after this internal registration review period are the details made available for external review by all Paratext member organizations (details in the next section).

What to do about errors

A reviewer without additional administrative permission may not edit their organizations registrations directly, but they are expected to contact the project’s administrator to resolve any issues they find.

What to check for

Project Full Name and Description

Are the name and description complete so that other reviewers will understand what this project is?

Language

The primary language subtag (a two or three letter code) must be accurate. In some cases, languages will be incorrectly marked as [EN] for English, because the language code was unknown at the time.

For those with edit permissions, there is an Advanced checkbox that allows the project to provide additional precision if the primary language subtag is shared by more than one dialect or variant.  This section should not be used unless it is needed to further distinguish between existing varieties of the language or script. Here is more information on how to choose language tags.

Scope

Make sure that the scope accurately reflects the goals of the translation project, whether a whole Bible, a New Testament, or portions.

Notes

  • Portions are one or more whole books.
  • Selections are usually selected passages from one or more books, not including a whole book.

Translation Type

It is important to distinguish between First, New, and Revision (and sometimes Study / Help Material).  Occasionally translations are marked as First when there is an older translation that already exists.  First means that it is the first translation work being done in a given language.  New is selected when a translation already exists in the language.  Revision is selected only when the project is a revision of an existing translation.

Country

Make sure the country or countries that the local language group is in are listed.

Status

The status can range from Projected ▷ Active ▷ Typesetting ▷ Completed ▷ Published, or it can be set to Inactive if no work is being done. Whatever is indicated should accurately reflect the project’s status.

Date Started and Expected Completion Dates

While not required, it is important to know this information about a project.  The expected completion date actually helps the team get more accurate projections of their rate of progress.

Project Visibility

Verify that the visibility is set correctly.  If it is a back translation that is not intended to be published, it should be set to Test/Training.  If it is marked as a confidential project, the reviewer should make sure that the reasons for confidentiality are sound.  Occasionally, copyrighted texts are found in the registry that are marked as Test/Training projects.  Even for training, purposes, the author’s permission must be granted. It is important for you to detect these and correct them before the second phase of the review process.

  • Standard – a project is working toward a publishable result and may be reported externally.
  • Confidential – a project is working toward a publishable result but must not be reported to other Paratext organizations due to the sensitive nature of the work. Only administrators and registration reviewers in your organization can see these.
  • Test or Training – a project that is not working toward a publishable result and should not be reported internally or externally.

Below the solid line

You should try to ensure that there is accurate data here in answer to the questions:

  • Church or other faith community represented
  • In what respects is your translation unique? How does it relate to any existing translations?
  • Describe the needs this translation intends to fulfill.

Very often these are left blank because they are optional.  We don’t want to slow people down when they are registering a new project, but this information is precisely what helps you do your job, and especially for the external review.

For a standard project, this information is what helps reviewers in other organizations to discover the unique target audience of the translation that would justify a second translation in a limited resource language. And if two organizations are working for the same target audience without each other’s knowledge, you can connect them so that they have the option of joining forces.

For a confidential project, this information will help the reviewer understand the reason for the confidentiality, and the project can rest assured that this information is only visible to administrators and reviewers in the organization.

With reference to project visibility, all projects which are set to “Standard” project visibility in the Registry will have their project progress reported via the public-facing progress.bible. This system is under development by SIL, but not yet deployed. The Paratext Registry will be a major source of information for this system.

External Project Registration Review

After the internal registration review period, projects with Standard visibility will be reported within the Registry to the registration reviewers of all organizations that have been approved to use Paratext. These reviewers will only have access to the information on the Basic tab of the project. This notification serves the following purposes:

  • Promoting partnership in existing languages. A team may contact another organization who is working on a project in an area or language of interest to them.
  • Upholding FOBAI translation principles. If a project is not fulfilling its agreement to abide by the FOBAI translation principles, the matter can be brought to the attention of the Paratext Board of Governors (boardofgovernors@paratext.org) for possible action.
  • Avoiding competition. Projects that are doing translation in competition with existing projects can be limited to Translator Tier access in some cases. Concerns may be addressed to the Board of Governors if no understanding or compromise can be reached by the two parties.

The Board of Governors of the Paratext Alliance has decided not to register organizations/projects that:

  • Can be associated with infringement of copyright and plagiarism, not honoring licensing agreements, etc.
  • Are engaged in socially irresponsible behavior,  including obscenity, defamation, incitement, etc.
  • Are engaged in activities deemed as damaging to the Church in general and the Bible Translation movement in particular

In cases of doubt, the final decision rests with the Board of Governors.

Was this helpful?