You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An increasing number of volunteers use FromThePage to gain "service hours" -- hours of volunteer effort for a charity which are required for awards, civic organizations, schools, and court-ordered community service. We calculate volunteer hours nightly by looking at the Ahoy logs, which track requests our webserver sees. Every night, a task looks at the requests for different pages/works/collections, for each user, and calculates the total time the user spent working.
The problem with this approach is that it can miss time spent by volunteers in typing. For most projects, that is not a big issue, since only a minute or two may elapse between when a user loads a page and when they press "Save" and we see the request. However, some transcribers work on pages that may take an hour or more to transcribe, during which time we do not see any requests and do not count their time. Worst of all, some transcribers navigate to a page which they want to work on tomorrow, leave that open in a tab, then on the next day start editing a page, so we only see their first request when they press "Save".
We'd like to add some functionality that calls a route like collection_id/work_id/page_id/active_editing when a user starts typing on a transcription input for the first time, and perhaps every 5 or so minutes after that. (Note that a still_editing action does exist, but this fires regardless of whether the user has made any changes, and is also ignored by the hour calculation).
The text was updated successfully, but these errors were encountered:
An increasing number of volunteers use FromThePage to gain "service hours" -- hours of volunteer effort for a charity which are required for awards, civic organizations, schools, and court-ordered community service. We calculate volunteer hours nightly by looking at the Ahoy logs, which track requests our webserver sees. Every night, a task looks at the requests for different pages/works/collections, for each user, and calculates the total time the user spent working.
The problem with this approach is that it can miss time spent by volunteers in typing. For most projects, that is not a big issue, since only a minute or two may elapse between when a user loads a page and when they press "Save" and we see the request. However, some transcribers work on pages that may take an hour or more to transcribe, during which time we do not see any requests and do not count their time. Worst of all, some transcribers navigate to a page which they want to work on tomorrow, leave that open in a tab, then on the next day start editing a page, so we only see their first request when they press "Save".
We'd like to add some functionality that calls a route like
collection_id/work_id/page_id/active_editing
when a user starts typing on a transcription input for the first time, and perhaps every 5 or so minutes after that. (Note that astill_editing
action does exist, but this fires regardless of whether the user has made any changes, and is also ignored by the hour calculation).The text was updated successfully, but these errors were encountered: