0
344 次瀏覽

I have a user who has a notes project for his consultant checking. He types one or more notes per verse into the verse text itself, and then uses those as a guide when he is doing consultant checking.

He is not interested in using the “Consultant Notes” feature, he would rather just stick with using the project itself.

My question is how I migrate it to PT8, specifically what settings I choose when I register the project. It is not really an Auxiliary project to their language project because it is not language specific. I noticed a setting on the Registration Page that said something like “No Linguistic Data” for language. I also saw “Help / Study Material” as an option. Would those be appropriate in this case?

Thank you for your suggestions,

SIL+LSS+PNG

[cid:[Email Removed]]

SIL+LSS+PNG
Language Technology Consultant
SIL PNG Language Resources
Ukarumpa EHP 444 | Papua New Guinea
[Email Removed].pgmailto:[Email Removed].pg

image

舊文章 - 以原文顯示
Paratext (411 點) 提出
已重新顯示 | 344 次瀏覽

1 個回答

0
最佳回答

The Auxiliary project type is the correct type to use for that type of project. Note that the restriction on the users and roles in an Auxiliary project type have been removed since that help was created.

舊文章 - 以原文顯示
[Expert]
(16.7k 點) 提出

That is true even though the project is not related to any particular language?

Is this a problem if we have already migrated all of their other projects?

Thanks,

SIL+LSS+PNG

舊文章 - 以原文顯示

Oh, I completely missed that it’s a consultant’s note project and not project-specific. :neutral_face:

There is probably no “perfect” way to migrate and register the project, then. The best way would be to make it into a Consultant Notes project (but you said he doesn’t like that idea), so I would say he has to pick another project for it to be an “auxiliary” of and change it to be an Auxiliary Project.

It shouldn’t be a problem that the other projects have migrated (assuming they weren’t converted). Just make the project an Auxiliary Project in PT7 and then migrate only that project to PT8.

舊文章 - 以原文顯示

I would suggest migrating the project and making it a Test project in the registry. I know of several consultants who have been putting their observations about the New Testament and Old Testament into a project that they created for that purpose years ago. Some have simply migrated their project and have continued to add information to the project.

舊文章 - 以原文顯示

相關問題

0
4 個回答 513 次瀏覽
I've been helping a user with the registration\migration process. We were able to migrate the actual project as well as a ... Can you advise us on how to resolve it? Thank you.
MSEAIT_LT 478 提出 已提問 1月 23, 2018
0
3 個回答 495 次瀏覽
In Paratext 8.0, a project created in an earlier version of Paratext must be migrated in Paratext 8.0 ... . Only project administrators and consultants can migrate a project.
[Expert]
anon421222
735 提出
已提問 2月 23, 2017
0
1 個回答 250 次瀏覽
Trying to migrate a back translation project to Paratext 8 and have run into a problem where we get as reason for the ... . The ticket reference is PTXS-17256 Thank you, MSEAIT/LT
MSEAIT_LT 478 提出 已提問 7月 31, 2018
0
1 個回答 315 次瀏覽
I try to migrate from 7.5 to 8 in in Kuvi project. I try to follow the steps in proper way. I was able to register ... three times still it is showing same. How can I migrate to 8.
anon480013 162 提出 已提問 6月 22, 2017
0
7 個回答 2.1k 次瀏覽
In Paratext 8.0 (and later): You cannot migrate resources from earlier versions of Paratext. Resources have a different ... See also: How do I install a Source Language Resource?
[Expert]
anon421222
735 提出
已提問 2月 23, 2017
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
And let us consider how we may spur one another on toward love and good deeds, not giving up meeting together, as some are in the habit of doing, but encouraging one another—and all the more as you see the Day approaching.
Hebrews 10:24-25
3,048 個問題
6,007 個回答
5,672 則評論
2,028 位使用者