-
-
Notifications
You must be signed in to change notification settings - Fork 389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate Research Update collaborators property from a list with one string value to just a string. #3695
Comments
simpler way:
The scripts could be combined. |
A bit confused, you mean that for |
For each Research Update Entry, there will only ever be one person given credit. Different Updates can have different creators, so individual Updates still need a field. I think there is no author field currently, but that is something I made up, for this simplification. If a person makes an Update for their own Research Article, they are considered a collaborator (see screenshot above.) It kinda doesn't make sense to be a "collaborator" on your own Research Article, that's why to go for a change to "author" instead of "collaborator". But we can still show "collaborator" on the user interface. We would still want to display all the individual people who contributed, this ticket is meant to be a refactoring that simplifies the data model. |
As a developer, I want the database schema to be easy.
On Research Updates, the collaborators property is a list, but it should really be a string. source.
The idea:
...well, I see why we just live with this mild inconvenience.
This process could be simplified with a maintenance downtime, but I'll think about that later.
The text was updated successfully, but these errors were encountered: