Meeting notes - January 30th, 2024 #25
unece-stat
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
BUILD PHASE (continued)
The group continued to discuss the following feedback contained in the Build phase issues.
Geospatial
• Giorgia said that the principle of “build by exception” is applicable to any type of data, and not just geospatial data
• InKyung said that while sub-process names had been changed to resuse and build (to emphasise reuse) maybe the phase name should be similarly renamed (reuse or build) to emphasise reuse over building new systems. – Was a decision made on this?
Workflow framework – 3.2
• It was decided to replace the phrase “workflow frameworks” with “workflow management tools“
Security – 3.5, 2.6
• There was discussion about adding some text to the introduction or to subprocesses 3.5 (testing) or 3.7 (finalise)
• Joni security is part of every stage of the build phase, for example if you work in a cloud-first environment it’s vital that each step taken is secure as it could be a breaking point. Systems involving staging environments might be a little different.
• Florian said that security considerations are something that are considered from the beginning of the design, and throughout the build phases. Testing should occur both at the component level and when they are assembled together. He suggesting including something in GAMSO.
• On this basis, some additional text was added to the instruction of the Build phase, though it was decided not to add any extra text in relation to data confidentiality requirements, as they are already dealt with under Data Management.
Training – 3.7
• A clarification was added that it was training for users of the (built or reused) system.
Renaming “Update output systems” (follow on from previous call in relation to boundary between Build and Disseminate)
• Chris proposed renaming the subprocess to “Refresh output systems” to avoid having the words “update” and “system” in the same sentence, which might cause comparison with the build phase, despite the fact that it is the data that is being updated, rather than the system itself.
• Juan suggested the problem is more the phrase “output systems” as opposed to “dissemination outputs”.
• Nadia suggested “updating dissemination systems”.
• Gabriel suggested that the word “system” is misleading.
• InKyung suggested “updating dissemination database” though Juan said it might be more expansive than a database (e.g. if maps are included)
• Chris suggested “populate dissemination system” but Joni thought “populate” was too specific.
• “Prepare dissemination data” sounds like part of the Process phase.
• It’s the contents of the system that is being updated, but this could include maps, for example.
• Chris suggested “prepare dissemination systems”. “Inform” or “setup” were also considered.
• The outcome of this discussion seemed to be not to change the wording.
Beta Was this translation helpful? Give feedback.
All reactions