In any translation, good communication between the team members and consultants is an essential ingredient for success. The send/receive function in Paratext enables this communication even if they are miles apart. This video explains more.
Receiving a project for the first time
Verify you have access
To receive a copy of a shared project, you need to be on the list of project members. Each project has one or more administrators that can add people to the project and define what books they can edit, or what other roles they can do in the project. If you are not sure you have been added to the project you want to work on, contact the project administrator to find out.
Receiving the project
Watch this video about how to use send/receive to get a copy of a project that is shared with you.
The term Send/receive and receive : In this video I demonstrate receiving a project for the first time, then doing a send/receive to share work with others. Both of these use the send/receive command. Some might wonder if there is a way to only receive, or only to send. There is not, send/receive always sends whatever changes you have made, and receives what other changes others have made.
Info - more about ChorusHub.
Chorus Hub is a simple program for setting up a shared network folder if you do not have a network server. If your team works in the same office and your computers connect to one another on a network, but you don't often or always have Internet connection, Chorus Hub may help. For more information or to download the program go here:
The methods for receiving a shared project for the first time include
USB or flashdrive
mark as True all the means by which you can receive a project
A danger with shared projects: conflicts
What is a conflict? Why are they so bad?
Watch the video
Conflicts are a danger when .
How Paratext shows you about a conflict
This is what you see in Paratext if a conflict comes up.
More about conflicts
You get conflicts when two people edit the same verse at the same time. You do not get conflicts when people write notes at the same time -- even if they put in notes about the same verse. It is only editing the text that can produce conflicts.
The parts of the text that are most prone to conflicts are the introduction and non-Biblical text books like the glossary. Introductory paragraphs are all the "same" verse, so two people editing the same introduction, even if they are editing different paragraphs (as in the video example) will produce a conflict.
The glossary is another case of an entire book that is prone to conflict. Since it has no verse numbers it is all "the same verse."
Paratext indicates a conflict by
A special note in the project
A message when the send/receive process finishes
Special formatting of the text in the project
Mark the options as true or false.
A conflict note flag looks like
Click the correct image
Working with a shared project
Verifying your editing permissions, send/receive as you edit
Watch this video about how to work in your shared project
Which of the following are ways to know you can edit a book?
Your name appears in the title bar when you are in that book
The text is gray in color when you cannot edit the book
You can see what books you can edit in Users, Roles and Permissions
When is it important to do a send/receive?
After you have made changes in the text
To get the latest work from your colleagues
The send/receive function provides another useful tool, the Project History.
Watch this video about it.
Tip: You can bring up the Compare texts window without going through the project history. Go to Tools, then Compare texts, then you can select an older version to compare in the right hand pane.
You can even use the tool to compare the text in two related but different projects. You can select a different project in the right hand pane to compare with the project in the left pane.
To bring up the project history, you first go to which menu?
Where would you click to choose an earlier version of the text to compare with the current version?
Getting your shared project on a new computer
Send/receive to a new computer
If you get a new computer, the easiest and best way to get your shared project on your new computer is to do a send/receive to get a new copy of the project from the server.
You, or computer experts around you, might think the project data could be just copied from the old computer or restored from a backup file. Don't do this, use send/receive. This video shows how.
Which of these statements are true?
If you replace your computer, the best way to get a shared project on your new computer is to use send/receive
Copying files, or restoring files outside of Paratext can create problems with a shared project