Add further configuration for ATLAS projects

[sol1105]

Pull Request Checklist:

• This PR addresses an already opened issue (for bug fixes / features)
  • This PR fixes issue #xyz
• Tests for the changes have been added (for bug fixes / features)
• Documentation has been added / updated (for bug fixes / features)
• HISTORY.rst has been updated (with summary of main changes)
• I have added my relevant user information to AUTHORS.md

• What kind of change does this PR introduce?:
  I added/corrected project descriptions for the ATLAS projects. This is necessary to identify the ATLAS projects via the netCDF metadata.

• Does this PR introduce a breaking change?:
  Not to my best knowledge.

• Other information:

I added the necessary project description so the ATLAS projects can be determined from the netCDF metadata.
The ATLAS datasets have each 3 different project strings defined (sigh):

ATLAS v0 / c3s-ipcc-ar6-atlas:

• in file-path: c3s-ipcc-ar6-atlas
• in metadata:
  • :project = "IPCC-WGI AR6 Atlas" ;
  • :product = "ipcc-ar6-interactive-atlas-dataset" ;

ATLAS v1 / c3s-cica-atlas:

• in file-path: c3s-cica-atlas
• In metadata:
  • :project = "Copernicus Interactive Climate Atlas" ;
  • :product = "copernicus -interactive-climate-atlas-dataset" ;
    ( notice the space between "copernicus" and "-Interactive-climate-atlas-dataset" - likely a typo from when creating the files?!)

Therefore I defined two new projects in the roocs.ini labeled with whatever is defined as product in the ATLAS metadata and set the mapper to product rather than project_id. I copied all other settings from the original project definitions. clisops is then able to detect the project without problems. I do not know if all this could have been achieved easier, but I am not aware of the possibility to define aliases for project names or multiple mappings for project.

[sol1105]

@cehbrecht Please have a look. This PR fixes the problems I have in clisops with the project detection for both ATLAS versions. I do not have permissions for this repo, so I cannot select you as reviewer and have to create the PR from a fork.

[cehbrecht]

@sol1105 good trick :) We can take it as "work-around" for now.

[cehbrecht]

... we might extend the mappings in the roocs.ini. It currently only defines the attribute to check for the project. We could also provide an expected value.

[cehbrecht]

@sol1105 works for me :) Can I merge?

[cehbrecht]

@Zeitsperre we will add a better solution for this later ... just want to get it working now for atlas datasets.

[Zeitsperre]

@cehbrecht

Sounds good. I still need to give a look over the latest comments/commits in CLISOPS. So long as everything gets a proper version and core functionality isn't affected, I trust your judgments.