GeoNode Task Force protocol 25.06.2024 - 13:00 - 14:30

[mwallschlaeger]

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

Abbreviation:

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

1. Organizational Topics

• GeoNode Retreat: takes place from the 7th til the 9th of october
  • location about 1h away from Müncheberg
  • Topic ideas:
    • Workflow? Conception and also adoption, to see, if the workflow works.
    • (Integration ORD Data) → hopefully finished before retreat
    • Integration of published BonaRes Repository data?

2. ORD / BonaRes Metadata Mapping

2.A) Contact Roles

Geonode currently uses: ISO 19115:2003 (GeoNode/geonode#11902) which is only supporting a limited number of contact roles, lately added with: GeoNode/geonode#10367

Datacite offers way more contact roles than the current GN provides how to deal with this situation?

Adding more contact roles to GeoNode is a mediocre effort.
See contributorType fields Datacite metadata used in ORD below:

'ContactPerson',
'DataCollector',
'DataCurator',
'DataManager',
'Editor',
'Funder',
'HostingInstitution',
'Other',
'ProjectLeader',
'ProjectManager',
'ProjectMember',
'RegistrationAgency',
'RelatedPerson',
'ResearchGroup',
'Researcher',
'Supervisor'

References:

• https://github.com/zalf-rdm/OpenResearchData_Migration/issues/12 - related issue
• https://docs.google.com/spreadsheets/d/15XTQuYxoRwm7RqDw-swC_GsCjof6oEIV-P6kGMoz0J0/edit?usp=sharing - metadata mapping

Discussion results:

We decided on implementing all current contact roles from the BonaRes metadata schema to fully support Datacite contributorTypes and inspire contactRoles metadata schema. The reasons for this are that we a) are unable and even forbidden to map current ORD Datacite contributorTypes to inspire contactRoles. Because there is no 1to1 mapping possible and the number of contactRoles in INSPIRE is less than the one in Datacite. Therefore mapping would lead to a information loss. An alternative we discussed was to keep the information on Datacite but do not store Datacite roles on GeoNode, what would forbid us to update metadata stored on Datacite for all ORD datasets forever.

So we agreed on the following implementation details:

• implement all roles currently defined in BonaRes:

Responsible party - (Role = Data Collector)
Responsible party - (Role = Data Curator)
Responsible party - (Role = Editor)
Responsible party - (Role = Hosting Institution)
Responsible party - (Role = Other)
Responsible party - (Role = Producer)
Responsible party - (Role = Project Leader)
Responsible party - (Role = Project Manager)
Responsible party - (Role = Project Member)
Responsible party - (Role = Registration Agency)
Responsible party - (Role = Registration Authority)
Responsible party - (Role = Related Person)
Responsible party - (Role = Research Group)
Responsible party - (Role = Researcher)
Responsible party - (Role = Rights Holder)
Responsible party - (Role = Sponsor)
Responsible party - (Role = Supervisor)
Responsible party - (Role = Work Package Leader)
Responsible party - (Role = Author)
Responsible party - (Role = Custodian)
Responsible party - (Role = Distributor)
Responsible party - (Role = Originator)
Responsible party - (Role = Owner)
Responsible party - (Role = Point of contact)
Responsible party - (Role = Principal Investigator)
Responsible party - (Role = Processor)
Responsible party - (Role = Publisher)
Responsible party - (Role = Resource Provider)

• provide information on mapping between Datacite and INSPIRE inside the Metadata Editor
• add additional information about the belongings of each field inside the database model, so distinguishing between different location is possible afterwards

TODOs

• implement missing roles: Feature: Add all BonaRes ContactRoles geonode#130
• migrate TF Workflow to fully use github project board: move TF workflow to github project board geonode#131