-
Notifications
You must be signed in to change notification settings - Fork 488
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
Epic: Get the existing ROR plug-in working on the dataverse demo #9151
Comments
priority discussion with Stefano;
|
Top priority for upcoming sprint |
sizing:
|
sprint:
|
Resizing for next sprint
|
Monthly update review bump: @sekmiller Steve, would it be possible to drop some breadcrumbs on this in such a way that my 5th grader brain can process them? Here's my shot at it. Lemme know if it's accurate. In this issue we installing a script for pulling down the Author affiliation field from the Research Organization Registry (ROR) in our demo dataverse. This previously ran and it represents a new lightweight way of retrieving this information and having more control over the user experience. The feature no longer works out of the box as of 5.12 and so the scope of work has expanded to understanding what we need to do to get this working. I'm unsure of whether the info that follows is within the expanded scope of this issue or will be in additional issues: Coming out of our meeting on the topic of PIDs we decided that our initial level of support for ROR will include:
|
sprint sizing:
|
As discussed at the sprint kickoff just now 🏈 🏈 🏈 the backend code for this issue is dependent on this (currently draft) PR by @qqmyers: |
See #9150 (comment) for info on an implementation mirroring the FundReg and ORCID scripts. |
Daily
|
Question for @qqmyers and @pdurbin:
Is this NIH GREI deliverable (1.2.1) complete? |
#12 is obsolete and refers to the example that existed before #9150. Before the deliverable is complete, there are a few things to do:
These steps are somewhat generic and probably apply to FundReg and to ORCID as well (at least the parts related to the external vocab/lookup of people at the ORCID service). |
Fundreg and ROR support - merged to make it easier to access for testing in IQSS/dataverse#9151
2023/12/18
|
FWIW: The "just work" issue is out-of-date, which is why ROR works on demo.dataverse.org - #9402 was added to v5.14 and the scripts were updated in gdcc/dataverse-external-vocab-support#14. Whether the way it works on demo is good-enough to use in production or if further work is desired is a reasonable question, but if it is acceptable as a start, it's a size3 to put it on Harvard. |
Ah thanks. I was just about to ask about the "just work" issue. Should I just close gdcc/dataverse-external-vocab-support#12 then? @pdurbin what do you think? About determining if the way it works on demo is good enough, I think we've heard a bit from the ROR folks about best practices for using ROR that we could consider. We could do usability testing to determine how much of those best practices we should be following before we apply these changes to the Author Affiliation field in Harvard Dataverse. And I have questions about how this affects several metadata exports, based on a quick review of the exports in Demo Dataverse, but I could start documenting those so they can be reviewed and worked on later if needed. If we did this, I would be concerned about us not finding the bandwidth to improve this later, similar to other issues where Dataverse exports were improved but extra steps are needed to apply those improvements to datasets that have already been published in Dataverse repositories, e.g. IQSS/dataverse.harvard.edu#222 and IQSS/dataverse.harvard.edu#146 |
@jggautier good catch. I just closed gdcc/dataverse-external-vocab-support#12 in favor of this one. |
Thanks @pdurbin. As discussed during today's Dataverse monthly meeting, the next step could be to evaluate the implementation and recommend more next steps. We could do the following:
But ROR can be used to help users add other types of information, like:
So while it'll be helpful to evaluate at how ROR is implemented for just this Author Affiliation field, if we make any changes to how ROR is implemented for just this Author Affiliation field, apply those changes to Harvard Dataverse, and encourage other installations to do the same, we risk needing to re-evaluate those changes once we're able to consider the use of ROR and other external controlled vocabularies, like ORCID, across all of the metadata fields that Dataverse ships with, which is part of what IQSS/dataverse.harvard.edu#230 is about. That work should involve considering larger changes, such as potential re-designs to the metadata model and the forms in the UI. So I'm recommending that we:
|
We'll close this issue and open a new issue for what I recommended in my earlier comment about evaluating what's been put on Demo Dataverse and building on that evaluation as we're looking at the use of ROR and other controlled vocabularies, like ORCID, across all of the metadata fields that Dataverse ships with. |
This script completes a single field on a form. Author affiliation
definition of done:
Make a recommendation as to if it can go into productionIf this is the case this will lead to a separate issue to move the script into productionThe text was updated successfully, but these errors were encountered: