They are answered by the XTRF community and our experts
I think that an XTRF user conference is an idea whose time has come. We could get to meet your team, share tips and tricks, network between LSPs and translators, have master classes à la memoQfest, see use case presentations, etc.
What do you think?
Hello, Is it possible to apply a filter from the "all vendors" section and display all the vendors working in the same language combination, filtred by their price? thanks a lot Gae
You can see the rates when you are in the price profiles section, but you have to apply at least these four filters to be able to do so:
1. Job type
2. Source language
3. Target language
4. Calculation unit
Then you should be able to see them.
Virtual Column / Custom Columns... are they consistent between implementations? Can we create a repository?
I've been thinking about virtual columns and how many I need to create, and how many others seem to need it also. There seems to be a lot of redundant work going on in this situation. So a few questions about this...
1) Are virtual column consistent among implementations? I mean, if I give someone my virtual column code, will it work on their system?
2) If so, would XTRF consider creating a library of virtual columns that we could access and use?
3) And would other users be interested in sharing and creating a code repository of some sort, that we could use and share among each other?
I am curious about the report module. I'm finding it very limited and only useful in very specific ways. Most of the time my reporting on XTRF data is about me creating custom project/quote/opportunity/Invoice views, exporting them for a time period, and manipulating in Excel. I'm finding the report module not so robust.
I am wondering if I'm looking at the reporting module wrong and if I don't understand the capabilities? Or do other people have a similar experience?
And if you are having success using the report module, what are you using it for? What reports are you finding useful? Are they custom reports or built in?
We're trying to use XTRF to evaluate an on-time delivery metric. We can compare the project deadlines to the project close date. However, in many cases, the date a project is closed is different than when it was delivered. And if you go into an old project to change something, the project close date then updates.
I started looking at "Actual delivery date and time" and realized that I have no data in this field.
So two questions.
1) Do others have a metric of on-time delivery in XTRF? How do you do it?
2) What is the "Actual delivery date and time" supposed to track? Are we doing something wrong? Is this field not used in Smart Projects?
When you set up a new project and hit the START TRANSLATION button, the vendor receives the new job, you can send him/her the PO. But how do we know that the vendor has accepted the job or viewed it?
@info There's no confirmation uppon manual Vendor assignment by the PM. Here system assumes the PMs know their Vendors and the selected one is a proven reliable business partner of yours. If the PMs are uncertain of hat they've should always send an availability request/job offer prior to the Vendor assignment.
@Snacho I'm very eager to read your proposal of a functionality that would be useful in the scenario you're describing. Because for me, this is a difficult one. If the Vendor had an accident, is injured, there's a typhoon, whatever makes the access to a mailbox impossible, are we safe to assume that the Vendor is not able to access mail but is able to log in to the Vendor portal and click a button?
Laszlo is reluctant to additional e-mails so we need to keep that in mind and the solution shouldn't increase the e-mail traffic between Vendor and PM.
As I said this is a tough puzzle for me.
I'm wondering others' experiences with reviewing new vendors. We find that going through the vendor data is a tedious process and requires many clicks, opens, closes and requires about 10 minutes to review a single vendor, just because of the various tabs and data formats that need to be clicked. We ended up hiring someone to only review potential vendors, enter it into a seperate database, which then allows us to review their data, and make decisions on who to reject, and who to follow up with.
This process is much better now than before we were XTRF, but it's still very labor intensive, very time consuming, and we do much of the analysis outside of XTRF. It seems to me that some interface tweaking, and with a few more features built for reviewing potential applicants, it could be much better.
What are other experiences with reviewing and managing vendors in XTRF? Do others have similar experiences?
When we identify a bug in version 7.0, is it being fixed for all instances, or one instance at a time?
And if we are all finding a few bugs here and there, should we all post them in one place so we can all look out for them and help identify if a bug is localized to one instance, or for everyone? This isn't for purposes of complaining, rather, I am afraid that I am not going to find all issues, and would love a little hive mind to help us all make sure we're not sending out incorrect information. Thoughts?
Customer support service by UserEcho