Skip to content

Test PR for #12659-Split terms table - #12914

Open
qqmyers wants to merge 77 commits into
IQSS:developfrom
GlobalDataverseCommunityConsortium:split-terms-table
Open

qqmyers wants to merge 77 commits into
IQSS:developfrom
GlobalDataverseCommunityConsortium:split-terms-table

Conversation

@qqmyers

@qqmyers qqmyers commented Nov 13, 2026

Copy link
Copy Markdown
Member

What this PR does / why we need it: Testing a fix for flyway V5.8.0.3* trying to add an index to the termsofuseandaccess_id column that no longer exists.

This PR should not be merged - just using it to veify setting the baseline works for new builds

Which issue(s) this PR closes:

  • Closes #

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:

jo-pol added 30 commits August 31, 2026 10:57
of DANS-KNAW#251 at 972a501 (irrelevant import changes)
# Conflicts:
#	src/main/webapp/dataset.xhtml
# Conflicts:
#	src/main/java/edu/harvard/iq/dataverse/DatasetPage.java
#	src/main/java/edu/harvard/iq/dataverse/search/IndexServiceBean.java
#	src/main/webapp/guestbook-terms-popup-fragment.xhtml
This reverts commit cd4c4b7.
qqmyers and others added 30 commits November 12, 2026 21:40
The test deletes the dataset’s only custom terms, leaving neither terms nor a license—a state the current validator rejects with HTTP 409. I’ll make the test assert that rejection, then restore CC0 through the semantic API and verify the custom terms are gone.

Updated testSemanticMetadataAPIs to expect HTTP 409 when deleting the only terms without a license, then restore CC0 and verify the custom terms disappear. Added regression coverage for that validation rule.
This reverts commit 0f64dad.
The test deletes the dataset’s only custom terms, leaving neither terms nor a license—a state the current validator rejects with HTTP 409. I’ll make the test assert that rejection, then restore CC0 through the semantic API and verify the custom terms are gone.

Updated testSemanticMetadataAPIs to expect HTTP 409 when deleting the only terms without a license, then restore CC0 and verify the custom terms disappear. Added regression coverage for that validation rule.
# Conflicts:
#	src/main/resources/db/migration/V6.12.1.1.sql

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants