Continue reviewing after accept

[rstorey]

Refs #749

[acdha]

redirect_to_next_reviewable_asset and redirect_to_next_transcribable_asset are very similar. It seems like we could have those functions be almost entirely reusable except for the initial asset queryset filter.

[acdha]

The assettranscriptionreservation shouldn't be relevant for review since that's only used when editing.

[acdha]

This is causing the test to fail because it no longer prioritizes staying in the same project ahead of staying in the same campaign.

[rstorey]

My effort to de-dupe the code was fruitless. It caused the never_cache decorator to fail for a reason that I'm not quite sure of. In any case, although the two methods are very similar, they aren't exactly the same and there seems to be some kind of reason why never_cache wants the redirect call to be in the main view method. It was worth a try.

[coveralls]

Coverage decreased (-0.4%) to 69.158% when pulling 0a9a900 on review-after-accept into d8a0989 on master.

[acdha]

never_cache shouldn't be preventing that – it just adds a couple of headers on the returned Response object so it should be fine as long as we consistently do so.

[rstorey]

But the returned Response object isn't available in the secondary method for some reason. It seems like it should be, but it isn't. I spent almost an hour trying to figure out why it wasn't there, fooling around with different method signatures to try to get it to work. The effort didn't seem worth it.