You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ksierks opened this issue
Nov 3, 2022
· 0 comments
· Fixed by #1408
Labels
back-endIssues relating to the service layer, repository, model, configuration, or databasedeveloperIssues effecting developers of IRIDA, but that aren't user facingmetadataSample metadata, line list, and metadata visualizations
Should we add a unique database constraint to the label column in the metadata_field table?
How does it work now?
I am able to create multiple entries in the with the same label with the following line of code: templateService.saveMetadataField(new MetadataTemplateField(label, "text"));
How should it work?
I think labels (and type) should be unique for data cleanliness.
Additional information
Add any other context, files, or screenshots about this request here.
The text was updated successfully, but these errors were encountered:
ksierks
added
back-end
Issues relating to the service layer, repository, model, configuration, or database
metadata
Sample metadata, line list, and metadata visualizations
developer
Issues effecting developers of IRIDA, but that aren't user facing
labels
Nov 3, 2022
back-endIssues relating to the service layer, repository, model, configuration, or databasedeveloperIssues effecting developers of IRIDA, but that aren't user facingmetadataSample metadata, line list, and metadata visualizations
What needs changed?
Should we add a unique database constraint to the label column in the metadata_field table?
How does it work now?
I am able to create multiple entries in the with the same label with the following line of code:
templateService.saveMetadataField(new MetadataTemplateField(label, "text"));
How should it work?
I think labels (and type) should be unique for data cleanliness.
Additional information
Add any other context, files, or screenshots about this request here.
The text was updated successfully, but these errors were encountered: