[Datasource / Service] datasource_model_eosc
#16
Merged
claudio.atzori
merged 9 commits from datasource_model_eosc
into master
2 years ago
Loading…
Reference in New Issue
There is no content yet.
Delete Branch 'datasource_model_eosc'
Deleting a branch is permanent. It CANNOT be undone. Continue?
This PR extends the Oaf Datasource model to include the extra fields about the EOSC services.
To me the PR can be integrated
@ -7,3 +7,2 @@
<packaging>jar</packaging>
<version>2.11.34-SNAPSHOT</version>
<version>2.11.34-eosc-SNAPSHOT</version>
Is this the expected version that must go into the beta branch?
Nope, I will remove the
eosc
tag right before releasing the module.@ -488,6 +578,12 @@ public class Datasource extends OafEntity implements Serializable {
datasourcetypeui = d.getDatasourcetypeui() != null && compareTrust(this, e) < 0
? d.getDatasourcetypeui()
: datasourcetypeui;
eosctype = d.getEosctype() != null && compareTrust(this, e) < 0
If I remember well, the EOSC Catalogue does not tell (yet) if a service is a data source or not. Are the EOSC services aggregated with lower trust than the other registries?
If yes, I am ok with this logics, otherwise I think the value "Data Source" should win over "Service" by default
The Datasource deduplication is performed beyond this logic and I don't think we are going to exploit it to build a representative record whose attributes are actually set according to the trust. So I propose to get rid of any specific businness logic and limit the implementation to invoke the
super.mergeFrom()
method.You are right, Claudio. We can assume that the data sources enter the graph in the final good shape and the mergeFrom method is not expected to be called by anyone.
2f960f6a18
into master 2 years ago2f960f6a18
.Step 1:
From your project repository, check out a new branch and test the changes.Step 2:
Merge the changes and update on Gitea.