11367 release notes

[sekmiller]

What this PR does / why we need it: Release Notes for 6.7 release

Which issue(s) this PR closes:

• Closes issue Release 6.7: Create release notes #11367

Special notes for your reviewer:
I didn't come up with a lot of "Release Highlights" feel free to add more.
For the upgrade instructions there wasn't a solr upgrade, nor any changes to the core metadata blocks. I didn't see a need to do a re-index or re-export, unless we make that part of upgrading as a rule. In 48684bc we explain that due to bugs in the Croissant exporter, a reexport is needed.

Suggestions on how to test this: Please follow the upgrade instructions and run a smoke test at the very least.

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

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

Additional documentation:

[pdurbin]

It looks like this step from https://guides.dataverse.org/en/6.6/developers/making-releases.html#write-release-notes wasn't observed (added in 07ecb4d as part of #10676):

"Snippets may not include any issue number or pull request number in the text so be sure copy the number from the filename of the snippet into the final release note."

% for i in 10134 10506 10520 10567 10618 10680 10941 11004 11041 11147 11172 11191 11197 11243 11252 11271 11275 11280 11287 11292 11299 11301 11305 11357 11360 11374 11394 11401 11413 11414 11415 11417 11434 11438 11482 11489 11497 11518 11540 11581 9247 9620; do echo "looking for $i..."; ack $i 6.7-release-notes.md;echo; done 
looking for 10134...
- It is now possible to link draft datasets to other Dataverse collections. As usual, the datasets will only become publicly visible in the linked collection(s) after they have been published. To publish a linked dataset, your account must have the "Publish Dataset" permission for the Dataverse collection in which the dataset was originally created. Permissions in the linked Dataverse collections do not apply. See also #10134.

looking for 10506...
In Dataverse 6.5 File Previewers were enabled in the "demo or eval" containerized (Dockerized) environment (#11025). These previewers are now available in the development environment as well and [documentation](https://dataverse-guide--11181.org.readthedocs.build/en/11181/container/running/demo.html#file-previewers) has been added explaining how to configure them. See also #10506 and #11181.

looking for 10520...

looking for 10567...
used. See [the guides](https://dataverse-guide--10567.org.readthedocs.build/en/10567/api/native-api.html#reconcile-the-pid-of-a-dataset-if-multiple-pid-providers-are-enabled), #10501, and #10567.

looking for 10618...
See also the [Container Guide](https://dataverse-guide--11477.org.readthedocs.build/en/11477/container/index.html), #10618, and #11477.

looking for 10680...
Archival Bags now use the JVM option `dataverse.bagit.sourceorg.name` in generating the bag-info.txt file's "Internal-Sender-Identifier" (in addition to its use for "Source-Organization") rather than pulling the value from a deprecated `bagit.SourceOrganization` entry in Bundle.properties ("Internal-Sender-Identifier" is generated by appending " Catalog" in both cases). Sites using archival bags would not see a change if these settings were already using the same value. See #10680 and #11416.

looking for 10941...

looking for 11004...
- The tutorial on running Dataverse in Docker has been updated to include [how to load a metadata block](https://dataverse-guide--11204.org.readthedocs.build/en/11204/container/running/demo.html#additional-metadata-blocks) and then update Solr to know about the new fields. See also #11004 and #11204

looking for 11041...

looking for 11147...

looking for 11172...
- Deeply nested compound fields are not (yet) supported by Dataverse but the Search API now properly avoids returning duplicate values for them. See #11172.

looking for 11191...

looking for 11197...
See [the guides](https://dataverse-guide--11193.org.readthedocs.build/en/11193/installation/config.html#feature-flags), #11193, #11197, and #11314.

looking for 11243...

looking for 11252...
[Dataverse Previewers](https://github.com/gdcc/dataverse-previewers) v1.4 contains a bug in the NcML previewer that prevents it from working with signed URLs. (See #11252 for screenshots.)
See also #11252 and #11311.

looking for 11271...
### Update File Metadata API (PR #11271)

looking for 11275...
See also [the guides](https://dataverse-guide--11359.org.readthedocs.build/en/11359/api/native-api.html#imposing-a-limit-to-the-number-of-files-allowed-to-be-uploaded-to-a-dataset), #11275, and #11359.

looking for 11280...

looking for 11287...
An undocumented Search API parameter called "show_my_data" has been removed. It was never exercised by tests and is believed to be unused. API users should use the [MyData] API instead. See the [API changelog](https://dataverse-guide--11375.org.readthedocs.build/en/11375/api/changelog.html), #11287 and #11375.

looking for 11292...
See also [the guides](https://dataverse-guide--11359.org.readthedocs.build/en/11359/api/native-api.html#updating-file-tabular-tags), #11292, and #11359.

looking for 11299...
See [the guides](https://dataverse-guide--11349.org.readthedocs.build/en/11349/api/native-api.html#restrict-files), #11299, and #11349.

looking for 11301...

looking for 11305...
In previous versions of Dataverse, it was only possible to export metadata from published datasets. It is now possible to export metadata from draft datasets via API as long as you supply an API token that has access to the draft. As before, when exporting metadata from published datasets, only the latest published version is supported. Internal exporters have been updated to work with drafts but external exporters might need to be updated (Croissant definitely does). See "upgrade instructions" below for details. See [the guides](https://dataverse-guide--11398.org.readthedocs.build/en/11398/api/native-api.html#export-metadata-of-a-dataset-in-various-formats), #11305, and #11398.

looking for 11357...

looking for 11360...

looking for 11374...

looking for 11394...

looking for 11401...
See also [the guides](https://dataverse-guide--11359.org.readthedocs.build/en/11359/api/native-api.html#updating-file-metadata-categories), #11401, and #11359.

looking for 11413...
See also [the guides](https://dataverse-guide--11359.org.readthedocs.build/en/11359/admin/rate_limiting.html), #11413, and #11359.

looking for 11414...

looking for 11415...
It's now possible to retrieve the Application Terms of Use (called General Terms of Use in the UI) via API. These are the terms users agree to when creating an account. See [the guides](https://dataverse-guide--11422.org.readthedocs.build/en/11422/api/native-api.html#get-application-terms-of-use-general-terms-of-use), #11415 and #11422.

looking for 11417...

looking for 11434...

looking for 11438...

looking for 11482...

looking for 11489...

looking for 11497...

looking for 11518...
- OJS 3 (version 3.3 and higher) is now supported as an integration with Dataverse. See [the guides](https://dataverse-guide--11518.org.readthedocs.build/en/11518/admin/integrations.html#open-journal-systems-ojs) for details.

looking for 11540...
Information about various Dataverse-related AI efforts have been documented in a new [AI Guide](https://dataverse-guide--11541.org.readthedocs.build/en/11541/ai/index.html). See #11474, #11540, and #11541.

looking for 11581...
- The [dataverse-metadata-crawler](https://github.com/scholarsportal/dataverse-metadata-crawler) was added to the guides. See #11581.

looking for 9247...

looking for 9620...

That means that most of these entries are dead ends. There's no issue link to click to learn more about the item.

It's way more work to put these issue links in after the fact than to start over so I'll just close this PR and start over.

I'll definitely take into consideration highlights and upgrade instructions @sekmiller has put in this PR. Thanks for taking a swing at this.