... | ... | @@ -219,7 +219,7 @@ who should be included in the citation as authors beforehand. Some helpful tips: |
|
|
- In general, follow the structure of the [DaRUS entry for release e.g. 3.7](https://darus.uni-stuttgart.de/dataset.xhtml?persistentId=doi:10.18419/darus-3405)
|
|
|
- text formatting in DaRUS is done via html syntax
|
|
|
|
|
|
* __Updating badges:__ Update the `archived` badge in the dumux repository. You can access and change the badges in the browser using gitLab: "Settings->General->Badges". The necessary information for the `archived` badge can be found when clicking on your release in the [softwareheritage dumux releases](https://archive.softwareheritage.org/browse/snapshot/50fb10d5d33803233d6475cf1fab33b088c8a143/releases/?origin_url=https://github.com/dumux/dumux). On the right side of the screen (at the time of writing this), you will find a button `Permalink` with SoftWare Heritage persistent IDentifiers (SWHIDs) as well as links to the images of the badges (Copy image link).
|
|
|
* __Updating badges:__ Update the `archived` badge in the dumux repository. You can access and change the badges in the browser using gitLab: "Settings->General->Badges". The necessary information for the `archived` badge can be found when clicking on your release in the [softwareheritage dumux releases](https://archive.softwareheritage.org/browse/snapshot/50fb10d5d33803233d6475cf1fab33b088c8a143/releases/?origin_url=https://github.com/dumux/dumux). On the right side of the screen (at the time of writing this), you will find a button `Permalink` with SoftWare Heritage persistent IDentifiers (SWHIDs) as well as links to the images of the badges (Copy image link). Also Update the DARUS badge once the FDM Team send you the badge to the dataset. Maybe ask if they don't send it rightaway.
|
|
|
|
|
|
* __New release entry__: Prepare are a new entry for your release in the dumux [releases page](https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/releases).
|
|
|
|
... | ... | |