Question: authors and user accounts in GeoNode

[specka]

Basic problem is that all users related in GN metadata must be users inside the geonode repos. But users come from different sources: ORD, BonaRes Repo, ZALF AD, BonaRes AD, ORCID.

Users must be identified as themself no matter where they come from, and if we create them beforehand e.g. by ORD upload, they still need to be connected to their already uploaded datasets when uploading for the first time after zalf geonode launch.

Further we must discuss how new users enter the system?

[specka]

Im Workshop am 5.6. diskutiert, aber noch nicht vollständig gelöst.

• Users can use different authentication systems (ZALF AD, BonaRes AD, ORCID) to authenticate; user accounts can be merged if the same email address is used; than different user
• Question: how to deal with “further authors” → in G, an user account must be created;
  • Example: ORD data → 300 persons/authors; some still existent at ZALF
  • Should email address of user be changed if he changes organization?
  • Differentiation between “corresponding author” and “simple author”
    • “Corresponding author” (entspricht Data Cite Contributor -> ContributorType = ContactPerson
    • “Simple author
• We need to avoid duplicates “duplicated users”;
  Question:
• Do users need to login to GeoNode?
• For publishing of datasets no login is required; only Data Stewards will interact with GeoNode
  What about GeoStories?

[specka]

Konsens from 5.6.2024

• only local admin users can login into GeoNode
• authors are created by GN admins as local user accounts
• Based on information from upload tool, in this tool GeoNode groups can be automatically created / assigged (e.g. Uni Kassel)
• When author details has ORCID ID provided in the Upload-Tool
• We will automatically create a user profile and integrate information from they ORCID profile → Niko will check data protection issues

[gannebamm]

Maybe of interest: GeoNode#10342

I had the same issue with GeoNodes rigid metadata contact = GeoNode User binding. Our idea was similar: Use non-login contacts to store those information. But see: GeoNode#11511 (comment)