You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
The text was updated successfully, but these errors were encountered:
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;
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.
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:
The text was updated successfully, but these errors were encountered: