peer35
commented
1 month ago TODO:
-
Mock up an updated instrument Edit form proposing the new fields.
-
Decide on database change
-
Implement database change
-
Implement form changes
-
Implement catalog changes
-
Create a script to migrate as many existing instrument records as possible
Currently instrument names, variants, aliases and versions are stored as a single string in the name field. It would be better to have a single instrument table, linked to a separate table with the name variants or versions.
An alternative could be to store the name and variants as a jsonb object, but only if we're certain the amount of querying will be limited. https://guides.rubyonrails.org/active_record_postgresql.html#json-and-jsonb
The instrument names could still be shown as single strings in the front end.