Skip to main content

v1.1.7

· 2 min read
John Renfrew
John Renfrew
Programmer and data architect

Version 1.1.7 internal test release​

  • Writing playbooks
  • New server

Many of the core technology tests or pipeline requirements are now encapsulated into playbook markdown files. These serve the dual purpose of documenting test assumptions and results, and keeping a record of open or unanswered questions. They will also provide a valuable resource for the eventual documentation of the structure behind production build code.

The most important of these under devlopment, is the DigiFolio_Student, which decribes the interactions with the app from the position of the various defined roles. It also covers the core principles behind how the Student Taksks relate to Placements and Modules. These playbooks enable assumptions to be questioned in advance of writing code, as it is 'cheap' to make amendments at this planning stage, and much more difficult later.

Now that Oracle have stopped being difficult to deal with, there is a dedicated FileMaker server for this project. It is reached at folio.moorlands.ac.uk. This means we can start to scope out the architecture of file relationships, especially communication between Folio FileMaker files and Sopley Central. Testing and build can now proceed with final urls and account settings even during test phases. There is a need for a register of 'users' to feed the Clerk auth, and replicated data on placements.