HIFIS Technical Documentation issueshttps://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/issues2022-01-14T07:10:41+01:00https://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/issues/40Getting started section for Mattermost2022-01-14T07:10:41+01:00Norman ZiegnerGetting started section for MattermostMaybe it would be a good idea to provide a "Getting Started" section for Mattermost [analogous to Codebase](https://hifis.net/doc/software/gitlab/getting-started/).
/cc @frust45 @hueser93Maybe it would be a good idea to provide a "Getting Started" section for Mattermost [analogous to Codebase](https://hifis.net/doc/software/gitlab/getting-started/).
/cc @frust45 @hueser93Hueser, ChristianHueser, Christianhttps://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/issues/65codebase: Remove section about direct GitHub Sign-In2023-01-26T10:17:51+01:00Norman Ziegnercodebase: Remove section about direct GitHub Sign-InThe direct GitHub login was removed from the Codebase on September 1st, 2022. After a transition period, we can remove the corresponding section from docs.
Related to !315
Related to https://gitlab.hzdr.de/hifis-software-deployment/gi...The direct GitHub login was removed from the Codebase on September 1st, 2022. After a transition period, we can remove the corresponding section from docs.
Related to !315
Related to https://gitlab.hzdr.de/hifis-software-deployment/gitlab/-/issues/239
\cc @frust45 @hueser932023-01-06https://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/issues/26More levels of menu formatting2021-10-20T17:34:57+02:00Uwe Jandt (DESY, HIFIS)More levels of menu formattingLeftover from !113, [comment](https://gitlab.hzdr.de/hifis/hifis-technical-documentation/-/merge_requests/113#note_804809)
DG used three nested levels in the navigation pane for "guidelines" and "organisational" sections, but more than ...Leftover from !113, [comment](https://gitlab.hzdr.de/hifis/hifis-technical-documentation/-/merge_requests/113#note_804809)
DG used three nested levels in the navigation pane for "guidelines" and "organisational" sections, but more than 2 levels are not properly supported in this theme of RTD, so these sections are always expanded by default, while the current section you are reading is collapsed. So we might need to change things there.https://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/issues/101CI Runner: Add a hint which containers can be run on the Windows runner2024-02-28T09:50:32+01:00Hueser, ChristianCI Runner: Add a hint which containers can be run on the Windows runnerThomas @tfoerst1 would like to have a note on which containers are working on the Windows runner:
* Windows containers only up to the Windows version installed on the runnerThomas @tfoerst1 would like to have a note on which containers are working on the Windows runner:
* Windows containers only up to the Windows version installed on the runnerhttps://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/issues/100CI Runner: Mention that the windows runner `privileged` is set to `false`2024-02-26T14:40:13+01:00Foerster, ThomasCI Runner: Mention that the windows runner `privileged` is set to `false`Basically states that users can not build container images with the Windows runner.Basically states that users can not build container images with the Windows runner.https://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/issues/99Add Cloud KPI for 20232024-02-22T12:29:24+01:00Annette Spicker (HZB)Add Cloud KPI for 2023Publish Cloud operation KPI for 2023Publish Cloud operation KPI for 2023Annette Spicker (HZB)Annette Spicker (HZB)https://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/issues/98Cloud KPI: add explanation about T_fitstart, T_reference2024-02-14T13:50:07+01:00Annette Spicker (HZB)Cloud KPI: add explanation about T_fitstart, T_referenceFor all who do not understand the mathematical explanation, we need to add a text regarding
- [x] T_onboard
- [x] T_logstart
- [ ] T_fitstart
- [ ] T_fitstart, manually defined
- [ ] T_reference_overall
- Startwert ist fix und ändert s...For all who do not understand the mathematical explanation, we need to add a text regarding
- [x] T_onboard
- [x] T_logstart
- [ ] T_fitstart
- [ ] T_fitstart, manually defined
- [ ] T_reference_overall
- Startwert ist fix und ändert sich nicht
- der Startwert kann nicht unter dem 1. echten Meßwert liegen
- er kann aber höher liegenAnnette Spicker (HZB)Annette Spicker (HZB)2024-02-15https://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/issues/97CI: Add MTU hint to the documentation2024-01-17T11:39:48+01:00Huste, TobiasCI: Add MTU hint to the documentationSee https://support.hifis.net/#ticket/zoom/6175See https://support.hifis.net/#ticket/zoom/6175Huste, TobiasHuste, Tobiashttps://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/issues/96Add Mattermost Changelog Entry for Version 9.2 and 9.32024-01-04T07:31:25+01:00Hueser, ChristianAdd Mattermost Changelog Entry for Version 9.2 and 9.3Hueser, ChristianHueser, Christianhttps://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/issues/95Adapt Process Framework due to Regular Service Portfolio Review2024-01-18T10:24:59+01:00Laura Marie HolzAdapt Process Framework due to Regular Service Portfolio Reviewhttps://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/issues/94datahub.erde-und-umwelt.de nicht erreichbar2023-12-18T10:12:09+01:00Uwe Jandt (DESY, HIFIS)datahub.erde-und-umwelt.de nicht erreichbarMoin @marie.schaeffer , der Link https://datahub.erde-und-umwelt.de/en/ ist nicht mehr erreichbar, er wird auf einer Seite verlinkt, die ursprünglich von Dir kam, daher pinge ich Dich zuerst an.
https://codebase.helmholtz.cloud/hifis/ov...Moin @marie.schaeffer , der Link https://datahub.erde-und-umwelt.de/en/ ist nicht mehr erreichbar, er wird auf einer Seite verlinkt, die ursprünglich von Dir kam, daher pinge ich Dich zuerst an.
https://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/blob/master/docs/service-integration/roles/roles-datahub.md?plain=1#L3
Kannst Du da was machen?Marie SchaefferMarie Schaefferhttps://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/issues/93Add Mattermost Changelog Entry for Version 9.12023-12-11T16:25:23+01:00Hueser, ChristianAdd Mattermost Changelog Entry for Version 9.1Hueser, ChristianHueser, Christianhttps://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/issues/92Update GitLab Runner documentation with Windows runner information2023-11-21T11:11:41+01:00Hueser, ChristianUpdate GitLab Runner documentation with Windows runner informationHueser, ChristianHueser, Christianhttps://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/issues/91Add Mattermost Changelog Entry for Version 9.02023-11-15T10:08:40+01:00Hueser, ChristianAdd Mattermost Changelog Entry for Version 9.0Hueser, ChristianHueser, Christianhttps://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/issues/90Add Mattermost Changelog Entry for Version 8.0 and 8.12023-10-22T12:45:24+02:00Hueser, ChristianAdd Mattermost Changelog Entry for Version 8.0 and 8.1Hueser, ChristianHueser, Christianhttps://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/issues/89Limesurvey Doc page still necessary?2024-01-09T16:26:02+01:00Uwe Jandt (DESY, HIFIS)Limesurvey Doc page still necessary?@f.doering
Is the explicit Limesurvey Techdoc page still necessary or could it be simplified or even deleted?
- :point_right: <https://hifis.net/doc/cloud-services/LimeSurvey_DKFZ/docs/>
It is linked from the [portal page of Limesurv...@f.doering
Is the explicit Limesurvey Techdoc page still necessary or could it be simplified or even deleted?
- :point_right: <https://hifis.net/doc/cloud-services/LimeSurvey_DKFZ/docs/>
It is linked from the [portal page of Limesurvey](https://helmholtz.cloud/services/?serviceID=8b90d666-2d49-4506-8924-fc4700da6a1d), however it seems that several information are redundant.
The authoritative information should be in portal, so either we should leave only additional information here, or delete the page altogether...FlorianFlorianhttps://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/issues/86Add Mattermost Changelog Entry for Verson 7.102023-06-01T15:51:43+02:00Hueser, ChristianAdd Mattermost Changelog Entry for Verson 7.10Hueser, ChristianHueser, Christianhttps://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/issues/85Add GitLab and Mattermost Changelog Entries to Documentation2023-04-26T08:33:52+02:00Hueser, ChristianAdd GitLab and Mattermost Changelog Entries to DocumentationHueser, ChristianHueser, Christianhttps://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/issues/84Interpretation of the empty Attribute Query response by the Helmholtz AAI2023-04-21T15:32:00+02:00Uwe Jandt (DESY, HIFIS)Interpretation of the empty Attribute Query response by the Helmholtz AAIFrom https://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/merge_requests/382#note_4098225 :
@sa.apweiler, could you please do some specification in [line 141, under "Interpretation of the empty Attribute Query ...From https://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/merge_requests/382#note_4098225 :
@sa.apweiler, could you please do some specification in [line 141, under "Interpretation of the empty Attribute Query response by the Helmholtz AAI"](https://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/blob/master/docs/helmholtz-aai/Attribute_Query/SAML2_Attribute_Queries_basic.md?plain=1#L150)?
\cc @andreas.klotzSander ApweilerSander Apweilerhttps://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/issues/83Follow-up: Handling of the wording "Associated Services"2023-03-21T09:26:13+01:00Uwe Jandt (DESY, HIFIS)Follow-up: Handling of the wording "Associated Services"@SpickerHZB @laura.marie.holz The following [discussion from !377](https://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/merge_requests/377#note_4012970) should be addressed:
> Would it solve the problem, if we ...@SpickerHZB @laura.marie.holz The following [discussion from !377](https://codebase.helmholtz.cloud/hifis/overall/hifis-technical-documentation/-/merge_requests/377#note_4012970) should be addressed:
> Would it solve the problem, if we skip the [image](https://hifis.net/doc/process-framework/3_Service-Portfolio-Management/3.2_Service-Type-Definitions/3.2.0_Service-Type-Definitions/)?
>
> @laura.marie.holz Actually, I cannot see the benefit anymore of mentioning *Helmholtz AAI registered services* and *Associated Services*. In the beginning, when you wrote this chapter, it seemed to be important. But currently, we do not have the issue to explain that to our providers, right? And the fact, that a Helmholtz Cloud Service has to be connected to the Helmholtz AAI is mentioned in the Application Form (or canvas, not sure).
>
> WDYT?Laura Marie HolzLaura Marie Holz