You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even though, from a querying perspective, it would be easier to have the instituteAddress directly in the Institution table, it's not a good SQL practice to have locations/addresses stored in two distinct places (since locations include institutional addresses). What I think we are missing and should add is a column "streetAddress" in table Location. This way, with the locationId in table Institution, you can get all the information you need from table Location, and we have all locations stored in one place.
Solution: Add column streetAddress to table Location; define a unique key/index out of (name, street address, latitude, longitude) for that table, to ensure good behavior.
Institution address is not explicitly placed in the database.
But can be differed to Location -> LocationAdditionalInfo: "propertyName":Address
Suggestion: Column address varchar(254) DEFAULT NULL in table Institution
Reference:
https://github.com/plantbreeding/API/tree/master/Specification/Studies#get-studies-by-studydbid--get-brapiv1studiesstudydbid
The text was updated successfully, but these errors were encountered: