-
Notifications
You must be signed in to change notification settings - Fork 496
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
Feature Request: Allow for single checkbox option in custom guestbook question #11158
Comments
Interesting. This is related, although guestbooks have a different implementation than metadata blocks: It sounds like you don't want to create a multiple choice between "I agree" and "I disagree". Something like the following. |
Maybe it would be easier to create a new custom question type that was just "checkbox?" Or "Check all that apply?" The reason adding "I disagree" as an answer is not ideal is because the guestbook allows a user to download files regardless of what they select/answer. Even in the single line answer, a user could type "I disagree" and still proceed to download files. This might be important/useful because in the guestbook workflow, when users click the "access data" button they receive the guestbook popup, with the "accept" button at the bottom to submit their answers. Collection admins like the option of a clearer, required click-to-agree option. I can also ask around to see if a clearer "accept" button would be sufficient. Perhaps something like "Accept terms of use and submit" (but that seems quite long...). The problem is that a lot of users like the additional layer of having a user type or select something in addition to the "accept" button at the bottom. |
FWIW: The idea of Guestbook-at-request is to allow admins to see the answers before granting download permissions. |
Interesting. It makes me think of validation. For example, if an email is invalid (#11022), you can't proceed with downloading the file. It sounds like we want the "I agree" or the checkbox to work the same way. Download should be prevented until validation passes, until you type "I agree" or check a box. GitHub has a similar UI for when you try to delete a repo. You have to type the repo name before they show the delete button. |
The github example is an interesting comparison, and I think exactly what users are looking for. @qqmyers I'll be interested to see if having the review process for restricted files stay within the Dataverse UI will improve this experience too. My experience has been that users are looking for something that doesn't require a human to intervene/review access requests, but the new guestbook-at-request might lessen the burden sufficiently. |
Overview of the Feature Request
Users have started to use the guestbook feature as a method of asking files downloaders to "Agree" to a dataset's stated Terms of Use. This seems similar to how one "agrees" to the Terms of Use for any other software application.
Currently, the guestbook supports this in some way by allowing a collection admin to create a custom question. This is an example:
It would be great to be able to have a single checkbox option that downloaders can check to indicate agreement rather than typing "I agree" in a single line entry.
The guestbook allows collection admins to create a custom "multiple choice" question, however this option requires two or more answers. I would like to create the option to include only one possible response. This would allow for the creation of a question such as: "I agree to the dataset's stated Terms of Use" with a single response option: "I agree."
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Dataverse collection admin
What inspired the request?
Users building workflows to use the guestbook as an additional mechanism to alert file downloaders to the dataset's Terms of Use.
What existing behavior do you want changed?
Allow the "multiple choice" custom question type in a guestbook to support single answers.
Any brand new behavior do you want to add to Dataverse?
No.
Any open or closed issues related to this feature request?
No
Are you thinking about creating a pull request for this feature?
No.
The text was updated successfully, but these errors were encountered: