Menu

#540 Fix workflow - we need an "I accept this session" page

None
closed-fixed
None
8
2013-05-18
2013-05-02
No

From an email I just sent to Val:

The James Moseley session, was the one I assigned this morning
http://curation.pombase.org/pombe/view/object/pub/9522?model=track
and appears as "session_Accepted" but this seems a bit premature (an no
e-mail has been spawned to the helpdesk yet. I assume this will happen
when Jamie really does accept the session?)

Ah.

That's a very good point and I should have spotted that earlier. The
problem is that currently a session is marked as "SESSION_ACCEPTED" as
soon as the session has a curator. That works OK for the case where
they put a PMID in the search box and then they fill in their name and
email.

But it doesn't make sense if you are creating a session for a
publication and setting the curator. In that case if you send the
session link out the curator won't (currently) need to put in their
name and email - they go straight to the gene upload page. They have
bypassed the need to accept the paper. Whoops.

What needs to happen is that they should be initially sent to a page
that says something like a short version of the email they get when you
send a link to them. So something like:

We invite you to contribute annotations based on this paper to
PomBase. Any annotations you make will be prioritised for inclusion
in PomBase, and will therefore also be readily visible in other
databases such as GO, UniProtKB, BioGRID, etc.

If you wish, you can reassign this paper to a colleague.

(then two buttons:) [reassign] [accept]

Perhaps it needs a "reject" button for when the researcher doesn't want
to curate the paper and doesn't know who to reassign to?

Something has been niggling me about the current workflow and I think
this might be it.

This isn't hard to fix. We just need an extra page with the text above
and two or three buttons. Internally we just need an extra flag on the
session that says it's been accepted. I'll make a ticket.

Discussion

  • Kim Rutherford

    Kim Rutherford - 2013-05-16
    • status: open --> open-fixed
    • Group: -->
     
  • Kim Rutherford

    Kim Rutherford - 2013-05-16

    This is fixed now, except for adding a "reject" button. I'm closing the ticket. If you think a reject button is a good idea, please open a new ticket for it.

     
  • Kim Rutherford

    Kim Rutherford - 2013-05-18

    "open-fixed" is starting to annoy me.

    Changing to "closed-fixed".

     
  • Kim Rutherford

    Kim Rutherford - 2013-05-18
    • status: open-fixed --> closed-fixed
     

Log in to post a comment.