BulkTagging extension #250

This PR is to add the possibility of applying constraints horizzontally on all the results.
A new element (advancedConstraint) is supposed to exist in the context of the community where it is possible to express constraints to be verified in the same syntax used to express constraints on the datasources.
The set of result fields that can be used to express the costraint should be extended with the subject field.

The pathMap parameter should be modified as

{
    "author": "$['author'][*]['fullname']",
    "title": "$['title'][*]['value']",
    "orcid": "$['author'][*]['pid'][*][?(@['key']=='ORCID')]['value']",
    "contributor": "$['contributor'][*]['value']",
    "description": "$['description'][*]['value']",
    "subject": "$['subject'][*]['value']"
}

It also considers FOS and SGD stored in specific param withing the context, respectively

<param name="fos">fos1,fos2</param>

and

<param name="sdg">dg1,sdg2</param>

They will be added to the subject set for the tagging, but considered separetely when dealing with the api.

This PR is to add the possibility of applying constraints horizzontally on all the results. A new element (**advancedConstraint**) is supposed to exist in the context of the community where it is possible to express constraints to be verified in the same syntax used to express constraints on the datasources. The set of result fields that can be used to express the costraint should be extended with the subject field. The `pathMap` parameter should be modified as ``` { "author": "$['author'][*]['fullname']", "title": "$['title'][*]['value']", "orcid": "$['author'][*]['pid'][*][?(@['key']=='ORCID')]['value']", "contributor": "$['contributor'][*]['value']", "description": "$['description'][*]['value']", "subject": "$['subject'][*]['value']" } ``` It also considers FOS and SGD stored in specific param withing the context, respectively ```<param name="fos">fos1,fos2</param>``` and ```<param name="sdg">dg1,sdg2</param>``` They will be added to the subject set for the tagging, but considered separetely when dealing with the api.

I decided to put all together in the same PR since there was no reason to create a PR just to accomodate commit ca216a92ad

I decided to put all together in the same PR since there was no reason to create a PR just to accomodate commit https://code-repo.d4science.org/D-Net/dnet-hadoop/commit/ca216a92ad8db5bd658e45c72f93ed861f27a7cb

Labels Milestones

BulkTagging extension #250

Step 1:

Step 2: