it would be very nice if we got a notice that our batches were expiring. I download several batches which I intend to index, but sometimes life gets in the way and the date passes and my batches are gone.
Often I could make the time to index a record that would be gone tomorrow if I knew I would lose the opportunity
I strongly support Judith’s idea, and in connection with it, I suggest that the expiry date/time be presented in the Indexer’s local time. Also, although lower priority for me than simply providing the notice, upon receipt of the expiry notice, I would suggest inclusion of a one-time (1-day ?) extension option. And perhaps an option to return the batch immediately, if the Indexer knows he or she won’t be able to get to it in time.
These modifications.might improve overall efficiency and flow. And from the number of complaints that I’ve seen over the years about “surprise” expiration of batches, make for happier and less frustrated Indexers.1
I strongly support john's recommendation. Note that "surprise" occurs once and is disappointing and frustrating, even for experienced indexers. On-going, give us more control over expiration- at least the option to "renew" or extended the date. Experienced indexers- and the "system" knows who we are- could be respected or at least given the benefit of the doubt.😁1
I support the elimination of surprises due to time zone differences, and suggest the solution include the information provided for indexing goals. The new month starts way early for us in the west.1