Request - user management - sharing required reading

[dustymc]

Help us understand your request (check below):

• [x] other

Describe what you're trying to do

When granting a user more roles, it is a requirement to share the information behind the Scary Red Box:

but that still requires some explanation (shared roles should always be emphasized, etc.), and then copy/paste of several resources (see https://github.com/ArctosDB/arctos/issues/8184#issuecomment-2405451349 for example). Making all of this easier and more consistent would be good. How can we do that?

1. I could add a 'copy/paste this markdown' bit to https://arctos.database.museum/Admin/user_roles.cfm
2. We could recommend sending the link to (maybe a more public-friendly version of) https://arctos.database.museum/Admin/user_roles.cfm
3. Arctos could send notifications, which sounds
   • awesome, I think many problems involve supervisors ignoring all the requirements and leaving users in the dark, and
   • possibly a little overwhelming when one gets (and/or loses?) a bunch of rights/notifications, and
   • possibly cryptic (everyone DOES see and read notifications, right?!)
4. That superawesome thing I haven't thought of yet, help??

[dustymc]

Somehow integrate @mkoo 's document/map, https://docs.google.com/document/d/1MkD2neHjR99JXtTQ2KO17Hm1d-_ROdmpIyjSjNB8eps/edit?tab=t.0 (maybe a 'click to highlight {type} roles' widget)

Merge the various documentation into one column, add copy-link.

Add rows for

• anonymous (user clicked the "I'll be nice" button)
• public (user has created a non-operator account)

These things are different, that should be documented somewhere, with all other access-stuff seems right

Try to more-hide the admin stuff - an increasing number of roles will only ever be carried by a very few people, try to make them a bit less intrusive (but they still need to be there, someone who wants to control who gets bug reports should be able to figure it out).

Going dev.

[dustymc]

I am removing the editor for table cf_ctuser_roles as part of the necessary cleanup for this. The magic can't work against malformed and inconsistent data, I don't think effective sanitation is possible, updates are an easy issue request away.

[dustymc]

@mkoo I pulled your document into a scalable table

https://docs.google.com/spreadsheets/d/1ycz47txemQ0ESokVsFPbeteC6P-47mBX4Tg2pWGrg94/edit?gid=107240188#gid=107240188

Columns are:

* package_source - groups various names (so anyone can add their own package, there could be dozens of these 'schemas' - short name-string shared by one or more role-grounps)
* package_name - "role level" 
* package_description - elaborate
* package_role_list - comma-separated no-space list of database roles
* order_within_source - integer, just what it sounds like

If you want to update anything just send me CSV, I can update the table at any time. (And we can talk about the above UI, and maybe about using this to actually assign roles, once the dust settles a bit.)

Early action shot - I've clicked a button and it's highlighted the roles in that 'package.'

[dustymc]

I also pulled the revised roles doc here https://docs.google.com/spreadsheets/d/1ytYgKaJ84HGCb5c2oRs5tAMUUkrrFohYCIBYYExurGA/edit?gid=792087406#gid=792087406

I'll clean it up a bit, ping me anyone wants edit access/to help.