Mohab25
commented
1 year ago -
for organizations, CKAN saves the organization information in several tables in the database, the group table being the most direct, there is also a member table which holds relations between users, groups ..etc., every organization has several roles where each connected to an account, a "member" role has the ability to view metadata records authored by the org, "editor" role has authorship capabilities, "admin" role can add other accounts to the org.
-
users contacts are saved in user table in the database, it holds regular contact info as name, password, email, static data as user profiles are handled via links as opposed to local storage, more elaboration is needed on "Ideally contact details are entered once and can be re-used" as the current model saves contact into in this table in a central way, it appeals to the browser behavior on entering contact details to login vs caching the details, if SSO is needed please specify so and relate to an existing RF.
-
more elaboration is needed on the meaning of
"metadata contact", if a user is a part of an organization system, they will be able to interact with metadata records according to their roles, hopefully the notification system will notify different contacts in one org about the latest changes to a specific metadata record. -
the number of contact fields is limited, it's hard to tell which field are you referring to and the functionality you want to achieve, is there any RF about this ?,
"Some contact fields can be populated from or linked to existing or new user accounts". -
do you mean that these custodians are out of the system completely "not users" ? as far as CKAN allows, users do not have to be members of an organization to be able to collaborate, there is the notion of dataset collaborators which can be enabled to allow some users accessibility to certain metadata records without them being a part of an organization, but they still have to be a registered on the system as "users",
"Some contacts (like the data contact at a custodian) might never be users but might need to be repeated / re-used across metadata records - how to manage these?"
gubuntu
How are contact details currently managed?
Ideally contact details are entered once and can be re-used
Some contact fields can be populated from or linked to existing or new user accounts
Some contacts (like the data contact at a custodian) might never be users but might need to be repeated / re-used across metadata records - how to manage these?