Versions Compared

Key

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

...

DescriptionJIRAImplementedLast WorkingTestedStatus

SRP Reviewer

  • See list of proposals (after conflict certification)
  • Review Type is displayed
    • Default is None; otherwise P,S,T
  • Review State is displayed
    • default is Blank; otherwise Saved, Completed, Finalized, Closed
  • Conflict State is displayed
    • Conflict/Available
  • If not Conflicted, have an ISR in which to enter comments and a score and see the proposal
    • can Save (Review State → Saved) per ISR
      • validate if score not equal to 0; otherwise it cannot save
      • does not validate comments
    • can Complete (Review State → Completed) per ISR
    • can Finalize (bulk action) if any ISRs with Review not equal to None are not Closed or Finalized
  • If Conflicted, only see title, abstract, proposal ID and cannot enter any information
  • All comments and scores are saved (though not propagated to consensus; see later)
  • Normalized Individual Scores are calculated on Finalize
  • Cannot provide comments or scores for ISRs with a Review State of Closed
  • Edge cases:
    • If an external proposal is added after reviewer has finalized, they should be able to review and finalize that one proposal (finalize is still bulk in theory)
    • If consensus has started for their panel, the Finalized Normalized Individual Score in that panel may be inconsistent with their new Normalized Individual Score (since it has the extra proposal). This is acceptable.
  • Instructions present
  • Finalize Reviews button always there but not active


Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-877

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-878

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-873

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-879


Sprint 46, 47

Sprint 61

V0.2

Sprint 61

V0.2

Status
subtleTrue
colourBlue
colorgreen
titleWorking

  • See list of proposals (after conflict certification)
  • Review Type is displayed
    • Default is None; otherwise P,S,T
  • Review State is displayed
    • default is Blank; otherwise Saved, Completed, Finalized, Closed
  • Conflict State is displayed
    • Conflict/Available
  • If not Conflicted, have an ISR in which to enter comments and a score and see the proposal
    • can Save (Review State → Saved) per ISR
      • validate if score not equal to 0; otherwise it cannot save
      • does not validate comments
    • can Complete (Review State → Completed) per ISR
    • can Finalize (bulk action) if any ISRs with Review not equal to None are not Closed or Finalized
  • If Conflicted, only see title, abstract, proposal ID and cannot enter any information
  • All comments and scores are saved (though not propagated to consensus; see later)
  • Normalized Individual Scores are calculated on Finalize

 

  • If an external proposal is added after reviewer has finalized, they should be able to review and finalize that one proposal (finalize is still bulk in theory)
  • If consensus has started for their panel, the Finalized Normalized Individual Score in that panel may be inconsistent with their new Normalized Individual Score (since it has the extra proposal). This is acceptable.
  • Cannot provide comments or scores for ISRs with a Review State of Closed
  • Instructions present
  • Finalize Reviews button always there but not active

Status
subtleTrue
colourRed
colorgreen
titleto fix

External Reviewer

  • External Reviewer is someone who is on any one panel associated with the Solicitation in question
  • An external reviewer can be assigned an external ISR for any proposal as long as the Panel associated with that proposal has not started Consensus
  • An external reviewer can be assigned an ISR even if their host panel is in Consensus.
  • External Reviewers do not have to declare conflicts on external ISRs. When assigned, the conflict state is automatically set to Available
  • External Reviewers can see the external ISR in their list of ISRs.
  • ER can provide comments, scores, save, complete, and finalize their external ISRs
  • ER do not have access to the Consensus UI or any responsibility at Consensus for the panel associated with the external ISR.
  • ER scores and comment are available in Consensus and corretly correctly integrated

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1395

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1328

Sprint 59

Sprint 61

V0.2

Sprint 61

V0.2

Status
subtleTrue
colourBlue
colorgreen
titleWorking

  • External Reviewer is someone who is on any one panel associated with the Solicitation in question
  • An external reviewer can be assigned an external ISR for any proposal as long as the Panel associated with that proposal has not started Consensus
  • External Reviewers do not have to declare conflicts on external ISRs. When assigned, the conflict state is automatically set to Available
  • ER do not have access to the Consensus UI or any responsibility at Consensus for the panel associated with the external ISR.
  • ER scores and comment are available in Consensus and corretly integrated

 

  • External Reviewers can see the external ISR in their list of ISRs.
  • ER can provide comments, scores, save, complete, and finalize their external ISRs
  • An external reviewer can be assigned an ISR even if their host panel is in Consensus.

Status
subtleTrue
colourRed
colorgreen
titleto fix

Import/Export ISRs

  • a CSV file is expected but it can use as a delimiter any of the following:
    • , ; | tab
  • putting double quotes around the comment will keep the commas within the comment safe
  • if reviews exist when asked to export, it will export the reviews
  • cannot upload a file with any blank fields (fails and warning issued)
  • if a user changes the name of the reviewer within the file, it gives an error
  • protects against Bobby Drop Tables
  • on a successful upload, the Review State of the ISR will changed to Saved
  • reuploading will update the comments/score
  • Don't need every ISR in file to work



Sprint 57?

Sprint 61

V0.2

Sprint 61

V0.2

Status
subtleTrue
colourBlue
colorgreen
titleworking

