Accepted, Not Yet Planned

If the project and the return kit do not match, warning message is displayed when importing the return kit.

If the project and the return kit do not match, warning message is displayed when importing the return kit.

for example
By wrong I mean like importing a return kit for English to a German project or vice versa.

by mistake imported a return kit that was not the one I was planning to import.
It made me scared that I may have overwritten the data with the wrong return kit.
I don't know what happened but the translations were imported to its correct project.

I would know that something is wrong if I check the publications.
but I would never know if I was the one that messed up importing the wrong return kit or if the translation itself were never in the return kit.

Satoru Nakamura

  • Hi Eric

    Thank you for comment.

    >What i remember from discussions with SDL and with my own testing, is that when on the projects page or tasks page, it there is currently no correlation to what is being imported.

    That's right.

    >I think the best you could hope for that is easy would be to make it known what project was being imported on the import screen.

    User can confirm by Log of WS11.1 .

    >Additionally, you cannot import a return kit to a task that is not claimed by you so unless you export all tasks from WS yourself, this issue shouldn't occur all that often.

    We want to reduce the risk of mistakes.

  • Given the way that imports are handled this would require if i recall correctly, a not insignificant change in process. What i remember from discussions with SDL and with my own testing, is that when on the projects page or tasks page, it there is currently no correlation to what is being imported. What the import process does now is simply look at the sdlxliff inside the return kit and get the information from there. To have it be aware of what project you were in would have to be added, and how would the import button on the projects page function.

    I think the best you could hope for that is easy would be to make it known what project was being imported on the import screen.

    Additionally, you cannot import a return kit to a task that is not claimed by you so unless you export all tasks from WS yourself, this issue shouldn't occur all that often.

    Thoughts?