-
Notifications
You must be signed in to change notification settings - Fork 5
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
access controls on instruments #338
Comments
At the moment access to different instruments is controlled via admin so if you don't want someone to have English WS, you don't give them access. Are you asking for something more controlled (ie admins cannot give certain users access to English WS)? I would need someone to provide the on-boarding documentation - I have written this https://github.com/langcog/web-cdi/wiki/Researcher-Manual which I do point new researchers at, but I wrote it so I understood what the features are so is written from my perspective. By signup route, do you mean a link to the registration page? |
I think we are talking about a registration process starting on the home
page.
Yes, we would help with the onboarding documentation.
Maybe with respect to permissions, we'd set a default instrument
permissions that someone gets when they register. Then as admin we can
upgrade someone's permissions to have all instruments if they ask and get
approved.
…On Tue, Mar 16, 2021 at 2:12 AM Henry Mehta ***@***.***> wrote:
@mcfrank <https://github.com/mcfrank> @vmarchman
<https://github.com/vmarchman>
At the moment access to different instruments is controlled via admin so
if you don't want someone to have English WS, you don't give them access.
Are you asking for something more controlled (ie admins cannot give certain
users access to English WS)?
I would need someone to provide the on-boarding documentation - I have
written this https://github.com/langcog/web-cdi/wiki/Researcher-Manual
<http://url> which I do point new researchers at, but I wrote it so I
understood what the features are so is written from my perspective.
By signup route, do you mean a link to the registration page?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#338 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAI25F7KD7JIULH366BEJJDTD4OGDANCNFSM4ZHKVHRQ>
.
|
thanks - we are continuing to discuss with Brookes publishing and so we are not ready to build this feature yet, but I'm noting various features. brookes will sell alphanumeric codes that enable access to particular instruments. when you create a study with the affected instruments (English American long form, Mexican Spanish long form, and English CAT), you must have a code on file. if you do have a code, we
if you don't have a code, we provide a link to the product page through brookes
|
Further thoughts:
(1) We would need to automate registration - right now it's done by the
admin
(2) Part of the registration process now is assigning instruments to the
user. A user cannot create a study with the affected instruments unless
that instrument has already been assigned to that user.
(3) What to do about users who are currently in the system? Do we
grandfather them in or start charging moving forward?
…On Fri, Jul 29, 2022 at 10:21 AM Michael Frank ***@***.***> wrote:
thanks - we are continuing to discuss with Brookes publishing and so we
are not ready to build this feature yet, but I'm noting various features.
brookes will sell alphanumeric codes that enable access to particular
instruments.
when you create a study with the affected instruments (English American
long form, Mexican Spanish long form, and English CAT), you must have a
code on file. if you do have a code, we
- check whether it's valid
- banner reminding expiration date if it's less than a month
- let them make new studies and new administrations
if you don't have a code, we provide a link to the product page through
brookes
- then we enable the instrument for a year when a code is entered
- we also want to email folks when codes 1 month from expiration
—
Reply to this email directly, view it on GitHub
<#338 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB2TUTF55X6CNW6XH5N63GDVWQHKDANCNFSM4ZHKVHRQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
eventual feature request (3-6 months out at least):
Idea would be that if we add other users automatically, we won't give them access to copyright content (e.g., no english WS/WG) but they would get CAT and other languages.
@vmarchman @HenryMehta
The text was updated successfully, but these errors were encountered: