Waste Carrier Registration - Service Assessment
...convincing explanation as to why this can’t be done for specific subsets of the source code). Code from the service has been published and is currently being reused by another...
...convincing explanation as to why this can’t be done for specific subsets of the source code). Code from the service has been published and is currently being reused by another...
...code, code that contains sensitive information (e.g. fraud detection components) or can pose a security risk if open. Publishing the source code will be a mandatory requirement when the service...
...and constantly improving the service. A strong commitment to open sourcing the code (with all code being placed on Github), as well as to open data with each page being...
...look for specific accessibility content issues. We wrote it in Python, as it’s a GDS-supported programming language, and structured the code in a way that allowed us to write and...
...was standardised (e.g. 'Epsom & Ewell' was always named 'Epsom and Ewell'), an 'ONS name' table was imported into the database too. This table contained local authority names, ONS codes...
...set up and populate statistical reports. The potential time savings for analysts are enormous, freeing them up to focus on the interpretation of the results. The other huge benefit comes...
...code open and reusable, and the team told us that DVLA as a whole is now proposing to adopt this process. The process will include additional controls, reflecting the organisation’s...
...also not passed point 8 – although there are plans to share code within DVLA, and the team expressed a willingness to make its source code open and reusable, there...
...code open and reusable The team have a plan to open source the subsets of the code they are able to. We encourage them to do this sooner rather than...
...place to make all new source code (or specific subsets of the source code) open and reusable. The panel expect evidence of this to be demonstrated at the beta assessment....