-
Notifications
You must be signed in to change notification settings - Fork 487
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
Dataset Linking: As a dataverse owner, I want to link a related dataset to my dataverse to help relevant researchers find it. #4410
Comments
Huh, I didn't realize this was a feature of DVN 3.x but sure enough "Link Datasets/Studies" appears on the "3.6 & 4.0 Feature Comparison" spreadsheet at https://docs.google.com/spreadsheets/d/1ftHM6E4b9Dft_AvA6KTzeklJyLguItz2_0hNAFL8-VM/edit?usp=sharing Please note that even superusers cannot delete links. That's what #1364 is about. |
Today in Slack @thegaryking brought up this feature, requesting:
Also, related to the feature's name, "link" he said:
All good feedback to consider when adding this feature for all dataverse admin's. Bonus feature request, also from Gary, to have the system suggest datasets to dataverse admin's:
Some related issues to also consider:
|
After much deliberation, some updates to this issue:
For future reference, this is our document where the design team deliberated on this feature. Keep in mind that it is not 100% up to date, especially regarding permissions: https://docs.google.com/document/d/14J8uBV4kNPHDfbiumNNKb01tdEksPpnfbRklrY1KhAc/edit |
Discussed with UX team, will revise |
Just adding here for posterity the decisions made about how the type-ahead field works for finding dataverses to link to: Dataverse allows users to create dataverses with names that have 1 or more characters. But when a user starts typing in the type-ahead field to look for a dataverse to add a dataset link into, the field will start displaying matching dataverse names after 3 characters have been entered into the field. (The component used for the type-ahead field has a default character limit of 2 characters.) Which means that the user won't be able to find dataverses that have names that are fewer than 3 characters. This is fine for Harvard Dataverse because all published dataverses have names (display names, not aliases) that are more than 3 characters (and the unpublished dataverses that have names with fewer characters are obviously test dataverses). Open questions we've decided to address later:
|
…o dataset linking popup help msg, removed it from success msg [ref #4410]
Added configurable support team name and text link to contact popup to dataset linking popup help msg, removed it from success msg. Sending back to @sekmiller for a bug fix.
|
@dmurphy @scolapasta @sekmiller @djbrooke
|
Just talked about that first point with @djbrooke - let's have both the UI and API require that a dataset is published in order to link it. We talked about the second point too. For now let's leave the unlinking API as it is, and if we end up getting a ton of support tickets we can revisit. |
This issue is narrowed down from the earlier, broader issue #2053.
Currently, only Super Users have the ability to link other users' datasets to their dataverses. This functionality used to be available to all users before Dataverse 4.0. Let's restore this functionality so all users are able to link others' datasets to their dataverses.
Issue #1840 also seems relevant.
The text was updated successfully, but these errors were encountered: