The LCO facility confuses users by offering SOAR and BLANCO proposals in the proposal drop-down menu. (and the SOAR facility probably offers LCO proposals, but not verified).
The TOM Toolkit populates the proposal drop-down from the facility /api/profile/ endpoint, and extracts proposal names from the profile payload. Currently, this is what goes into the drop-down menu.
The OCSFacilty subclasses should filter down that list: They should use the proposal names returned in the profile payload to get the proposal details (i.e. hit the /api/proposals endpoint) and make sure the proposal matches the specific facility (LCO, SOAR, BLANCO) that the user has selected. Then, populate the drop-down menu with appropriate proposals.
The LCO facility confuses users by offering SOAR and BLANCO proposals in the
proposaldrop-down menu. (and the SOAR facility probably offers LCO proposals, but not verified).The TOM Toolkit populates the proposal drop-down from the facility /api/profile/ endpoint, and extracts proposal names from the profile payload. Currently, this is what goes into the drop-down menu.
The OCSFacilty subclasses should filter down that list: They should use the proposal names returned in the profile payload to get the proposal details (i.e. hit the /api/proposals endpoint) and make sure the proposal matches the specific facility (LCO, SOAR, BLANCO) that the user has selected. Then, populate the drop-down menu with appropriate proposals.