Warning not to edit deprecated verson of migrated project

Question

After a project is migrated to PT8, will there be a warning to users who still have edit rights to it in PT7, not to edit it? If not, then shouldn’t there be?

Is there a best practice written up somewhere that helps avoid this issue?

Answer 1

After doing due diligence to notify all users and get their changes, as Shegnada mentions above, my procedure is to do the following to the PT7 project after migration:

• Add: Migrated to PT8 - to the beginning of the Full Name on the Project>Project Properties and Settings>General tab
• Uncheck Editing Enabled on the Project>Project Properties and Settings>Advanced tab
• Make all users on the project observers, so they can neither edit nor comment on the old project.

If I have changed the short name of the project during migration to NewName, then I add the following to the beginning of the Full Name of the PT7 project: Migrated to PT8 as NewName -

You might want to also add to the beginning of the Full Name: Do not edit. That way the warning stays with the project from then on.

Comments

CrazyRocky:

1. Add: Migrated to PT8 - to the beginning of the Full Name on the Project>Project Properties and Settings>General tab
2. Uncheck Editing Enabled on the Project>Project Properties and Settings>Advanced tab
3. Make all users on the project observers, so they can neither edit nor comment on the old project.

This should be published as a best practice!

I have been doing your third step, but I like your first and second points, too.

But I still think that PT could have an option at migration time to do this for you. If you had 30 users with non-Observer roles (one of our projects has close to that), then it’s quite a job to switch them, one-by-one, to Observer .

---

It’s actually not particularly hard or time consuming to change 30 people to Observer status assuming you are an Administrator and want everyone else to be Observers. You don’t have to do a send receive after each role change. Just once at the end.

---

But I thought the point of computers was that the tasks that are no brainers and/or repetitive are done by the computer.

Answer 2

If you are migrating, you need to collect a send/receive from all users and
inform them to stop editing and using Paratext 7. You need to be especially
careful with those who are not able to send/receive to the internet or do
email regularly. After you migrate a project, go back to the Paratext 7
project and change all Users to Observers except yourself and take away
editing rights from yourself also. Anyone who belongs to that project
should be doing send/receive first before editing and, if so, they will
then not be able to edit the project and will come to you asking for help.
If they don’t do send/receive before editing, they will lose those edits.

Blessings,

Shegnada J.

Language Technology & Publishing Coordinator, SIL Nigeria

Complex Script Layout Specialist, GPS Dallas

Skype: Shegnada.james.

([Phone Removed]

Comments

Shegnada:

If you are migrating, you need to collect a send/receive from all users and

inform them to stop editing and using Paratext 7.

Yes, after I posted, I migrated a project, and a list of instructions and warnings was displayed before I proceeded. But I wonder why it can’t also be enforced by PT itself. Anyone think I should submit that as a feature request?