3 ms·
If I'm non-technical, the term "job" is throwing me a bit. I'm thinking job as in employment, which doesn't makes sense in the context. Maybe call it a "Harve
by ams6110 16y ago
If I'm non-technical, the term "job" is throwing me a bit. I'm thinking job as in employment, which doesn't makes sense in the context. Maybe call it a "Harvest". "Harvest a document in seconds" instead of "Start a new job in seconds." The "New Job" button could be labeled "New Harvest" etc.
- cemerick 16y agoYeah, I've struggled with the "job" terminology quite a bit, having used "run", "batch", and "task" in prior iterations. (Whoa, think I'm a backend dev or something? ;-) I'll mull over the "Harvest" idea. Seems like a good way to provide a verb for people to use to reference the site/process, e.g. "I'll just harvest these docs" :: "I googled and didn't find anything".