Registered Traveller - Service Assessment
...that in the next phase of development the team: make further progress towards publishing more of its code, particularly for elements that would be useful for other services like the...
...that in the next phase of development the team: make further progress towards publishing more of its code, particularly for elements that would be useful for other services like the...
...to this service 10. Alternate channel in place 15. Code is not open source but templates are shared 23. Not reported on the performance platform during beta 26. Not at...
...(part of the prison visits exemplar). The supplier have taken MOJ code and ported to angular.JS; hooked it up to their API; and made it time zone aware. The supplier...
...not have full control over the HTML output, it is unclear whether the code is accessible. It was not clear from the presentation that the form components and fragments align...
...commercial platform (WordPress), where there has been bespoke development, the source code will be made available on Github. The team also said that they will be blogging about the work...
...SRO sign-of will be secured prior to launch. Work is underway to identify sections of code for publication in open source repositories. Work is underway to integrate with the GOV.UK...
...the service should focus on throughout the beta phase and must be addressed before coming for a live assessment. Publishing source code must be in place for the live assessment....
...No non-digital steps were identified. 15. Whilst HEFCE have confirmed they are happy to release the code they do not believe there is value in doing so due to the...
...relying as they do on a supplier (based in New York), with closed code, and GDS researchers. Also, it was noted with approval that the service team aims to split...
...source code, using open standards and following GOV.UK design patterns and style guide. The panel confirmed that assisted digital support only needs to be applied to the digital element of...