We need to allow organizational administrators to replace the list of default research output types, or add additional types to the default list.
Here is a screenshot of the select box a researcher currently interacts with when editing/adding a research output:
Please refer to the spec document for some ideas on implementation.
This will require the creation of a new table that stores the template_id foreign key and the value of the type. When the admin wants to append their entries to the default list, the code should add an entry for each default type to this table . This will ensure that changes to the default list do not change the admin's selections over time.
The current output types are defined as an enum on the research_output model. If it makes things easier, those values can be moved into a separate table of their own.
The template model will then need to be updated to ensure that the version method is still working and does not require any changes needed to accommodate the new values. The Template's deep_copy method should also be updated to ensure that the values in the table are carried forward to new versions.
Once the admin components are in place, the research outputs view and controller will need to be updated to fetch the correct values.
We need to allow organizational administrators to replace the list of default research output types, or add additional types to the default list.
Here is a screenshot of the select box a researcher currently interacts with when editing/adding a research output:
Please refer to the spec document for some ideas on implementation.
This will require the creation of a new table that stores the template_id foreign key and the value of the type. When the admin wants to append their entries to the default list, the code should add an entry for each default type to this table . This will ensure that changes to the default list do not change the admin's selections over time.
The current output types are defined as an enum on the research_output model. If it makes things easier, those values can be moved into a separate table of their own.
The template model will then need to be updated to ensure that the version method is still working and does not require any changes needed to accommodate the new values. The Template's deep_copy method should also be updated to ensure that the values in the table are carried forward to new versions.
Once the admin components are in place, the research outputs view and controller will need to be updated to fetch the correct values.