we have followed the Node Registration guide to register the PaNOSC node and found it quite straight forward - thanks for enabling this. We nonetheless had a few questions which about the Data Sources:
When should we register all our data sources?
For now we only registered one data source but we have over ten we would like to register. Should we register them now or wait until the Node has been registered?
When will the resource catalogue be integrated in the node resources?
We provide a resource catalogue endpoint (one of the mandatory FC’s) for harvesting the resources. Can it be used to harvest all the data sources for the node even if it does not provide all the metadata requested in the registration dashboard.
Should we try to harmonise the different policies mentioned in the data sources registration at least within the node (which is not the case today because we are a multi-partner node)?
We noticed the following polices are mentioned:
Terms of Use (mandatory)
Privacy Policy (mandatory)
Access Policy / Acceptable Use Policy
User Access Policy
Submission Policy
Preservation Policy
Thanks for any answers or insights you can give on these questions.
The registration process requires the node to register at least one Data Source. The Data Source must be a Service Catalogue and not a scientific data source as explained above. This is not clear from the documentation. If you are a node then take note of this to avoid having your data source being rejected and having to start again!
The questions in the post above therefore do not need to be answered in the case of registering a Service Catalogue.
One of the mandatory requirements for a successful Node registration is to register at least one data source (Research Product Catalogue or Service Catalogue).
You may register additional data sources during your registration, or after you have successfully registered as a Node. We would propose the latter option, as this would expedite Node registration – you can always register more data sources later.
The mandatory requirements for Node registration required the registration of at least one data source (Research Product Catalogue or Service Catalogue). These need to conform to the currently established mandatory guidelines:
You can cross-check the conformance status of your Node’s data sources through your Node’s Catalogues WG member or NOC member (this information is periodically updated and made available to all Nodes).
As far as we know, there is no mandatory requirement or EOSC policy for harmonized policies at the Node/Federation level. However, this would indeed be optimal, and one of the points that should be discussed and agreed upon by the Nodes under the Build up Group.
I think the confusion arose from the use of the term Data Source for different catalogues. Data Source sounds like it should be a data catalogue when in fact a Research Product Catalogue or Service Catalogue is meant. I presume there is a glossary of these terms in the document you cited. We should include them in the handbook.
Hi @Thanassis_Karmas I’m having troubles in interpreting Data Source meaning, because section 3.3.1 reads:
The Data Source must not be collections or catalogues of Services: i) if the Data Source also contains Services, these Services will be ignored from all onboarding activities, ii) if the Data Source is considered to be a Service itself, it must be onboarded as a Service, see Clause 3.2.
When I go to this other document section 3.10 and 3.11 then data source seems to include services as described in this thread. Indeed, it reads “you must provide the Data Source Type (i.e., Software repositories, Services metadata, Publications, Data, or all of the above)” and “Data Source Classification (i.e., Research Product Catalogue or Service Catalogue)”.
Please note that you are not consulting the correct policy document.
The correct policy for EOSC Node registration (covering also the Node’s data sources registration) is the following:
Thanks @Thanassis_Karmas the EEN Node registration policy is indeed self-consistent, but the EEN onboarding policy seems not consistent with the former to what it refers to data source. Do you expect the policies terms be aligned in the future to prevent confusion?
Hi @Carlo There is no requirement for the two policies to be consistent since their scope is different. Depending on the scope the appropriate policy applies.
