Feature Request/Idea: Add new parameter "headers" into :CVocConf

[jeromeroucou]

Overview of the Feature Request
The proposal of the issue is to permit HTTP headers customization with external controlled vocabulary services, managed via via the :CVocConf setting. This headers will be used when Dataverse call external vocabulary services (HTTP requests).

What kind of user is the feature intended for?
Sysadmin who configure :CVocConf setting.

What inspired the request?
This is related to issue #9276 and the Google group discussion

What existing behavior do you want changed?
Adding a new parameter headers into JSON configuration of :CVocConf setting, like below :

[{
        "field-name": "compoundDemo",
        "term-uri-field": "compoundDemoTermURI",
        "headers": {"User-Agent": "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:122.0) Gecko/20100101 Firefox/122.0"},
        "...": "..."
}]

User-Agent is mentioned only for example. The idea is to configure any HTTP headers used in HTTP requests to external vocabulary services.

Any open or closed issues related to this feature request?

• Issue Feature Request/Idea:Implement mechanism to support integration with OntoPortal #9276
• PR CVOC 9276 Initializing integration of ontoportal #10145
• Google group discussion
• Issue Add HTTP headers customization gdcc/dataverse-external-vocab-support#18