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
REDCap Projects don't allow have a departmental affiliation. This attribute would be helpful in searching for projects by department and for reporting on projects by department. Whereas we can join user data with departmental affiliation data, a collaborative project might have users from multiple departments. That would make it difficult to divine the one department that is truly responsible for a project. A singular department attribute on the project would provide clarity.
I think the departmental attribute should prepopulate with the department of the owner. I think the department owner field should be a drop down or auto-complete field that only allows for departments on a canonical list of departments. This will require a data source for that canonical list and a data source for the person-departmental affiliations.
The text was updated successfully, but these errors were encountered:
REDCap Projects don't allow have a departmental affiliation. This attribute would be helpful in searching for projects by department and for reporting on projects by department. Whereas we can join user data with departmental affiliation data, a collaborative project might have users from multiple departments. That would make it difficult to divine the one department that is truly responsible for a project. A singular department attribute on the project would provide clarity.
I think the departmental attribute should prepopulate with the department of the owner. I think the department owner field should be a drop down or auto-complete field that only allows for departments on a canonical list of departments. This will require a data source for that canonical list and a data source for the person-departmental affiliations.
The text was updated successfully, but these errors were encountered: