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
Right now the portal is only displaying items from the application_draft table, but we need to surface data from the application table as well as assessments and other related things.
The API was returning that information previously, but it's been commented out.
We need a landing page for student applications that has details (non-editable), documents related to the application, letters related to the application, funding requests, etc. formatted similarly to the draft screens. An application dashboard of sorts.
Work in progress:
Context
Right now the portal is only displaying items from the
application_draft
table, but we need to surface data from theapplication
table as well as assessments and other related things.The API was returning that information previously, but it's been commented out.
We need a landing page for student applications that has details (non-editable), documents related to the application, letters related to the application, funding requests, etc. formatted similarly to the draft screens. An application dashboard of sorts.
@datajohnson will do the screen design and @klondikemarlen can do the wiring and API work.
Expected Endpoints and Data Formats
See https://guides.rubyonrails.org/routing.html#crud-verbs-and-actions for a stable example of route naming conventions.
TODO: it might also be worth making flat URL such as
TODO: application and draft-application formats should be identical, except for a "type"??? column.
example of list format
example of item format
Data Flow Modeling
How a Draft becomes an Application
NOTE: Students can't edit a submitted application.
The text was updated successfully, but these errors were encountered: