ossr-curation issueshttps://gitlab.in2p3.fr/escape2020/wp3/ossr-curation/-/issues2023-06-15T14:27:23+02:00https://gitlab.in2p3.fr/escape2020/wp3/ossr-curation/-/issues/17ONBOARDING: INDIGO IAM2023-06-15T14:27:23+02:00Jutta SchnabelONBOARDING: INDIGO IAM# Onboarding project
## Project overview
**Title:** INDIGO IAM
**Description (Abstract):**
**Project Owner / Organization:**
## Repositories
_Add here a subsection for each repository intended for onboarding.
Repeat for several re...# Onboarding project
## Project overview
**Title:** INDIGO IAM
**Description (Abstract):**
**Project Owner / Organization:**
## Repositories
_Add here a subsection for each repository intended for onboarding.
Repeat for several repositories._
### INDIGO IAM
| Information | header |
| ------ | ------ |
| Project name | Please give a descriptive name |
| Repository link | URL |
| Project Owner | Name/Organization |
- [ ] Applied for adding to ESCAPE group
- [ ] Added to ESCAPE group
## Checklist
_The following steps should be completed to finalize the onboarding, in addition to adding the project to Zenodo:_
- [X] Onboarding talk scheduled
- [x] Onboarding talk given
- [ ] Documentation providedhttps://gitlab.in2p3.fr/escape2020/wp3/ossr-curation/-/issues/16ONBOARDING: Wavelet Detection Filter2023-06-15T18:04:37+02:00Jutta SchnabelONBOARDING: Wavelet Detection Filter# Onboarding project
## Project overview
**Title:** Wavelet Detection Filter
**Description (Abstract):**
The Wavelet Detection Filter is an open source Python package devised to search for transient signals detected by gravitational...# Onboarding project
## Project overview
**Title:** Wavelet Detection Filter
**Description (Abstract):**
The Wavelet Detection Filter is an open source Python package devised to search for transient signals detected by gravitational waves detectors. These signals include gravitational waves from astrophysical sources but also instrumental artifacts found in detector data, called glitches. As a search pipeline, WDF utilizes Wavelet decomposition and de-noising of the signal.
**Project Owner / Organization:**
I report the current WDF gitlab organisation:
* Original Author and Gitlab Project Owner: Elena Cuoco
* Owner: Alberto Iess
* Maintainer: Francesco Di Renzo
* Maintainer: Filip Morawski
* Maintainer: Alessandro Staniscia
## Repositories
### INDIGO IAM
| Information | header |
| ------ | ------ |
| Project name | Please give a descriptive name |
| Repository link | URL |
| Project Owner | Name/Organization |
- [ ] Applied for adding to ESCAPE group
- [ ] Added to ESCAPE group
## Checklist
_The following steps should be completed to finalize the onboarding, in addition to adding the project to Zenodo:_
- [X] Onboarding talk scheduled
- [X] Onboarding talk given
- [ ] Documentation providedhttps://gitlab.in2p3.fr/escape2020/wp3/ossr-curation/-/issues/15ONBOARDING: Matchmaker2023-06-15T14:28:35+02:00Jutta SchnabelONBOARDING: Matchmaker# Onboarding project
## Project overview
**Title:** Matchmaker
**Description (Abstract)**: MATCHMAKER is a python package to perform cross-matching of catalogs and parameter comparisons.
**Project Owner / Organization**: Dany Vohl @v...# Onboarding project
## Project overview
**Title:** Matchmaker
**Description (Abstract)**: MATCHMAKER is a python package to perform cross-matching of catalogs and parameter comparisons.
**Project Owner / Organization**: Dany Vohl @vohl
## Repositories
### Matchmaker
| Information | |
| ------ | ------ |
| Project name | Please give a descriptive name |
| Repository link | https://gitlab.in2p3.fr/escape2020/virtual-environment/matchmaker |
| Demo | https://gitlab.in2p3.fr/vohl/notebooks |
| Project Owner | Dany Vohl |
- [x] Applied for adding to ESCAPE group on Zenodo
- [ ] Added to ESCAPE group
## Checklist
_The following steps should be completed to finalize the onboarding, in addition to adding the project to Zenodo:_
- [x] Onboarding talk scheduled
- [x] Onboarding talk given
- [x] Documentation providedhttps://gitlab.in2p3.fr/escape2020/wp3/ossr-curation/-/issues/14ONBOARDING: G-Tomo2023-06-15T14:29:04+02:00Jutta SchnabelONBOARDING: G-Tomo# Onboarding project
## Project overview
**Title:** G-Tomo
**Description (Abstract):**
**Project Owner / Organization:**
## Repositories
_Add here a subsection for each repository intended for onboarding.
Repeat for several reposi...# Onboarding project
## Project overview
**Title:** G-Tomo
**Description (Abstract):**
**Project Owner / Organization:**
## Repositories
_Add here a subsection for each repository intended for onboarding.
Repeat for several repositories._
### G-Tomo
| Information | |
| ------ | ------ |
| Project name | Please give a descriptive name |
| Repository link | URL |
| Project Owner | Name/Organization |
- [ ] Applied for adding to ESCAPE group in Zenodo
- [ ] Added to ESCAPE group
## Checklist
_The following steps should be completed to finalize the onboarding, in addition to adding the project to Zenodo:_
- [ ] Onboarding talk scheduled
- [ ] Onboarding talk given
- [ ] Documentation providedhttps://gitlab.in2p3.fr/escape2020/wp3/ossr-curation/-/issues/12merge request is not updated if a new record version is pushed to Zenodo2022-12-01T17:02:22+01:00Vuillaumemerge request is not updated if a new record version is pushed to ZenodoVuillaumeVuillaumehttps://gitlab.in2p3.fr/escape2020/wp3/ossr-curation/-/issues/4Linking technical report if not detailed documentation is provided2022-02-01T14:18:41+01:00VuillaumeLinking technical report if not detailed documentation is providedThe tech. report should be useful for users, especially in case there is no documentation.
Bu there is no clear link to the technical report.
- How is this report published? (should we make a separate zenodo record?)
- How is it associa...The tech. report should be useful for users, especially in case there is no documentation.
Bu there is no clear link to the technical report.
- How is this report published? (should we make a separate zenodo record?)
- How is it associated to the software and OSSR record?Sprint: Policy and Documentationhttps://gitlab.in2p3.fr/escape2020/wp3/ossr-curation/-/issues/3ESFRI association in codemeta2022-06-13T12:49:42+02:00Jutta SchnabelESFRI association in codemetaHow to properly distinguish software delivered by ESFRIs ('official software') and software delivered by the user community ('unofficial software'), e.g. CTA software vs. software to be used with CTA data (proposal from TV to be evaluate...How to properly distinguish software delivered by ESFRIs ('official software') and software delivered by the user community ('unofficial software'), e.g. CTA software vs. software to be used with CTA data (proposal from TV to be evaluated)" in the minutes.
## Comments from previous discussion (M. Füßling):
- I agree that we do not need to introduce additional keywords (like official or unofficial). All releases also from user-contributed software (e.g. the open community version of gammapy and not the offical CTAO science tool based on gammapy) will come as official releases. Only one from the open community version and the other released from CTAO. I agree with Thomas that one should be able to distinguish this via the 'provider' keyword.
- The provider keyword will allow to distinguish 'official' (i.e. CTAO-released) from 'non-official' software (i.e. user-contributed). I do think that we are not yet using the keyword properly though.
- The provider keyword will not allow to distinguish which user-contributed SW are supported by the ESFRIs. This could be either to say that "a certain software (e.g. tempo or astropy or 3ML) work well with the official CTAO-released science tool" or "from the tempo software package, the released version 1.3 works well with the latest CTAO-released science tool version, but not the tempo version 1.2". These are use cases that I have not yet checked with the current metadata and/or ways to implement this in the OSSR.
So far so good. Now to the current landing page (at https://escape2020.pages.in2p3.fr/wp3/ossr-pages/) and why I think that the keywords are not yet fully exploited:
- Currently, the landing page (clicking on CTA) opens the zenodo page where the keyword 'CTA' is enabled. And then a list of user-contributed software appears. This keyword currently expresses "has something to do with CTA" or "is released by the ESFRI CTA" or "can be used with CTA data". All is valid information, but I would like to be able to distinguish here the software released by CTAO and the user-contributed software (probably using the 'provider' keyword).
- I could imagine different implementations:
-- one could have in the left list of keywords one tile to select the ESFRIs as providers, or
-- on the middle results page have two sections: the above section is for official ESFRI software and the below section is for user-contributed software. In this way, still all CTA-related software is shown on one page.Sprint: Define codemeta entries and vocabularyVuillaumeVuillaume