Skip to content

Commit 0042283

Browse files
committed
chore(migrate): update migration script for keywordTermUri handling
Added explanatory comments and references to Dataverse 6.3 release notes to clarify migration. Included guidance for manual loading of the keywordTermURI field and revised notices for better user direction.
1 parent 567c978 commit 0042283

1 file changed

Lines changed: 9 additions & 2 deletions

File tree

modules/dataverse-migrate-db/extra-migrations/V6.2.0.2__migrate_keywordTermUri.sql

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
--
1+
-- See also
22
DO
33
$$
44
DECLARE
@@ -15,8 +15,13 @@ $$
1515
IF keyword_count > 0 THEN
1616
RAISE NOTICE '--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---';
1717
RAISE NOTICE 'Found % keywordValue metadata fields starting with "http"', keyword_count;
18+
RAISE NOTICE 'See release notes of Dataverse 6.3 to learn more about migrating these to the keywordTermURI field.';
1819

19-
IF should_migrate THEN
20+
/*
21+
To execute this migration, the keywordTermURI metadata field needs to be loaded.
22+
So far, we never added metadata fields using a migration. Maybe it's fine to keep it a manual task for now.
23+
24+
IF should_migrate THEN
2025
RAISE NOTICE 'Migrating keywordValue fields with http... to keywordTermUri as requested by -Dmigrate.keywordTermUri';
2126
UPDATE datasetfield df
2227
SET datasetfieldtype_id = (SELECT id FROM datasetfieldtype WHERE name = 'keywordTermURI')
@@ -31,6 +36,8 @@ $$
3136
ELSE
3237
RAISE NOTICE 'Auto-migrate these into keywordTermUri using `mvn -Dmigrate.keywordTermUri ...` (re-execute migrations)';
3338
END IF;
39+
*/
40+
3441
RAISE NOTICE '--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---';
3542
END IF;
3643
END

0 commit comments

Comments
 (0)