Přeskočit na hlavní obsah

v1.0.5

· 2 minuty čtení
John Renfrew
John Renfrew
Programmer and data architect

Version 1.0.5 public test release​

  • Code refactoring to cache metadata IDs server-side
  • Investigations into speed of invoices retrieval
  • Moved processing of data containing pre-composed JSON to server-side
  • Core novigation structure becoming defined

Cache of metatdata can improve performance whenever a page or route needs to use or display items we are storing - like an ID. It is stored in the Clerk API and so request use involves a query, which can be sped uop with the used of cached data. This data changes very rarely and so this pattern is used to hide the IDs away, while making them available for server-side routes which are using them as filters or keys in OData queries.

To allow for this to be build out from the Student Portal, the following routes enable that. /login => with a student email => dashboard, with a staff email => staff-dashboard. The student version has a link from there into the Digifolio parent.

If a user logs in with an email associated with a superId then they arrive at portfolio-super, with an email associated with a markerId then portfolio-marker, and if external, then portfolio-external. These are siloed from each other, and in the event that there is a staff portal, then there would be a button to enter the digifolio similar to students.

Students will see a picker for the placements they have active during the year, with action buttons for further sections to manage and enter time-based events, and another to enter task data.

Supervisors would see the students they are supervising in the current year, and on selection of the student the detail as above with additional fields for their commments on the student responses to the task questions.

Markers would see a longer version of the list, based on being assigned as marker for a set or module, and other controlsa vailable as above. Markers would be able to add adidtional comments after the supervisor. This may never happen if it is detirmined that all markers will be accessing the data from FileMaker.

External would see a pre-filtered list simialar to above of the random set assigned to them.