-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'funder-registry-announcement' into dev
- Loading branch information
Showing
19 changed files
with
194 additions
and
37 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -61,9 +61,9 @@ In line with ROR's commitment to the [Principles of Open Scholarly Infrastructur | |
|
||
### Operations team | ||
|
||
The ROR operations team is responsible for strategic decision-making about registry resourcing and operations. This team comprises the ROR project lead and a representative from each governing organization. | ||
The ROR operations team is responsible for strategic decision-making about registry resourcing and operations. This team comprises the ROR Director and a representative from each governing organization. | ||
|
||
- [Maria Gould](https://cdlib.org/contact/staff_directory/maria-gould-staff-profile/) (Project Lead), California Digital Library | ||
- [Maria Gould](https://cdlib.org/contact/staff_directory/maria-gould-staff-profile/) (ROR Director), California Digital Library | ||
- [John Chodacki](https://cdlib.org/contact/staff_directory/john-chodacki-staff-profile/), California Digital Library | ||
- [Ed Pentz](https://www.crossref.org/people/ed-pentz/), Crossref | ||
- [Matt Buys](https://datacite.org/team.html), DataCite | ||
|
@@ -88,9 +88,9 @@ Email Amanda at [[email protected]](mailto:[email protected]) or [book a 30-minute mee | |
|
||
Liz [joined the ROR team in late 2020](https://blog.datacite.org/working-at-the-intersection-of-people-and-technology/) as our first Adoption Manager and has developed extensive guidance to support ROR users and integrators, before [stepping into the role of ROR Technical Lead in February 2022](/blog/2022-02-14-new-year-at-ror/#changes-on-the-ror-team). Previously, Liz was based at ORCID for 6 years, where she held roles ranging from member support to technical lead. A librarian by training and a software developer by necessity, Liz thrives at the intersection of people, processes and technology. She loves understanding the human and technological aspects of systems and developing solutions that suit both the people and the machines. | ||
|
||
#### Maria Gould, Project Lead | ||
#### Maria Gould, Director | ||
|
||
Maria [joined ROR in November 2018](https://cdlib.org/cdlinfo/2018/11/14/maria-gould-joins-cdl-as-uc3-product-manager/) and led the team that launched the minimum viable registry (MVR) prototype at PIDapalooza in 2019. As project lead, Maria is responsible for coordinating ROR operations and developing ROR's strategic vision. Maria is based at California Digital Library, where she leads the University of California Curation Center (UC3)'s portfolio of persistent identifier services, including ROR. Prior to joining ROR and CDL, Maria was a scholarly communication librarian at UC Berkeley and led documentation and training activities at PLOS. | ||
Maria [joined ROR in November 2018](https://cdlib.org/cdlinfo/2018/11/14/maria-gould-joins-cdl-as-uc3-product-manager/) and led the team that launched the minimum viable registry (MVR) prototype at PIDapalooza in 2019. As director, Maria is responsible for coordinating ROR operations and developing ROR's strategic vision. Maria is based at California Digital Library, where she leads the University of California Curation Center (UC3)'s portfolio of persistent identifier services, including ROR. Prior to joining ROR and CDL, Maria was a scholarly communication librarian at UC Berkeley and led documentation and training activities at PLOS. | ||
|
||
#### Alumni and affiliates | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -22,7 +22,7 @@ ROR, the Research Organization Registry, is operated as a collaborative initiati | |
|
||
### **How is ROR funded?** | ||
|
||
During its first few years, ROR relied on a mixed funding model that included in-kind support from the three ROR governing organizations, contributions from supporting organizations, and grants. ROR is [transitioning to a resourcing model](/blog/2022-10-10-strengthening-sustainability) where all staffing and core expenses will be supported entirely by the three ROR governing organizations. Additional funding from community supporters or future grants will be used to offset operating costs and support time-limited projects. [Learn more about ROR’s business model](/about#business-model). | ||
During its first few years, ROR relied on a mixed funding model that included in-kind support from the three ROR governing organizations, contributions from supporting organizations, and grants. In 2022, ROR began [transitioning to a resourcing model](/blog/2022-10-10-strengthening-sustainability) where all staffing and core expenses will be supported entirely by the three ROR governing organizations. Additional funding from community supporters or future grants will be used to offset operating costs and support time-limited projects. [Learn more about ROR’s business model](/about#business-model). | ||
|
||
*** | ||
|
||
|
@@ -103,7 +103,7 @@ Yes, ROR metadata includes both parent-child organizational hierarchies and late | |
|
||
### **Why doesn't ROR include university departments?** | ||
|
||
ROR is focused on addressing the fundamental affiliation use case and increasing interoperability with other systems, and therefore it is not focused on capturing all subdivisions of a given organization, such as a university’s academic departments. The more granular the registry, the less suited it is to address the use case of tracking outputs at the institutional level. The "high-level" institutional information in ROR is also more stable than departmental information and is therefore better suited for persistence. ROR concentrates on maintaining inclusive global coverage of research organizations rather than on capturing the internal structure of organizations, and this approach keeps ROR easy to use. Additionally, some high-level sub-units of organizations are in scope for ROR, such as research institutes. Because ROR's code and data are entirely open, ROR users are free to build upon it in their local integrations to add their own department-level taxonomies. | ||
ROR is focused on solving the problem of connecting research outputs to research organizations while remaining easy to use, and therefore it is not focused on capturing all subdivisions of a given organization such as a university’s schools or departments. ROR does support organizational hierarchy, and units such as research institutes and laboratories are in scope for ROR. The more granular the registry, however, the less suited it is to address the key use case of linking research outputs to research organizations and the more difficult it is to implement and maintain. University departments in particular often emerge, close, combine, and change: the "high-level" institutional information in ROR is more stable and is therefore better suited for persistence. ROR concentrates on maintaining broad, inclusive global coverage of research organizations rather than on capturing the internal structure of particular organizations. ROR might extend its scope in the future, but meanwhile, because ROR's code and data are entirely open, ROR users are free to build upon it in their local integrations to add their own school- and department-level taxonomies. | ||
|
||
*** | ||
|
||
|
@@ -225,7 +225,7 @@ Contact [[email protected]](mailto:[email protected]) if you have a list of organi | |
|
||
### **I submitted a curation request to ROR. How can I track it?** | ||
|
||
After a request is submitted via the feedback form, an issue will be created in the [ror-updates Github repository](https://github.com/ror-community/ror-updates/issues) and added to a [project board](https://github.com/ror-community/ror-updates/projects/1). You can track the status of your request by following the repository and by signing up as a watcher on the issue associated with your request. | ||
After a request is submitted via the feedback form, an issue will be created in the [ror-updates Github repository](https://github.com/ror-community/ror-updates/issues) and added to a [project board](https://github.com/ror-community/ror-updates/projects/1). You will receive an email notification with a link to the Github issue associated with your request. You can track the status of the request by following this issue and subscribing to issue notifications. | ||
|
||
*** | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -223,3 +223,9 @@ And then, you know, really what we are looking for, just like many other institu | |
### {{< figure src="/img/amanda-sq-100.png" class="round-figure" alt="Amanda French" >}} Amanda French | ||
|
||
Great! This was tremendously interesting -- thanks for telling us all about your ROR integration. | ||
|
||
{{% callout color="green" icon="no-icon" %}} | ||
|
||
Questions? Want to be featured in a ROR case study? Contact <[email protected]>. | ||
|
||
{{% /callout %}} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -373,6 +373,8 @@ Oh, I should mention that part of the reason we're able to work so effectively w | |
|
||
Well, thank you so much for speaking to me. It was lovely to talk to you. | ||
|
||
{{% callout color="dark-grey" icon="no-icon" %}} | ||
Do you have a comment on or question about this post? Email [[email protected]](mailto:[email protected]) or [get involved](https://ror.readme.io/docs/get-involved) with the ROR community. | ||
{{% callout color="green" icon="no-icon" %}} | ||
|
||
Questions? Want to be featured in a ROR case study? Contact <[email protected]>. | ||
|
||
{{% /callout %}} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -182,4 +182,10 @@ I don't know if I have anything else. I'm a big supporter of ROR, and I've been | |
Great! That's great to hear. Thank you so much, Tom. | ||
|
||
### {{< figure src="/img/blog/caltech/tom-morrell.jpg" class="round-figure" alt="Tom Morrell" >}} Tom Morrell | ||
Well, thank you. It's been great to chat. | ||
Well, thank you. It's been great to chat. | ||
|
||
{{% callout color="green" icon="no-icon" %}} | ||
|
||
Questions? Want to be featured in a ROR case study? Contact <[email protected]>. | ||
|
||
{{% /callout %}} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -134,14 +134,6 @@ Thanks for telling us all about your work with ROR, Rob and Emily. | |
|
||
{{% callout color="green" icon="no-icon" %}} | ||
|
||
- [Download the slides](/documents/2022-12-08-ROR-RUP-Silverchair-Slides.pdf) as a PDF | ||
|
||
- [Contact Rob O'Donnell,](mailto:[email protected]) Senior Director of Publishing, Rockefeller University Press | ||
|
||
- [Contact Emily Hazzard](mailto:[email protected]), Product Operations Analyst, Silverchair | ||
|
||
- [Contact Amanda French](mailto:[email protected]), ROR Technical Community Manager | ||
|
||
- [Register for an upcoming ROR Community Call](/events) to hear about integrations like these and more. | ||
[Download the slides](/documents/2022-12-08-ROR-RUP-Silverchair-Slides.pdf) as a PDF. Questions? Want to be featured in a ROR case study? Contact <[email protected]>. | ||
|
||
{{% /callout %}} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -271,8 +271,6 @@ I appreciate your time. Thanks for involving me. Happy to be doing this for ROR. | |
|
||
{{% callout color="green" icon="no-icon" %}} | ||
|
||
- [Contact Cory Schires](mailto:[email protected]), Co-founder and CTO, Scholastica | ||
- [Contact Amanda French](mailto:[email protected]), ROR Technical Community Manager | ||
- [Register for an upcoming ROR Community Call](/events) to hear about integrations like these and more. | ||
Questions? Want to be featured in a ROR case study? Contact <[email protected]>. | ||
|
||
{{% /callout %}} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -369,5 +369,8 @@ Great. Well, thank you so much again for doing this with us, Andy. | |
|
||
Thank you for the opportunity. | ||
|
||
{{% callout color="green" icon="no-icon" %}} | ||
|
||
Questions? Want to be featured in a ROR case study? Contact <[email protected]>. | ||
|
||
{{% /callout %}} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -342,4 +342,6 @@ My pleasure. Thanks for your time. | |
|
||
See also the [press release](https://www.eurekalert.org/news-releases/984137) about Europe PMC's incorporation of ROR into its Grant Finder. Contact <[email protected]> with any questions. | ||
|
||
Questions? Want to be featured in a ROR case study? Contact <[email protected]>. | ||
|
||
{{% /callout %}} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.