Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add facility to proposal model #139

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

nmaytan
Copy link
Collaborator

@nmaytan nmaytan commented Jan 30, 2025

Currently, the /proposals endpoint does not actually respect the facility query parameter. This PR adds a facility field to the proposal data model and syncs this field when proposals are "cached" from PASS. Furthermore, the proposal fetching mechanism is updated to also query based on facility.

This is not tested.

@stuartcampbell
Copy link
Collaborator

stuartcampbell commented Feb 4, 2025

Can you please test this? Otherwise it might be a while before I have time to test this fully.

Adding a facility changes the data model and the assumed / implied data relationship that the facility name is associated with the proposal via the resource/beamline/instrument

I'm not sure how this would work with multi-facility proposals - which we don't have many, but they do exist in theory.

@nmaytan
Copy link
Collaborator Author

nmaytan commented Feb 6, 2025

@stuartcampbell Should we instead infer the facility using the instrument list - would that be a preferred approach? I was not aware of this implicit relationship. Trying to follow existing conventions, but figuring it out in realtime.

I believe there are still places where we need to address the multi-facility case besides this PR, however.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants