Release Notes related to HDC 1 and 3A/3B #8894
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pdurbin
reviewed
Aug 8, 2022
|
|
||
| - Initial support for Globus file transfer to upload/download to/from a Dataverse managed S3 store. The current implementation disables file restriction and embargo on Globus-enabled stores. | ||
| - Initial support for Remote File Storage. This capability, enabled via a new RemoteOverlay store type, allows a file stored in a remote system to be added to a dataset (currently only via API) with download requests redirected to the remote system. Use cases include referencing public files hosted on external web servers as well as support for controlled access managed by Dataverse (e.g. via restricted and embargoed status) and/or by the remote store. | ||
| - Workflow (add Aday's notes here or reword to separate the Objective 2 work) |
There was a problem hiding this comment.
@adaybujeda do you have notes to add here?
Co-authored-by: Philip Durbin <philipdurbin@gmail.com>
https://github.com/GlobalDataverseCommunityConsortium/dataverse.git into GDCC/8611-HDC_and_related_release_notes
pdurbin
reviewed
Aug 9, 2022
|
|
||
| ### OAI-ORE and Archival Bag Changes | ||
|
|
||
| Earlier versions of the archival bags included the ingested (tab-separated-value) version of tabular files while providing the checksum of the original file (Issue #8449). This release fixes that by including the original file and its metadata in the archival bag. This means that archival bags created prior to this version do not include a way to validate ingested files. Further, it is likely that capabilities in development (i.e. as part of the [Dataverse Uploader](https://github/org/GlobalDataverseCommunityConsortium/dataverse-uploader) to allow re-creation of a dataset version from an archival bag will only be fully compatible with archival bags generated by a Dataverse instance at a release > v5.12. (Specifically, at a minimum, since only the ingested file is included in earlier archival bags, an upload via DVUploader would not result in the same original file/ingested version as in the original dataset.) Administrators should be aware that re-creating archival bags, i.e. via the new batch archiving API, may be advisable now and will be recommended at some point in the future (i.e. there will be a point where we will start versioning archival bags and will start maintaining backward compatibility for older versions as part of transitioning this from being an experimental capability). |
There was a problem hiding this comment.
Under backward incompatibilities can we please make it super clear that
GET /admin/submitDataVersionToArchive
has changed to
POST /admin/submitDatasetVersionToArchive
? This is very likely to trip people up, like I was when reviewing a PR: #8901 (comment)
mreekie
added
the
NIH OTA: 1.1.1
mreekie
added
the
pm.GREI-d-1.1.1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it: With the interactions between HDC PRs, it makes more sense to have one integrated release notes - this is it.
Which issue(s) this PR closes:
Closes #8611
Special notes for your reviewer:
Suggestions on how to test this:
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: