ror-community / ror-updates

Central tracking for updates to ROR
51 stars 8 forks source link

Modify the information in an existing ROR record: Medical University of Vienna https://ror.org/05n3x4p02 #9083

Closed ror-curator-bot closed 6 months ago

ror-curator-bot commented 7 months ago

Summary of request: Modify the information in an existing ROR record

Update record: Name of organization: Medical University of Vienna ROR ID: https://ror.org/05n3x4p02 Which part of the record needs to be changed? Something else Description of change: Dear ROR team, our rectorate would like the following to be amended about this entry:

Thank you very much ahead for your efforts and best wishes to the entire ROR team, Elise

Merge/split/deprecate records: Organizations affected by this change: ROR ID(s) of organization(s) affected by this change: How should the record(s) be changed?

Add record: Name of organization: Website: Link to publications: Organization type: Wikipedia page: Wikidata ID: ISNI ID: GRID ID: Crossref Funder ID: Aliases: Labels: Acronym/abbreviation: Related organizations: City: Country: Geonames ID: Year established: How will a ROR ID for this organization be used?

Other information about this request:

adambuttrick commented 7 months ago

Review of relationships, relative to requested changes:

adambuttrick commented 6 months ago

All changes stemming from review now reflected with issues.

adambuttrick commented 6 months ago

Updated in release v1.43.

errortryagain commented 5 months ago

Hi Adam,

Thank you very much for reviewing our request and for the updates to our ROR record.

Following up on this, I would like to add a few notes on this.

The request derived from a communication we had with a publisher that commendably uses ROR for their submission process and due to a relationship in ROR between our organization and another falsely assumed we would be in charge of paying an author's APCs. It thus drew our institution's attention to our ROR record. A task force was formed and our Vice Rector for Research and Innovation, Michaela Fritz, explicitly said how she wanted the relationships in ROR to be publicly displayed. Hence, my request above was in fact formulated on behalf of our Rectorate.

We have an affiliation policy in place here at Medical University of Vienna that asks for authors to prioritize MUV as top level affiliation (s. page 6). In order to enforce that, we hereby would kindly ask for Universitätsklinik für Hals-, Nasen- und Ohrenkrankheiten and Universitätsklinik für Neurologie to be withdrawn from ROR (with MUV as their successor; following this example from your documentation). These records were apparently created without knowledge of our Rectorate, who would otherwise have intervened. Since these two represent only a couple of the many clinics of our university, it is deemed counterproductive by our Rectorate to maintain these two records, when there are none for all the other clinics/departments etc.

The very same affiliation policy may also serve as proof for our "related" relationships to Max Perutz Labs and to St. Anna Children's Cancer Research Institute (s. pages 9 and 10 of the policy). Hence, please kindly add these two "related" relationships to our MUV ROR record.

As for Comprehensive Cancer Center Vienna, Complexity Science Hub Vienna and Austrian BioImaging/CMI, yes, MUV collaborates with these institutions. But then again, it also does with so many other organizations, so again, these three are not representative for all our collaborations as it were. Hence, please remove these 3 relationships from MUV's ROR record so that it is kept as streamlined as possible. This will help us e.g. in future similar communication with publishers as the one outlined above.

For the sake of completeness, the relationships to Universitätszahnklinik Wien and Vienna General Hospital are represented correctly from our perspective.

Thank you very much ahead for your support, all the best, Elise (MUV university library)

adambuttrick commented 5 months ago

@errortryagain Thank you for this additional context. We will proceed with updating as described. I've tagged the corresponding issues here.