As a user trying out the first DyCons demo, I want to see an interesting and fully-applied example of how authorization decisions in Katsu affect the results viewed by the researcher in the researcher-portal. In order to accomplish this, the researcher-portal will need to retrieve and display more data to the user.
The GUI does not need to look good in order for this ticket to be completed. It will be prettified in a later ticket.
Acceptance Criteria
[x] Replace the component containing 10 individuals' ID and Updated_At fields with components containing the following:
[x] A table containing 10 complete results from Katsu's /api/individuals
[x] A table containing 10 complete results from Katsu's /api/phenopackets
[x] The authentication and authorization flows currently in place in the researcher-portal are retained and applied to the new components. However the code implementing those flows may be refactored as needed.
As a user trying out the first DyCons demo, I want to see an interesting and fully-applied example of how authorization decisions in Katsu affect the results viewed by the researcher in the researcher-portal. In order to accomplish this, the researcher-portal will need to retrieve and display more data to the user.
The GUI does not need to look good in order for this ticket to be completed. It will be prettified in a later ticket.
Acceptance Criteria
[x] Replace the component containing 10 individuals'
IDandUpdated_Atfields with components containing the following:/api/individuals/api/phenopackets[x] The authentication and authorization flows currently in place in the researcher-portal are retained and applied to the new components. However the code implementing those flows may be refactored as needed.
Dependencies
researcher-portal #15 should be completed first.