Describe the bug
The metadata security level/visibility is not considered when some OrcidProfileSectionFactory entry is calculating the metadata signature.
To Reproduce
Steps to reproduce the behavior:
Considering some configuration with some keyword and the configured metadata security [0 2] or [0 1]
configure the keyword to being pushed to orcid using some OrcidSimpleValueObjectFactory
add some keyword metadatavalue with visibility [2] (hidden) on some person profile connected with orcid
some orcid queue entry should be created for the orcid profile
Expected behavior
We expect only values with no visibility (null) or visibility 0 being pushed to orcid, because usually only these values are being shown to the public.
Related work
Link to any related tickets or PRs here.
we suggest some simple check on the implementations of the AbstractOrcidProfileSectionFactory to filter the metadatavalues which are used for generating the metadata signature . Only those are kept which have the value null or 0.
we are not sure if the normal DSpace Researcher Profile has the ability to hide certain metadata values.
Describe the bug The metadata security level/visibility is not considered when some OrcidProfileSectionFactory entry is calculating the metadata signature.
To Reproduce Steps to reproduce the behavior:
Expected behavior We expect only values with no visibility (null) or visibility 0 being pushed to orcid, because usually only these values are being shown to the public.
Related work Link to any related tickets or PRs here.
AbstractOrcidProfileSectionFactoryto filter the metadatavalues which are used for generating the metadata signature . Only those are kept which have the value null or 0.