10

I am a translator, I noticed that the Work dashboard has been renewed, providing now the informations in a more organized way. Nevertheless I must notify that a detail is missing: the date.
Customers have 120h for approving a job, and often they make use of the full time. Thus the translations stay in the "Reviewable jobs" folder for 5 days. Without the possibility of knowing the date when the job was made available (or the translator was assigned to), it becomes difficult to have an overview on the jobs. It is also lost the information (normally of personal interest of a translator) of how many jobs each day he was assigned to.
I think it would be helpful for a translator to have an additional column showing the date in the work dashboard, and I hope you can take in consideration of adding it. Maybe in the empty space between "Contents" and "Info"?

7 comments

  • 4
    Avatar
    Vox Nipponica

    Agreed -- it is good to gain new functionality, but not good to lose functionality. More data is always preferable to less. A messier but more informative design is always more useful than a cleaner but less informative one! This is consistent with proper standards of the design of interfaces and programs. Unfotunately, modern web design often fails to follow these canon rules in favor of minimalism.

  • 0
    Avatar
    Lara Fernandez

    Hi there,

    Thanks so much for this feedback!

    We're considering bringing the date back but we'd appreciate if you could let us know more about what you would find most useful. I know in the past we used to display the date when the job was ordered (not submitted) but would you prefer to see this, or the date when it was submitted? 
    Could you also elaborate on what you'd like to use the date as reference for? Is it to keep track of your work on certain dates? Or to calculate how long until it gets automatically approved?

    We'd like to hear more about your specific use of the date and preferences so that we can continue to improve the dashboard :)

    Thanks,

    Lara

  • 0
    Avatar
    Vox Nipponica

    It's actually more a question of data portability and accessibility. You cannot predict the specific use case of an end-user, which is why data should be provided in the most generic manner possible. Example:

    1. One user may want to know how many days until their work is approved
    2. One user may want to track down a certain job they did on X date
    3. One user may want to run an analysis of what their most active days of the week are
    4. One user may only infrequently perform jobs every few months or years, and want to parse which were their most active months/years
    5. One user may want to know what days of the week they don't perform work
    6. One user may need exact dates of every task performed and its dollar equivalent for tax filing purposes

    These are the main ones, but there are possibly dozens of corner cases. Everyone has different circumstances, which is why data should always be transformable and selectable from a range of filters.

    If I go to Amazon, I can see the exact dates of when I purchased something, when it shipped, when it reached me, when I returned it, and sort all of this by weekly, monthly, annual, or specific date ranges. This is useful when deducting business expenses, factoring when something returns/arrives, and other uses.

  • 0
    Avatar
    Cilhio

    Hi everybody,

    Thanks to Lara Fernandez for the support.

    I agree with Vox Nipponica that there could be many reasons to choose a date instead of another. Would be certainly very useful to have the possibility to filter between "job made available", "job assigned", "job submitted".
    Personally, I would use mostly the date of job assigned, or submitted. Sometimes a job is made available on a certain day, but it is rejected or expires and therefore it can be assigned to a new translator even some days after its publishing. For that reason I would not give the preference to the date of order as first choice.

    About the reasons on what I would use the date as reference for, Vox Nipponica was very clear in making a list many good points. I agree with all of them. With a date you can know when your job should be approved, track a single job according to the date, make an analysis of which are the most active/inactive days, and have a complete information for tax filing.

    Waiting to hear a following, many greetings

  • 0
    Avatar
    Alexander

    I think what people are really asking here is a way to filter and sort their work based on any metadata field (all relevant dates, units count, rewards, level, status, ...).

    While juan.garcia.heredero's gengoscraper is helpful, it would be much easier if Gengo would integrate an interface for such filtering and sorting in the Dashboard.

    If implementing such an interface is too much work, the second best thing would be if the Dashboard included a button to export all metadata of all archived jobs for further analysis in a spreadsheet. This cannot be hard at all.

  • 0
    Avatar
    Cilhio

    Dear Lara Fernandez,

    is there any news concerning the here mentioned topic?

    Thanks for the support, greetings

  • 0
    Avatar
    Lara Fernandez

    Hi @Cilhio - thanks for bringing this up again :)

    We're currently looking into it and in the process of making a decision on how to implement back the date in the dashboard. However, we are also caught up with a few other projects that have been prioritized, so I can't give you a date at the moment as to when changes will be implemented. Please rest assured that we're working on it and a fix is definitely in the pipeline!

Please sign in to leave a comment.