Skip to content
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

Supervisor role cannot import new vocabulary #1857

Closed
allanaaa opened this issue Jun 15, 2022 · 4 comments
Closed

Supervisor role cannot import new vocabulary #1857

allanaaa opened this issue Jun 15, 2022 · 4 comments
Assignees

Comments

@allanaaa
Copy link

No "Import new vocabulary" button. They also can't edit or delete.

If it's up in the air, I would vote to give them importing & editing but not deleting. Or maybe just editing their own vocabularies, not the base ones / ones installed by the global admins. The manual says:

Search, read, and create privileges for Vocabularies (cannot delete)

which doesn't say anything about editing either.

@sharonmleon
Copy link
Member

I'd vote for

  • Search and read
  • Import, edit, and delete own
  • Not delete those owned by others

Edit in this context actually does make sense, since it means that you can change the language and label application. And also, reimport/update the vocab.

There is, of course, a question of whether or not Vocabs actually have owners.

@zerocrates
Copy link
Member

So yeah just to get the lay of the land here, the actual rules in current usage explicitly deny the import page, and underlying create/update/delete for vocab objects, from the Supervisor role.

Vocabularies do have owners recorded for them.

@zerocrates
Copy link
Member

Branch vocab-supervisor contains the fix here: it allows supervisors to do the import, and to update/remove only the vocabs they themselves imported.

@sharonmleon
Copy link
Member

Can confirm that with Supervisor role, I can

  • see and use, but not edit existing vocabs
  • import new vocab
  • edit those I import
  • delete those I import

zerocrates added a commit that referenced this issue Jul 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants