QA for Fundreg and ROR support

[cmbz]

Overview of the QA Request

• The following issue: Fundreg and ROR support #14 related to a GREI aim (see: Epic: Get the existing ROR plug-in working on the dataverse demo #9151) was merged (at my request) and needs QA

What existing behavior do you want investigated?

• Please see comment: "perform some review/QA of the overall changes to Dataverse (Create a javascript for the frontend that supports Fundref #9150) with the new JavaScript (Fundreg and ROR support gdcc/dataverse-external-vocab-support#14) w.r.t. the goals of the deliverable - could be done before or after Fundreg and ROR support gdcc/dataverse-external-vocab-support#14 is merged"

[cmbz]

2023/10/10: Adding size 3 following discussion. Opportunity to review UI for future enhancements.

[kcondon]

@qqmyers I could use some help setting up the fundreq and ror CVOC on demo for real as it would be deployed to prod, not as a test metadatablock.

Can you provide the necessary config files for this specific case and whatever additional steps I need to perform?

I've read the examples, https://github.com/gdcc/dataverse-external-vocab-support , and saw the steps:

To enable external voabulary support on the example metadata block provided you need to:

Install the custom metadata block
Update your solr schema to include the custom fields
Set the :CVocConf setting - use the /examples/config/cvoc-conf.json as the value
Enable the use of this new block in your test Dataverse collection (e.g. Use the Edit/General Information menu item, /Metadata Fields section to add the block/specific fields.)
Add any desired terms from the example block to the Browse/Search Facets list (same Edit/General Information menu item)

-The first step re: custom metadata block, seeing as it would be an existing block ie. Citation, does it need to be updated to alow controlled vocab? Can I get the tsv for that?
-Since it isn't a new custom block containing new fields, the solr step can be skipped, right?
-I tried setting :CVocConf by combining the .json files into an array but I am sure my file is lacking something. I know you provided a schema to compare against but tbh, it's not something I'm up to speed on.
-The other two steps are again only for a new block so can be skipped. Seems like the only steps in our use case are maybe updating the citation block to enable cvoc and uploading the correct json file to enable fundreq and ror, assuming those scripts are hosted/served remotely. Is that correct?

[kcondon]

Thanks @qqmyers and @landreev, I was able to configure this on test and demo. The main changes needed were:

1. create a cvoc_fundreg_ror.json that includes the json from the individual files into an array:
   cvocconf_fundreq_ror.json

2. Move the .js scripts from the gdcc repo to /var/www/http/cvoc/js and make the owner dataverse

3. Edit ssl.conf and add Rewrite rules to skip these files from being forwarded to payara, ie. serve from apache:
   RewriteRule ^/cvoc/js/cvocutils.js /var/www/html/cvoc/js/cvocutils.js
   RewriteRule ^/cvoc/js/fundreg.js /var/www/html/cvoc/js/fundreg.js
   RewriteRule ^/cvoc/js/ror.js /var/www/html/cvoc/js/ror.js

Status of this issue is resolved:

1. deployed to demo, 2. can set author affiliation (ror) and grantfunding/funder fields using controlled vocab. 3. The last item in Iqss/9150 handle fundreg reqs for ext cvv #9402 said all major issues resolved and needs UX post spa 4. Will communicate demo availability to dvn-core shortly 5. The path it took was winding but I think it is mostly delivered but needing UX at a later date. I think there is some useful info in the issues found as in what to look out for, later.