GeoNode Task Force protocol 11.06.2024 - 11:00 - 12:30

[mwallschlaeger]

Participants: @specka , @mwallschlaeger , Niko, @krmeierzalf, @KevinUrbasch

ORD / BonaRes Metadata Mapping

Abbreviation:

ORD -> OpenResearchData (old ZALF research data management platform)
GN -> GeoNode

1.A) Licenses

mapping of metadata fields from ORD datasets. Niko once gave me a list of funding agencies and licenses to be available in GN metadata editor. Now after investigating ORD data, in ORD licenses and funding agencies are referenced which are not available in Nikos list. We need a mapping or solution on how to deal with these entries. Else we cannot continue work in integrating ORD datasets.

refs:

• BonaRes / Inspire / Datacite / GeoNode / Smart.finder metadata mapping (WIP): https://docs.google.com/spreadsheets/d/15XTQuYxoRwm7RqDw-swC_GsCjof6oEIV-P6kGMoz0J0/edit?usp=sharing
• https://github.com/zalf-rdm/OpenResearchData_Migration/issues/13

Discussion results:

user story upload tool:

User logs into upload tool, uploads data, fills out metadata. All users who want to publish data in our repository must accept our term of use. The terms include:

• dataset (data itself) is published under CC-BY license
• metadata is published under CC-0 license
• use ZALF use constraints including ZALF disclaimer and personal disclaimer are set with inspire restriction codes: Intellectual Prop, Copyright, Restricted)
  Further, users can define their own data restrictions by filling out the field other constraints (which published with the restriction-code: otherRestrictions)

how to handle this inside GN

After the metadata is edited and confirmed inside the metadata editor, this metadata get applied onto the corresponding geonode objects, like defined in GeoNode Workshop protocol 05.06.2024 - 09:00 - 12:00. The following metadata fields are used (need to be created):

• base.license <-> dataset license
  • list of all used licenses. All new published dataset get CC-BY. Only if somebody requests something else we are changing this. Old datasets e.g. from ORD are getting the license they had before. All Licenses must be create for the ORD licenses
• base.license_metadata <-> metadata license
  • list of metadata licenses. Currently only CC-0.
  • old ORD datasets and new published datasets metadata receive CC-0 as metadata license
• base.use_constraints: ZALF use contraints including ZALF disclaimer and personal disclaimer
  • combination of restrictioncodes and free text field (automatically filled by upload tool on setting metadata)
    • set with inspire restriction codes: Intellectual Prop, Copyright, Restricted
• base.other_constraints: user definined additional constraints
  • combination of restrictioncodes and free text field
    • fixed with inspire restriction code: otherRestrictions
    • filled with optional disclaimer users wrote into upload tool

TODOs

• @mwallschlaeger : Implement additional field for metadata licenses
• @svoboda-zalf ZALF disclaimer and personal disclaimer)requires a new text
• @svoboda-zalf Ask external carsten related to license disclaimer
  -> Z:\FOR\FDS\FDS-Shared\WG_FDM_DIS\Team\01_Team_Meetings\TF_Data_Publication
• @zalf-rdm/zalf-dis extend ZALF Policy by Rights of first use