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
Publications were indeed listed under "additionalInfo" in call GetTrials, but since in the call GetTrialsByDbId there is now a dedicated section for them and they have multiple attributes, we should indeed revise our database structure.
Solution: Create a table Publication with the necessary fields plus the trialId (I think it is safe to assume that each publication can only refer to one trial, so we can link them in this manner).
Action: Create an Issue in the main BrAPI github to ask them to review the GetTrials call so that publications are listed in the same manner in both GetTrials and GetTrialByDbId. It does not make sense to have two different paradigms. In the meanwhile (and if they don't agree with this assessment) we will have to revise the GetTrials call to get the publications from the new Publication table, and list them under additionalInfo.
How do I store this information? The first though was study additionalInfo, but this might warrant a dedicated table for this information.
I don't have a method to extract a specific key value pair. From a table with dynamic attributes. But this can be implemented.
The text was updated successfully, but these errors were encountered: