-
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.
- Loading branch information
1 parent
8b6f6f2
commit aebfce1
Showing
5 changed files
with
11 additions
and
14 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). | ||
|
||
*** | ||
|
||
|
@@ -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
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 |
---|---|---|
|
@@ -17,7 +17,7 @@ If you find content on the ROR website, Github site, blog, or social media chann | |
|
||
## Website, Github, Blog, and Services | ||
|
||
ROR operates a website at <https://ror.org>, maintains code on a Github site at <https://www.github.com/ror-community>, maintains documentation on a Readme.io site at <https://ror.readme.io>, publishes blog posts at <https://ror.org/blog>, and manages support requests via email at <[email protected]>. It is ROR's policy to respect your privacy regarding any information we may collect while operating these sites and services. If you have questions about deleting or correcting any personal data you find on these sites please contact <[email protected]>. | ||
ROR operates a website at <https://ror.org>, maintains code on a Github site at <https://www.github.com/ror-community>, maintains documentation on a Readme.io site at <https://ror.readme.io>, publishes blog posts at <https://ror.org/blog>, and manages support requests via email at <[email protected]> and <[email protected]>. It is ROR's policy to respect your privacy regarding any information we may collect while operating these sites and services. If you have questions about deleting or correcting any personal data you find on these sites please contact <[email protected]>. | ||
|
||
## Site Visitors | ||
|
||
|
@@ -39,15 +39,11 @@ ROR provides documentation and support guidance on a Readme.io site (<https://ro | |
|
||
## Metadata and Identifiers | ||
|
||
ROR provides a registry of unique identifiers for research organizations and associated metadata about these organizations. All of the metadata and Identifiers registered with ROR are made available for use and reuse without restriction and under a CC0 license through our public APIs, search interfaces, and dataset downloads from Figshare and Zenodo. We are open and transparent about the use of our identifiers and metadata. | ||
ROR provides a registry of unique identifiers for research organizations and associated metadata about these organizations. All of the metadata and identifiers registered with ROR are made available for use and reuse without restriction and under a CC0 license through our public APIs, search interfaces, and dataset downloads. We are open and transparent about the use of our identifiers and metadata. | ||
|
||
## ROR Support Queries | ||
|
||
Help and support queries are handled via email to <[email protected]>. Any details provided during a support conversation are kept private. From time to time ROR may add your email to an appropriate mailing list for additional information. Individuals may remove themselves from mailings by following the unsubscribe link provided in messages or by contacting <[email protected]>. | ||
|
||
## Comments on the ROR Blog | ||
|
||
Readers of the [ROR blog](https://ror.org/blog) can submit comments on each post. ROR uses a platform called [Disqus](https://disqus.com/) to enable comments on the blog. Users can control their privacy settings with a Disqus account. | ||
Help and support queries are handled via email to <[email protected]> and <[email protected]>. Any details provided during a support conversation are kept private. From time to time ROR may add your email to an appropriate mailing list for additional information. Individuals may remove themselves from mailings by following the unsubscribe link provided in messages or by contacting <[email protected]>. | ||
|
||
## Email Communications | ||
|
||
|
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