Under Community Review

Source file System field in SDLTMs

Hi,

Creating a new idea just for the Source file System field in Studio.

Please do consider having a Source file system field in SDLTMs which capture at least the file where that segment was first created. Filepath and name would be ideal but filename is already better. It's a very useful piece of information which is available in the TMX file but not visible in the SDLTM format.

There was a recommendation in a previous post to use the Record source plug-in for it but this is key functionality that is missing in Studio. Besides, the suggestion of a plug-in will not do much, as that is not something that can be deployed in TMS TMs.

Thank you once again for considering this enhancement.

Kind regards,

Miriam

Miriam Santos Freire
  • in reply to Adrian Boloveschi

    This would be very useful for our Linguistics Services team as it would allow us to record the project name and the source file name in every single TM segment without slowing down productivity.

  • Great article by Paul Filkin on this topic for whomever reads this idea request: https://multifarious.filkin.com/2016/01/14/recordsourcetu/

    However, the bottom line is still there: Storing the filename as a TM Field for GroupShare TMs is not practical with projects that have more files. And it does seem that "Of these it’s the last one “Source File” that I have seen people asking for since adopting Studio.". So I am wondering how can we push this idea more?

    Also another avenue for our users needing this idea would be to post on the App Forum and request for this app to support GroupShare TMs. That would be this place:

    https://community.sdl.com/product-groups/translationproductivity/f/openexchange_applications/6309/record-source-tu-plugin-question

  • I would like to bring a bit more attention to this. The functionality provided by Record Source should be made available in Studio out of the box. Record Source does not work with GroupShare TMs and having a easy way to store ProjectName and FileName as fields in the TM is important. Studio TM Fields can be used for the ProjectName, but for filename this is not really feasible there is a lot of manual work needed, while Record Source does this automatically.

  • I totally agree and raised a similar concern with the SDL Support team and this is the response I received.

    "One thing that you can do is to add Fields to your TMs. Then you can choose values for each of those Fields in each of the projects. So for example you could have the project name in there. The value you set will be recorded in the TM and you can later use it to find out where a certain segment came from.

    To add fields in a TM you need to go to the TM Settings from the Translation Memories view and then in the Project Settings under Translation Memories and Automated Translation you have the section "Update" - the fields you added will appear there."

    I have been doing this as a workaround, but it does take a little extra time and would be nice to just have as a built-in feature.

  • Also, the record source TU plugin slows down tasks like TM update excessively, meaning Tm updates can take up to 8 times longer with the plug in that without. So incorporating this function in Studio directly, and making sure it does not impact performance, would help massively