Add a new organization to ROR: Python in Heliophysics Community (PyHC)

[ror-curator-bot]

Summary of request: Add a new organization to ROR

Name of organization: Python in Heliophysics Community Website: https://heliopython.org Link to publications: https://doi.org/10.1029/2018JA025877 , https://doi.org/10.5281/zenodo.5822784 , https://doi.org/10.1016/j.asr.2022.10.006 Organization type: Other Wikipedia page: Wikidata ID: ISNI ID: GRID ID: Crossref Funder ID: Aliases Labels: Acronym/abbreviation: PyHC Related organizations: https://ror.org/0171mag52 (related) https://ror.org/01fcjzv38 (related) City: Boulder, Colorado Country: USA Geonames ID: 5574991 Year established: 2018 How will a ROR ID for this organization be used? To identify affiliations for research publications, To acknowledge research funders

Other information about this request: I'm not entirely sure if PyHC is actually "located" anywhere. I put Boulder, Colorado because that's where LASP is, the institution from which myself and PyHC's lead PI come. But PyHC has no physical building and its members are worldwide.

[adambuttrick]

Science and open source advocacy group that helps develop and further adoption of Python in the heliophysics research community. Publications provided are academic articles describing the group's work, but where all authors use another primary institutional affiliation. That being said, clearly an established group operating for several years, sponsored by NASA's Goddard Space Flight Center. We likewise have similar groups in ROR (e.g. https://ror.org/000tetj79), so I think this is fine to add.

[sapols]

@adambuttrick Will you please help me clarify the "Type of Organization" PyHC should've chosen? I picked "Nonprofit" when I filled out the form because it seemed like the most relevant option at the time. But our funding agency just pointed out to me that we are not legally a nonprofit entity (e.g. you cannot make contributions to us).

That makes me think I should've chosen "Other" instead. Do you agree?

[adambuttrick]

@sapols Other is fine in this context. I've updated the request.

[sapols]

@adambuttrick Perfect. Thank you for updating the request!

[arthurpsmith]

I'm not seeing how this will be used as a ROR id - the request states "To identify affiliations for research publications" - but nobody is using this as an affiliation now, is it expected some people will in future? Multiple people? And also "To acknowledge research funders" - this doesn't seem to be a funding body. While I understand this is an organization involved in the research community, it seems out of our normal scope.

There are surely many other "communities" like this that we don't yet have in ROR, will they all be eligible? Examples would be: pyOpenSci - https://www.pyopensci.org/ R4DS - https://www.rfordatasci.com rOpenSci - https://ropensci.org/ HEP Software Foundation - https://hepsoftwarefoundation.org

I see that these organizations are doing good things related to research software but it's not clear to me they are in scope! Moving to "needs discussion".

[sapols]

@arthurpsmith I'm happy to explain how this will be used as a ROR id. It is absolutely the case that people will use this as an affiliation in the future. We've already had a number of publications where authors wanted to list PyHC as their affiliation (e.g. this one) but ultimately did not because there was no citable way to do so. And more such publications are in the works. This has been a leading topic of conversation at recent community meetings. We first started down the path of making a DOI for PyHC via DataCite for this purpose, but DataCite's support team told us a DOI wasn't appropriate because we really need a ROR ID rather than a DOI.

PyHC isn't necessarily a funding body yet, but we have plans with NASA GSFC to start a program under which member package developers would get funding and development support from PyHC.

Additionally, PyHC is a veritable research organization itself. One area of research we're particularly active in right now is "executable papers." We're in the final stages of the review process with Frontiers in Astronomy and Space Sciences for a publication that will be the first published executable paper in heliophysics (preview here). We need this ROR ID to reliably identify PyHC as the organization that produced that work—and will need it for all future work. Another important output of our organization is our Python development standards which are used by NASA's Heliophysics division as criteria for proposal submissions. We'll use this ROR ID to unambiguously identify PyHC as the organization producing those standards. I believe these facts distinguish us from the four other "communities" you listed.

Does that help? I'm happy to provide any further details.

[adambuttrick]

For additional context, rOpenSci is used as an affiliation (https://doi.org/10.12688/f1000research.14013.2; https://doi.org/10.1109/mcse.2018.2882753; https://doi.org/10.1073/pnas.1816367116) but is funded through the NPO NumFOCUS, so the circumstances are quite similar.

[adambuttrick]

Per curation team discussion on 2022/12/06, in scope for ROR. Evidence of pending research output, connection to existing, established organization, and intent to use for multiple contributors.

[adambuttrick]

Assigned ROR ID https://ror.org/012prn105 in release v1.17.