Add 2 review categories and provide ability to search on review categories

NRAO Interactive Services Modification Request 1C108, November 2007

1. Introduction

Why do we need this?

2. Background

  • Where (what screen) do you think would be the best place to add the 1-2 review categories?
    • The main screen on the proposal list, a separate column that we could either write into or use a drop menu.
  • Are there a list of review categories that we would choose from?
    • Yes, we do have a list. One problem would be that we have two categories have sub-categories so either the main drop down list would be really long or we could have a sub-menu for these two categories.
  • Would you want to add new review categories, and if so, how frequently?
    • Yes, but not very frequently, once a year maybe
  • I also presume that to search on review category, you would want a new search field in the “Options” box at the left – is that OK?
    • Yes, that would work
  • Would you want to search on multiple review categories at one time?
    • I don't see a reason right now why i would need to do that
  • Few comments -
    • Not everyone should be able to pick these categories and not everyone should even see these categories on their proposal, certainly should not be able to edit/change them
    • Administering "roles" again I think is the best way to do this. i.e., Carl, myself, Joan,Barry and Mark Claussen should be able to view/edit this field, the Proposal Selection Committee should be able to view the code (Dickman, Chandler, Frail, and five outside members). The proposer and no one else should be able to view the codes.
    • For down the road, we would like for a referee to be able to login and view the proposals for his/her category (Instead of me mailing them).
    • These are all functions that will help me and "lead" us into the future but one thing to keep in mind is that Carl/GBT handles his proposals differently??? so what works for me may not work for him

3. Requirements

  • 1
  • 2
  • 3

4. Design

Technical lead should provide a brief description of how this will be implemented in the code.

5. Deployment Checklist

Documentation? Systems/hardware/networking things needed for deployment?

6. Test Plan

6.1 Internal Testing

6.2 Sponsor Testing

6.3 Integration/Regression Tests


APPROVED: I acknowledge that my request is fully contained in this MR, and if the Open Sky (or other NIS or PST developers) deliver exactly what I specified, I will be happy.

ACCEPTED: I acknowledge that I have validated the completed code according to the acceptance tests, and I am happy with the results.

Written - - - - -
Checked - - - - -
Approved by Scientific Sponsor - - - - -
Accepted/Delivered by Sponsor - - - - -

  • Use %X% if MR is not complete (will display ALERT!)
  • Use %Y% if MR iscomplete (will display DONE)

Discussion Area

-- DanaBalser - 02 Nov 2007

This topic: Software > IntxSvcsPlanOfRecordC12008 > IntxSvcsMR2C108
Topic revision: 2007-12-11, OpenSky
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding NRAO Public Wiki? Send feedback