Discussion: Proposal to Remove Unused User Fields (Middle Name, Nationality, Alternate Telephone) #1057
Replies: 3 comments 6 replies
-
|
We have some external scripts that manage entries in the users table which we'd need to update, but I don't think that'd be much work. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, @ACLay, I will proceed with the ticket then |
Beta Was this translation helpful? Give feedback.
-
|
Yes, we don't use these, but then again we don't use much of that table (beyond as Alex says where external scripts need to deal with these columns). As you're looking at making changes anyway, would it be an opportunity to look at whether there's anything else in there that could be removed? We only use this as a link to our separate users database and that database contains all the personal details (feel free to correct me anyone). As I understand it ESS have changed how you handle user management since this was originally introduced - do you still need to record everything in here or is it now just duplicating info you have elsewhere too? |
Beta Was this translation helpful? Give feedback.
-
|
We (ELI) do not use these fields either. Moreover we are planning to use our "real" user data (from our dedicated registration/auth service) instead of those stored in UOS (something similar to the STFC approach). Presenting user data on UOS frontend from the internal UOS DB leads to a lot of confusion because the UOS DB gets only updated when the user logs in, however, the users change their registration data without signing in again. Also, we have plans to make it possible to store multiple affiliations per user and let the user select an actual affiliation for any given proposal. This affiliation should not change during the proposal lifecycle even if the user move from a facility to another one. |
Beta Was this translation helpful? Give feedback.
-
|
@srconway That’s a great point. We do intend to remove additional fields, but progress has been slower than we’d like. Removing the three fields you mentioned is a low-hanging fruit and a good place to start cleaning things up. |
Beta Was this translation helpful? Give feedback.
-
|
Tho we dont use the fields in the database we do use the PI country in one place: I think it is to do with working out where the proposal is coming from for funding reasons |
Beta Was this translation helpful? Give feedback.
-
|
@TCMeldrum thank you for looking into it.
We still keep the country of institutions, but remove the nationality of the User. I can't really see where is the 'PI Country' populated. Do you know? |
Beta Was this translation helpful? Give feedback.
-
|
Its the orginisations ID but comes as the users country: we dont store it in the db so I am happy for the column to be removed. But we still need this field in our excel exports as it is used to help work out which proposals come from which country.We don't really use the institution id/country for anything we currently just have them as a dummy value. |
Beta Was this translation helpful? Give feedback.
-
|
@TCMeldrum okay, now I see how the data is populated with Correct me if I'm wrong, but it looks like then the PR is in good shape as it does not remove the PI country. Thank you for your feedback. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone,
I’d like to open a discussion around cleaning up our Users table in UOS by removing the following fields, which are currently not used by ESS:
Background
These fields were originally added to support various user-data requirements, but in practice:
Proposal
Remove middle_name, nationality, and alternate_telephone columns from the Users table in UO.
Questions for the community
Beta Was this translation helpful? Give feedback.
All reactions