Currently, if a user has access to a study, but it is not found in the EDA database, the /studies endpoint throws a 500. This can happen when a new study is being reloaded in dev or QA environments.
After discussion, we decided it may be preferable to use the EDA database as the authority and ignore extraneous studies from dataset access service to avoid disruption in dev environments. This is still pending discussion to ensure the whole backend team is on board with this approach.
Currently, if a user has access to a study, but it is not found in the EDA database, the
/studiesendpoint throws a 500. This can happen when a new study is being reloaded in dev or QA environments.After discussion, we decided it may be preferable to use the EDA database as the authority and ignore extraneous studies from dataset access service to avoid disruption in dev environments. This is still pending discussion to ensure the whole backend team is on board with this approach.