-
Notifications
You must be signed in to change notification settings - Fork 490
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
update of the keywordVocabularyURI metadata to make it consistent wit…
…h its name Controlled Vocabulary URL
- Loading branch information
1 parent
a5f4bd7
commit 9f72845
Showing
3 changed files
with
7 additions
and
2 deletions.
There are no files selected for viewing
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
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
5 changes: 5 additions & 0 deletions
5
src/main/resources/db/migration/V6.1.0.2__10288-update_keywordVocabularyURI_metadata.sql
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
-- update of the "keywordVocabularyURI" metadata to make it consistent with its name "Controlled Vocabulary URL" | ||
UPDATE datasetfieldtype SET name = 'keywordVocabularyURL' | ||
WHERE name = 'keywordVocabularyURI' | ||
AND parentdatasetfieldtype_id = ( | ||
SELECT id FROM datasetfieldtype WHERE name = 'keyword') ; |
9f72845
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
keywordValue pouvait accueillir des "prefLabel" ou des "termUri", donc des libellés ou des ID. Maintenant on fait la différence entre les 2 avec le nouveau champ keywordTermURI.
Peut se poser la question de migrer la donnée de keywordValue à keywordTermURI si
keywordValue like 'http%'
9f72845
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Le select et l'update est intégré à la doc, dans le .md
Concernant la modification de la métadonnée coté Recherche Data Gouv de keywordTermURL à keywordTermURI, oui c'est bien ce qui est prévu (sujet spécifique à l'équipe)