Changing BT to daughter or auxiliary files

Question

Please remind me of the process of changing Back translation registry entries from registered projects to daughter or auxiliary files to the main project.
I need to share this with a quite a large number of users so we can clean this up in the registry.

Answer 1

A project administrator (Administrator of both the project being changed, and the project listed as the source) can change the project type by going to Project Properties and settings and selecting the new type. A back translation shouldn’t be in the registry anyway, it should use the registration of the source project. So if something labeled “Back translation” is in the registry, its type was probably incorrectly set to “Standard translation”.

image.png599×622 16.4 KB

Answer 2

The step by step instructions are located in this article:
https://pt8.paratext.org/2018/01/04/migration-preparation-issues/

Answer 3

My question, to which I have not found an answer, is this: What is the difference in functionality between a daughter project and a back-translation? Or is it merely a different in registration?

Comments

Thanks for joining the group!
I don’t think there is a functional difference in Paratext behavior.

A daughter project is usually a related language and must have its own registration.

A back translation is usually for internal use by the team and should not be registered

They both have the check boxes to show whether they are in sync with the primary project or not.

Answer 4

I have a user who registered a BT project as a standard project, and then changed the project type in Project Properties and Settings to a Back Translation project.
After they did this, I checked in the registry, and the Back Translation still shows as a registered project.
Since the project type was changed, will this eventually correct itself, or what process should be followed to correct things?
Thanks.
BEH

Comments

He has to remove the old entry from the registry.

He should be able to go to Delete project, select the project, then look on the “Other actions” list and pick “Keep only my copy, delete for others; delete registration.” He clicks OK and that will remove the registration and the server copy for other users. But he can do a new send/receive of his copy, and that should restore the server copy for anyone else that is part of the back translation project.

Answer 5

I realize now I didn’t look at this as closely as I should have. I don’t think we want to tell people to make a back translation that was registered as a standard translation into a daughter project, but to make it a back translation project.

A daughter translation still requires a separate registration, while a back translation does not.

Answer 6

Thanks for the answer. I know that before changing the type of project, he should have deleted the project from the registry like you mentioned. However, he didn’t do that, he just changed the type in Properties and Settings. Since he has already changed the type, I am wondering if the project in the registry is still linked to that project now designated as a BT, etc., or if the current project in the registry is now unlinked, due to the fact that the BT should now be included in the registration of the main project.
I am not sure what happens when the type of project gets changed like that, so figured I would ask first.
Thanks