add 3d objects metadata block

[stevenwinship]

What this PR does / why we need it: Add to the metadata blocks that ship with Dataverse a metadata block for describing 3D data

Which issue(s) this PR closes: #11120

• Closes Feature Request: Add to the set of metadata blocks that ship with Dataverse a metadata block for describing 3D data  #11120

Special notes for your reviewer:

Suggestions on how to test this: create dataverse with added 3d metadata block. Create new dataset. add 3d object block and test searching with those fields

Does this PR introduce a user interface change? If mockups are available, please link/include them here: No

Is there a release notes update needed for this change?: Included

Additional documentation:

[github-actions]

📦 Pushed preview images as

ghcr.io/gdcc/dataverse:11120-add-3d-object-metadata-block

ghcr.io/gdcc/configbaker:11120-add-3d-object-metadata-block

🚢 See on GHCR. Use by referencing with full name as printed above, mind the registry name.

[coveralls]

coverage: 22.751%. remained the same
when pulling 4b94bf5 on 11120-add-3d-object-metadata-block
into a6e36f6 on develop.

[pdurbin]

Some feedback.

[pdurbin]

Suggested change

	3dHandling Instructions Saftey and special handling instructions for the object textbox 14 #VALUE FALSE FALSE FALSE FALSE FALSE FALSE 3dobjects
	3dHandling Instructions Safety and special handling instructions for the object textbox 14 #VALUE FALSE FALSE FALSE FALSE FALSE FALSE 3dobjects

[pdurbin]

Suggested change

	datasetfieldtype.3dHandling.description=Saftey and special handling instructions for the object
	datasetfieldtype.3dHandling.description=Safety and special handling instructions for the object

[pdurbin]

Suggested change

	- 3D Objects Metadata (`see .tsv <https://github.com/IQSS/dataverse/blob/master/scripts/api/data/metadatablocks/3d_objects.tsv>`__) __.
	- 3D Objects Metadata (`see .tsv <https://github.com/IQSS/dataverse/blob/master/scripts/api/data/metadatablocks/3d_objects.tsv>`__).

I didn't test this but I see a weird underscore at https://dataverse-guide--11167.org.readthedocs.build/en/11167/user/appendix.html

[pdurbin]

Is this update-datasetfields.sh used anywhere? I don't think so, based on the history: https://github.com/IQSS/dataverse/commits/4b94bf56aed2b1f5aae2762cd6a454964bed6bbe/scripts/api/update-datasetfields.sh

Should we simply delete this script? @sekmiller you added it in 1787fc7. Are you (or anyone reading this) actively using it?

[pdurbin]

Suggested change

	This feature adds a new Metadata block for describing 3D Object Data
	The new Metadata block will be added during the installation or upgrade of Dataverse
	### New 3D Object Data Metadata Block
	A new metadata block has been added for describing 3D object data. You can download it from the [guides](https://dataverse-guide--11167.org.readthedocs.build/en/11167/user/appendix.html). See also #11120 and #11167.
	All new Dataverse installations will receive this metadata block by default. We recommend adding it by following the upgrade instructions below.
	## Upgrade Instructions
	TODO: local 3d block, update schema, etc.

As I wrote below, I don't think update-datasetfields.sh is actively used and I'm not sure why we're maintaining it. There's no magic to do all the updating (especially including the Solr schema) so we have to write it out. Some suggestions are below.

In a GitHub suggestion I can't add fenced code blocks so I'm just going to post verbatim the 6.4 part I think we need to add and tweak. We need to change citation to 3dwhatever and otherwise edit this and add it where I'm putting TODO:

6. Update metadata blocks

These changes reflect incremental improvements made to the handling of core metadata fields.

wget https://raw.githubusercontent.com/IQSS/dataverse/v6.4/scripts/api/data/metadatablocks/citation.tsv

curl http://localhost:8080/api/admin/datasetfield/load -H "Content-type: text/tab-separated-values" -X POST --upload-file citation.tsv

7. Update Solr schema.xml file. Start with the standard v6.4 schema.xml, then, if your installation uses any custom or experimental metadata blocks, update it to include the extra fields (step 7a).

Stop Solr (usually service solr stop, depending on Solr installation/OS, see the Installation Guide).

sudo service solr stop

Replace schema.xml

wget https://raw.githubusercontent.com/IQSS/dataverse/v6.4/conf/solr/schema.xml
sudo cp schema.xml /usr/local/solr/solr-9.4.1/server/solr/collection1/conf

Start Solr (but if you use any custom metadata blocks, perform the next step, 7a first).

sudo service solr start

7a. For installations with custom or experimental metadata blocks:

Before starting Solr, update the schema to include all the extra metadata fields that your installation uses. We do this by collecting the output of the Dataverse schema API and feeding it to the update-fields.sh script that we supply, as in the example below (modify the command lines as needed to reflect the names of the directories, if different):

	wget https://raw.githubusercontent.com/IQSS/dataverse/v6.4/conf/solr/update-fields.sh
	chmod +x update-fields.sh
	curl "http://localhost:8080/api/admin/index/solr/schema" | sudo ./update-fields.sh /usr/local/solr/solr-9.4.1/server/solr/collection1/conf/schema.xml

Now start Solr.

[pdurbin]

I assume we'd get the same results if we use the technique here:

• Format Solr schema.xml using update-fields.sh on Linux #11135

I'm just raising awareness of those new docs about using Docker to consistently sort the fields.