Changing expiration dates?

Discussion in 'General' started by parro, Jun 27, 2016.

  1. parro

    parro User

    Joined:
    May 28, 2016
    Messages:
    4,737
    Likes Received:
    431
    This morning I PANDA-ed a bunch of HITS, none of which would expire before 7/1, and moved them to my queue to do tonight. I'm not a newbie, but this is the first time I've tried to hoard them over a long period.

    When I peeked at them, the expiration dates on all of them had changed to within the next 3 hours. Is MT doing that to us to discourage PANDA-ing?
     
  2. Khalinov

    Khalinov User

    Joined:
    Dec 12, 2011
    Messages:
    873
    Likes Received:
    0
    I doubt that AMT did it, as there are much easier ways to thwart HIT hoarding (such as lowering the queue size to 10, 5, 2 or even 1 at a time).

    I’d bet the requester did it somehow, but I don’t know the mechanics of how that is done.
     
  3. Marcus

    Marcus User

    Joined:
    Jan 21, 2013
    Messages:
    466
    Likes Received:
    0
    You are probably confusing some of the different details for HITs.

    For example, this is from Copytext.

    HIT Expiration Date: Jul 5, 2016 (6 days 23 hours)
    Time Allotted: 10 minutes

    The HIT expiration date is for the requester end. That indicates when the HIT will be removed from the platform.

    The time allotted is the actual time workers have to complete a specific HIT.
     
  4. parro

    parro User

    Joined:
    May 28, 2016
    Messages:
    4,737
    Likes Received:
    431
    No, I'm not confusing "time allotted," which I generally ignore. When I queued the HITS with PANDA, the expiration time changed. When I tested one by putting it back into "Available," that new expiration time stuck. To test them, I watched the rest disappear from my queue in the course of the next 3 hours.

    Surely other people have seen this, but it might just be certain requesters. That's not a wise way to guarantee workers will finish your HITS.

    (and you can see I'm a red PANDA firefox)
     
  5. Marcus

    Marcus User

    Joined:
    Jan 21, 2013
    Messages:
    466
    Likes Received:
    0
    time allotted = expiration timer

    expiration timers dont change. I have seen HITs expire as soon as they are accepted if your computer clock isnt synced, but nothing like you state here.
     
  6. parro

    parro User

    Joined:
    May 28, 2016
    Messages:
    4,737
    Likes Received:
    431
    My puter time is perfect. If time allotted = expiration timer, what's this:

    "HIT Expiration Date: Jun 29, 2017 (51 weeks 6 days)"
    or
    "HIT Expiration Date: Sep 4, 2041 (1313 weeks 6 days)"

    Aren't those the dates that the HIT will be removed from the list because they have enough applicants?
     
    #6 parro, Jun 30, 2016
    Last edited by a moderator: Jun 30, 2016
  7. parro

    parro User

    Joined:
    May 28, 2016
    Messages:
    4,737
    Likes Received:
    431
    OK, it never occurred to me that MT would have a Help file. Mea culpa:

    "How much time do I have to work on a HIT?

    Requesters can specify a HIT's "Allotted Time" or how long a Worker can hold on to a HIT. Once the Worker accepts the HIT, a timer begins counting up to the HIT's allotted time. This timer is visible to the Worker on the Worker web site. When the timer reaches the HIT's allotted time, the HIT is made available for other Workers to accept and work on. This ensures that work is completed in a reasonable time period."

    For posterity and any newbie who might view this: It's the allotted time that counts down, and the HIT doesn't expire, it just goes back to "Available." The expiration date is when it's pulled completely from MT.

    So it sounds like I can't PANDA in the morning for the evening.
     

Share This Page