Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Task: Discussion on future of Related projects #133

Closed
mwallschlaeger opened this issue Jul 2, 2024 · 3 comments
Closed

Task: Discussion on future of Related projects #133

mwallschlaeger opened this issue Jul 2, 2024 · 3 comments
Labels
Metadata question Further information is requested TF GeoNode

Comments

@mwallschlaeger
Copy link

Task Description

Do we continue to use the previous BonaRes Projects as metadata entry for related projects, or do we overcome these. How to implement this field in general? BonaRes mapping linked this to hierarchyLevelName in inspire but when i read description on hierarchyLevelName inside the inspire standard this seems odd to me.

Screenshot from inspire standard:
image

@mwallschlaeger mwallschlaeger added question Further information is requested Metadata TF GeoNode labels Jul 2, 2024
@specka
Copy link

specka commented Jul 2, 2024

Konsens or idea from 02.07.2024:

  • we need a separate system (FDM Project Database), in which we can manage all project information required for the publication of ZALF and external datasets
  • this database will be filled with information and synchronized on the one hand by the ZALF Projektdatenbank (information from the PAP system)
  • this database allows also the "manual" addition of external projects
  • it also enables to integrate further project database from other institutions (e.g. from Kassel university)
  • this system will be also used in the Upload Tool to faciliate project selection in the dataset submission
  • the synchronisation task need to be monitored; if synchronization fails, we need to be informed; maybe the GeoNode-celery systems brings everything withhim;

@mwallschlaeger
Copy link
Author

in addition to that: we agreed on not using the inspire field HierachyLevelName anymore. Our interpretation of the field does not follow the official inspire interpretation.

@mwallschlaeger
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Metadata question Further information is requested TF GeoNode
Projects
None yet
Development

No branches or pull requests

2 participants