TTA Member

  • can change Review State to Closed
    • Auto changes Review Type to None
  • If a TTA member Finalizes a SRP member's ISRs (for the reviewer), it will finalize the ISRs that have a valid comment and score (Review State of Saved, Completed) and Review Type not equal to None. If a comment+score is not valid, regardless of the Review Type, it will Close the ISR (unsure if it still ignores review types of None)
  • can change Review Type until Consensus is initated for the SRP member's panel.
  • can change Review State until Consensus is initiated for the SRP member's panel.

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1039


Sprint 61

V0.2

Sprint 61

V0.2

Status
subtleTrue
colourBlue
colorgreen
titleworking

  • When TTA member uses Finalize, as a bulk action for all ISRs for that reviewer
    • Review Types of Primary, Secondary, Tertiary but have Review State of Blank are set to Close
    • Review Type of None is ignored, regardless of Review State
    • Review Types of P,S,T that have Review States in (Saved, Completed) are transitioned to Finalized
  • an change Review State to Closed
    • Auto changes Review Type to None
  • If a TTA member Finalizes a SRP member's ISRs (for the reviewer), it will finalize the ISRs that have a valid comment and score (Review State of Saved, Completed) and Review Type not equal to None. If a comment+score is not valid, regardless of the Review Type, it will Close the ISR (unsure if it still ignores review types of None)
    • When TTA member uses Finalize, as a bulk action for all ISRs for that reviewer
      • Review Types of Primary, Secondary, Tertiary but have Review State of Blank are set to Close
      • Review Type of None is ignored, regardless of Review State
      • Review Types of P,S,T that have Review States in (Saved, Completed) are transitioned to Finalized
  • can change Review Type until Consensus is initated for the SRP member's panel.
  • can change Review State until Consensus is initiated for the SRP member's panel.

Status
subtleTrue
colourYellow
colorgreen
titlenot implemented

  • A separate Close functionality will be per ISR

Status
subtleTrue
colourRed
colorgreen
titleto fix

Adding external reviewers as TTA member

  • If an external reviewer is added, the Conflict state is automatically Available.
  • TTA member can change Review Type until Consensus starts

Sprint 59

Sprint 61

V0.2

Sprint 61

V0.2


...

DescriptionJIRASlice 1Slice 2

Solicitation

  • Specify name of Solicitation
  • Specify Capabilities in Solicitation
  • Set Execution and Call period

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1437

 

 

 

  • Uses existing Solicitation and Proposal generator
  • Give Solicitation Name, Proposal Process, Number of Proposals

Status
subtleTrue
colourGreen
colorgreen
titlein progress

  • Set as Demo/Test

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1470

 


 

  • Separate Solicitation and Proposal Generation
  • Upload JSON for Solicitation Configuration

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1453

Proposal Generation

  • specify number of proposalsspecify number of science categories
  • use capabilities defined in Solicitation to generate demo/test proposalsFully supported proposals
  • Realistic Demo or Test proposals
  • can generate 100 proposals at a time and randomly distributes them across science categories

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1437

 

 

 

 

  • Uses existing generator paired with Solicitations
  • Proposals are belong to 1 category
  • Simple proposals - no real allocation requests

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1453

  • Separate Solicitation and Proposal Generation
  • More realistic proposals
  • Science Categories from Solicitation
  • Expanded user database

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1184
Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1466

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1546

Close Solicitation

Use existing structure


Panel Configuration

  • Create SC based on SCs of proposals
    • Set Name, Science Category
  • Associate users with SRP
  • Specify a chair
  • Associate proposals with SCs

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1436

 


 

  • Create 1 panel
  • Assign SC
  • Fill 6 non TTA members
  • Assign Chair
  • Assign Proposals

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1313

  • Create 1 to 6 panels
  • Assign each a unique Science Category

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1545

Vetting

  • Vet all proposals automatically

Jira
showSummaryfalse
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1436

 


  • Vet all proposals without modification

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1312


Finalize Panel Configuration


  • use existing framework; hookup FE

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1471


Conflicts

  • Fill out Conflict Declarations
  • Certify
  • Per panel, per SRP? Bulk options

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-901

 


  • Per panel button
  • set all to Available unless AutoConflicted
  • Certify Conflicts

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1472


ISRs

  • Assign Review Types satisfying minimum SRsPerProposal and 1 Primary and 1 Secondary per proposal
  • If assigned P,S,T, fill out comments and score randomly
  • If test solicitation, the comments should state the Proposal ID, the individual score, the reviewer name, and Review Type of reviewer
  • If Demo solicitation, the comments should be simulated comments.
  • Per panel, per reviewer, bulk options?

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-901

 


  • Per panel button
  • Use pattern for comments for all ISRs
    • Review Type not None
    • Review State not Blank
  • Randomize score
  • Assign Review Types randomly
    • 1 primary
    • 1 secondard
    • 1 tertiary

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1473



Finalize ISRs

per panel, per reviewer, bulk options?


  • per panel button to finalize ISRs

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1474


Initiate Consensus Phase


  • hook up existing structure per panel

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1475


Consensus

  • Fill out Comments for each
  • Complete PPR

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-901

 

 

 

  • Use appended ISR comments to make PPR Proposal Process comments for PI
  • Complete Reviews per panel

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1476

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1477

  • Pattern internal comments

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1551

Finalize PPR


  • per panel

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1478


Simulate All

  • Simulate full PPR Review Process

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1547


...