-
Notifications
You must be signed in to change notification settings - Fork 29
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
Sketch Engine connection database not individual based #218
Comments
@iztokkosem You mean configuring connection for whole local installation? Or for one dictionary? |
For one dictionary. |
Only setting that is not shared for all dictionary users is SkE API key. That would mean adding SkE API key to "Configure-Sketch Engine connection" page. Is there something else that should be added? |
I guess GDEX configuration, or does that come automatically with the SkE API key and the settings attached to the user of that key? |
GDEX configuration is set in SkE. I discussed this with @mjakubicek and we came up with better option then storing user API key in dictionary config (because of security issues). |
Hm, not sure if I understand your solution. Lexonomy works in a way where you assign users by their Lexonomy email, and then give them the rights. Normally, there is one (or a few) admins with access to configuration settings, ability to download/upload. Others are only allowed to edit. |
You need to differentiate between properties of a dictionary (who has access and at which level) and properties of a user (API key to Sketch Engine). The latter is strictly per user not per dictionary. |
Do we want to support SkE API key per dictionary? Or sticking with the user only API key? @mjakubicek @iztokkosem |
We are using the Sketch Engine connection (via our own plugin), and we found it would be useful that the project admin who sets up the database can also set Sketch Engine link settings for the entire team. Namely, currently, each user needs to insert his/her API code etc., plus upload GDEX configuration. This would mean that anyone who is given access to the database is automatically able to use all the features existing users use.
The text was updated successfully, but these errors were encountered: