#9332 5.13 release notes #9379
#9332 5.13 release notes #9379
Conversation
sekmiller
added this to Ready for Review ⏩
in IQSS/dataverse (TO BE RETIRED / DELETED in favor of project 34)
via automation
sekmiller
changed the title
pdurbin
moved this from Ready for Review ⏩
to Review 🔎
in IQSS/dataverse (TO BE RETIRED / DELETED in favor of project 34)
Note that the "preview" links need to be changed to 5.13
|
In 69a1d7a I did a major rewrite of the release highlights. We still need to look over the upgrade details. And I need to switch all the links from http://preview.guides.gdcc.io/en/develop/ to 5.13 (which doesn't exist yet). |
|
|
||
| ### Support for Cleaning up Leftover Files in Dataset Storage | ||
|
|
||
| Experimental feature: the leftover files stored in the Dataset storage location that are not in the file list of that Dataset, but are named following the Dataverse technical convetion for dataset files, can be removed with the new [Cleanup Storage of a Dataset](http://preview.guides.gdcc.io/en/develop/api/native-api.html#cleanup-storage-of-a-dataset) API endpoint. |
There was a problem hiding this comment.
convetion -> convention
|
|
||
| - restart solr instance (usually service solr start, depending on solr/OS) | ||
|
|
||
| ### Optional Upgrade Step: remove Workflow Schema fields from Solr index |
| removed it from the schema. If you are deploying the block to your installation, make sure to | ||
| update your index. | ||
|
|
||
| If you already added these fields, you can delete them from your index when not using the schema. |
There was a problem hiding this comment.
Also, could somebody please rewrite/clarify this sentence. If I understand it correctly (a big if), the words "delete from your index" in it mean "delete from your Solr schema", and then "when not using the schema" really means "if you are not using this metadata block". It did confuse me, because we usually don't call metadata blocks "schemas", and because we are talking about solr schema in the same paragraph...
I am kinda slow of course... but I can see how it may confuse another admin - ?
|
|
||
| 7b\. | ||
|
|
||
| For installations with Custom Metadata Blocks: |
There was a problem hiding this comment.
I highlighted the change to workflow support in the section on the schema.xml updates. Please take a look to see if you think it's adequate and understandable.
|
|
||
| 7a\. | ||
|
|
||
| For installations without Custom Metadata Blocks: |
There was a problem hiding this comment.
The updates look good to me. Would it be useful to make this "without Custom or Experimental Metadata Blocks" to mirror 7b?
There was a problem hiding this comment.
@landreev was still assigned but he's done hacking on these release notes. So am I. Approved! Off to QA! Thanks again to @sekmiller for kicking these off and to all others (@qqmyers et al.) for taking a look!
|
Need some clarification on this line: This might be what's missing: (https://guides.dataverse.org/en/5.12.1/admin/metadatacustomization.html?highlight=metadata%20block#loading-tsv-files-into-a-dataverse-installation) If you are improving an existing metadata block, the Dataverse Software installation process will load the TSV for you, assuming you edited the TSV file in place. The TSV file for the Citation metadata block, for example, can be found at scripts/api/data/metadatablocks/citation.tsv. If any of the below mentioned property values are changed, corresponding ResourceBundle property file has to be edited and stored under dataverse.lang.directory location name, displayName property under #metadataBlock DatasetField, Value property under #controlledVocabulary |
Co-authored-by: Oliver Bertuch <poikilotherm@users.noreply.github.com>
Co-authored-by: Oliver Bertuch <poikilotherm@users.noreply.github.com>
What this PR does / why we need it: Consolidates release notes from all PRs included in the 5.13 release
Which issue(s) this PR closes:
Closes #9332 Write 5.13 release notes
Special notes for your reviewer:
I left release highlights blank for now because I wasn't sure what we should be highlighting.
Also Jim and or Phil please take a look at the schema.xml upgrade instructions for geospatial.
Suggestions on how to test this:
At least go through the upgrade steps
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?:
wouldn't that be ironic?
Additional documentation: