Presentation is loading. Please wait.

Presentation is loading. Please wait.

Project Sharing in Paratext 7.1 based upon ICAP’s Paratext 7.1 Project Sharing Manual.

Similar presentations


Presentation on theme: "Project Sharing in Paratext 7.1 based upon ICAP’s Paratext 7.1 Project Sharing Manual."— Presentation transcript:

1 Project Sharing in Paratext 7.1 based upon ICAP’s Paratext 7.1 Project Sharing Manual

2 Introduction Paratext 7 enables project teams to easily and safely share project data using a feature called Send/Receive. In order to make sharing possible, Paratext maintains a detailed history of all the changes being made to a user's project files inside a container called a repository.

3 Project Repository A project repository is: Container of project copies Historical records Project folder is “.hg”, Never move or modified Belong to a particular person Never send anything to anyone else’s repository directly

4 Project Copy Refers to the storage of info about the revisions made to a project’s file Repository contains hundreds of copies Compact list of changes that have taken place since previous copy Repository can contain project copies from many different users made at different times

5 Send/Receive A Send gathers all the project copies from your local repository on your computer and copies them to another repository belong to you. A Receive gather project copies from other people’s repository & duplicates them in your local repository

6 Project Sharing Roles Observer – receive data, no changes Consultant – receive data, can add notes only. Translator – receive date, can add notes and can change text of any book assigned to him by the administrator Administrator – can do anything, sets up and maintains sharing activities

7 Administrator Should know how to: review other users’ changes work with project history compare texts resolve merge conflicts add/remove users, change their roles & give editing assignments.

8 S/R vs Backup/Restore Backup saves current project data to zip file. Restore adds project data to a computer. S/R maintains the entire history, not just current data. Can be use as a backup. Do not mix the two.

9 S/R Setup All users must be using 7.1 Only one administrator Get exact Paratext registration name Get current copies of project data (Use backup and restore) Restore current copies as a new project onto Administrator’s computer. Compare texts & resolve differences

10 Setup – Configuring Users In Project menu, select Users, Roles and Permission Checklist. Add user (need registration name) Change Current copy of project data (Use backup and restore) role Assign books and specific chapters.

11 Setup – Configuring Users Do NOT assign same book/chapter to multiple persons Administrator must receive changes before they are received by others.

12 Setup – Initial S/R Administrator computer Send/Receive Projects dialog box Internet Server – UBS managed USB Drive Network Shared Folder Shared Projects List Click Send/Receive

13 Setup – Initial S/R User computer In File menu, click Send/Receive Projects Select project. If list is empty, no projects are shared with you Click Send/Receive

14 Setup – Sharing Devices Sharing one using mutiple devices One project can use the internet user and another project can use USB drive Can change from one to another in same project

15 Ongoing S/R In File menu, click Send/Receive Projects Can reset checkbox for a project, if you do not want to Send/Receive. Send/Receive as often as you work on the text, at beginning and ending of a work session

16 Reviewing Text Changes Compare Texts in Tools menu Right-click inside a verse. View History for verse View Project History in Project menu Review Recent Changes in Project menu (available to administrator only)

17 Managing Conflicts Paratext accepts the one with the most changes. The other becomes a conflict note which needs to be reviewed Show Conflicts in Project menu. Click blue reference link Click blue edit link Resolve note

18 S/R Maintenance What data is shared? What data is not shared? Who can make changes to what Understanding the flow Changing administrators Troubleshooting

19 Shared Data Translation Text Notes Project properties & language settings Biblical terms rendering interlinearizer data Wordlist data Project progress

20 Shared Data Pictures Print draft configuration files If you created a folder named “shared”, within My Paratext Projects folder, any files in that folder will also be included in Send/Receive

21 Not Shared Data A folder named “local” within My Paratext Projects Folders created by Publishing Assistant

22 Who can do what View textAll (including Observer) Edit textAdministrator, Translator Add notesAdministrator, Translator, Consultant Project propertiesAdministrator Other project dataAdministrator, Translator, Consultant Edit assignmentsAdministrator, Translator sometimes

23 Understanding the Flow Peer to Peer

24 Understanding the Flow via Administrator - Users

25 Understanding the Flow via Administrator - Admin

26 Changing Administrators Recommendation: only one administrator Current Admin: first change user to administrator & then S/R New Admin: first S/R & then change current administrator to new role & then S/R

27 Troubleshooting Use S/R for backup To restore use S/R Speed of Internet is not as important as its stability for S/R to internet service Do not touch repository folder:.hg Do not user Mercurial s/w outside of Paratext to synchronize data


Download ppt "Project Sharing in Paratext 7.1 based upon ICAP’s Paratext 7.1 Project Sharing Manual."

Similar presentations


Ads by Google