Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Excerpt

Lorne Becker and Deirdre Beecher are at present responsible for any vocabulary requests (adding, merging or editing terms in our Cochrane vocabulary). When you have submitted any request, via the form which is available via your Group space in Confluence, they are automatically logged in JIRA and Lorne and Deirdre will take it from there.

Table of Contents

Workflow process

  1. Requests are logged on JIRA via request form available on each CRG space in Confluence
  2. Lorne will take an initial look at the requests to determine
    1. if they need a clinical input 
    2. if further consultation with requester is required
    3. if request is straightforward
  3. Lorne will deal with a and b, and when resolved Deirdre will take the necessary action to udpate the vocabulary and JIRA ticket
  4. Easily resolved issues will be dealt with by Deirdre and if further issues are discovered, requests to be returned to Lorne
  5. the Report a Vocabulary Issue form (see brief video)
  6. Anna Last will deal with the requests, consulting with the requestor as required, updating the vocabulary and JIRA ticket 
  7. When resolved the Resolved Vocabulary When resolved the Resolved Vocabulary Issues table (available in each Group space) will log the change in status to DONE (NB If you wish to see what has changed recently, this table can be sorted by clicking on the Updated table heading)

Workflow diagram

Image Removed

HTML
  1. to DONE 


Request Status

View  the status

Click on the following hyperlinks for video demos.

Notification of the status

As soon as any change is made to the status of a request you should receive an email alert (see brief video).

<a href="#com-atlassian-confluence">Back to Top</a>




Status description


Status of JIRA TicketsDescription
Time Frame
BacklogAs soon as a ticket is logged it is given this status
ConsultationDiscussion is required with the requester (or other potentially interested groups) before further action can be taken
No ActionFurther discussion or consultation with requester determines that there are other terms that could be used and therefore not necessary to proceed with request.
Solution identifiedAfter discussion it is apparent the action required is part of a larger issue or change and requires
a global edit to the vocabulary
some further work by our Software Developers before the change can be made. The issue has been added to the development "wish list" but is not currently being actively worked on.
within months
Ready for Development
the
The action required is part of a larger issue
Any global or technical changes to the tools are ready for
that the Software Developers are actively working on or testing.
within weeks
Ready for EditorThe term is ready to be added (or any other modifications to be made) to the vocabulary
within days
DoneThe action has been completed i.e. term has been added, merged etc., in the vocabulary
within days


HTML
<a href="#com-atlassian-confluence">Back to Top</a>


HTML
<script type="text/javascript">
AJS.toInit(function(){
AJS.$('#comments-section').hide();
});
 for (var i=0; i<nr_li; i++) {
    // if the element has the class fom 'clasa' parameter
    if(tags_li[i].getAttribute('class') == 'innerCell'){
         tags_li[i].style.overflow = 'visible';
            //tags_li[i].style.overflow-y= 'visible';
    }   
  }
</script>