Open camallen opened 9 years ago
So @rogerhutchings: @shaunanoordin made a handy little test for Shakespeare's World today and picked up on an 'out of data' error from Panoptes which turned out to related to subject sets that are turned off. So, we had the betatest subject set which was being read as an empty set even though it wasn't ticked on. It seems the thing to do is to delete the beta subject set if there is one (I didn't see one) or turn on all of the subject sets that are currently turned off and just rely on Greg's algorithm and the black dots to retire. Maybe we can adapt Shaun's test for AnnoTate?
@rogerhutchings, how did an in-active subject set get a request for subjects on it?
Because there’s no way of knowing whether a set is retired or not, unless we can mark it as inactive in the set metadata. So it’s still in the list of sets. Greg was working on something to do that.
On Thu, Dec 10, 2015 at 5:17 PM, Campbell Allen notifications@github.com wrote:
@rogerhutchings, how did an in-active subject set get a request for subjects on it?
Reply to this email directly or view it on GitHub: https://github.com/zooniverse/AnnoTate/issues/178#issuecomment-163691788
picked up on an 'out of data' error from Panoptes which turned out to related to subject sets that are turned of
and
So, we had the betatest subject set which was being read as an empty set even though it wasn't ticked on
so "turned off" means it was still an active subject set on the workflow? Even though it wasn't ticked as on?
As per conversation with @camallen this should be fixed by removing the page
parameter in the request subject url https://panoptes.zooniverse.org/api/subjects?page=1&sort=queued&workflow_id=121&subject_set_id=1032&order=asc
. Parameter order
is meaningless, so it also needs removing.
https://github.com/zooniverse/AnnoTate/blob/master/app/modules/transcribe/subjects.factory.js#L95
Loaded a subject for 1 page subject set. Immediately reloaded the page but didn't submit a classification and got this error: