# Proposal for significant ROR data model changes **URL:** \ **Category:** Content Registration\ **Tags:** metadata, schema, ror\ **Created:** [14 December 2022 18:04 UTC](https://community.crossref.org/t/proposal-for-significant-ror-data-model-changes/3189 "2022-12-14T18:04:36Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![amandafrench](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/amandafrench/32/710_2.png) [@amandafrench](https://community.crossref.org/u/amandafrench)\ **Post date:** [14 December 2022 18:04 UTC](https://community.crossref.org/t/proposal-for-significant-ror-data-model-changes/3189/1 "2022-12-14T18:04:36Z")
šŸ¦ šŸ¦ šŸ¦ As 2022 comes to a close, ROR has one last request for feedback. Youā€™ll almost certainly want to chime in on this one: our **[draft proposal of major changes to the ROR data model for schema version 2.0](https://docs.google.com/document/d/1JNDMoKmjR2y0quWXwFfoJTsIttbltJVN0l5Wddw1cIk/edit?usp=sharing)**. Comments are open until ~~February 5, 2023~~ **February 12, 2023** and we hope to release version 2.0 of the ROR schema and API in late 2023. There are **four major categories of alteration** weā€™re proposing for ROR schema 2.0: - Standardizing, clarifying, and reorganizing **name** fields (`name`, `aliases`, `labels`) - Removing repetitive, excessively granular **location** information retrieved from the GeoNames API (sub-fields in `addresses`) - Rethinking **web domain** information (`email_address`, `ip_addresses`, `links`) - Restructuring **external identifiers** to allow future addition or removal of identifier types without schema changes (sub-fields in `external_ids`) - Adding **administrative information such as created and last modified dates** Many of these are breaking changes, but we think itā€™s better to do a lot of them all at once so that future changes to the schema can be made with minimal disruption to existing ROR integrations. Read more in our blog post ā€œ[Schema Scheming: Evolving the ROR Data Model](https://ror.org/blog/2022-12-14-schema-scheming/).ā€ Let us know what you think by commenting in the [proposal Google Doc](https://docs.google.com/document/d/1JNDMoKmjR2y0quWXwFfoJTsIttbltJVN0l5Wddw1cIk/edit?usp=sharing) (so that the conversation all happens in one place) or emailing [support@ror.org](mailto:support@ror.org) before ~~February 5th, 2023~~ **February 12, 2023**. šŸ¦ šŸ¦ šŸ¦ ---
**Author:** ![marcelareinhardt](https://avatars.discourse-cdn.com/v4/letter/m/9e8a1a/32.png) [@marcelareinhardt](https://community.crossref.org/u/marcelareinhardt)\ **Post date:** [16 December 2022 16:03 UTC](https://community.crossref.org/t/proposal-for-significant-ror-data-model-changes/3189/2 "2022-12-16T16:03:58Z")
I have a doubt. Some Brazilian institutions appear with the main name in another language, such as English instead of Portuguese. In other names is the official name in the language of the institution, Portuguese, but I think that in other names the options in English should be. Example: [Research Organization Registry (ROR) Search](https://ror.org/00p9vpz11) ---
**Author:** ![amandafrench](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/amandafrench/32/710_2.png) [@amandafrench](https://community.crossref.org/u/amandafrench)\ **Post date:** [19 December 2022 16:47 UTC](https://community.crossref.org/t/proposal-for-significant-ror-data-model-changes/3189/3 "2022-12-19T16:47:17Z")
Thanks for your comment, @marcelareinhardt! It is true that most of the main names in ROR are in English, because the data ROR inherited from GRID had them that way, but we are usually happy to change the name in the `name` field to the primary language of the organizationā€™s country. You can submit a request to change ā€œFederal University of ParaĆ­baā€ to ā€œUniversidade Federal da ParaĆ­baā€ using the [curation request form](http://curation-request.ror.org/) linked to from every record. If youā€™d like to request that multiple Portuguese institutions have their main name in English, you can email [registry@ror.org](mailto:registry@ror.org) and we can begin such a project. In terms of the proposed ROR schema changes, one key suggestion weā€™re making is to add a language code to the `name` field so that we know what language the `name` is. The `labels` field (which is where we store the name of the organizations in other languages) does have language codes, but we need them in the `name` field as well precisely so that we can analyze the registry for issues like this. Right now we donā€™t have any reliable way of telling how many records in the ROR registry have the main `name` in English. ---
**Author:** ![marcelareinhardt](https://avatars.discourse-cdn.com/v4/letter/m/9e8a1a/32.png) [@marcelareinhardt](https://community.crossref.org/u/marcelareinhardt)\ **Post date:** [19 December 2022 17:03 UTC](https://community.crossref.org/t/proposal-for-significant-ror-data-model-changes/3189/4 "2022-12-19T17:03:12Z")
Thank you so much for the reply @amandafrench ! I will send suggestions. It seems really important to include the language code field. Update success! ---
**Author:** ![amandafrench](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/amandafrench/32/710_2.png) [@amandafrench](https://community.crossref.org/u/amandafrench)\ **Post date:** [7 February 2023 22:03 UTC](https://community.crossref.org/t/proposal-for-significant-ror-data-model-changes/3189/5 "2023-02-07T22:03:59Z")
Hi all! Weā€™ve extended the deadline to comment on our [proposal for major changes to the ROR metadata schema](https://docs.google.com/document/d/1JNDMoKmjR2y0quWXwFfoJTsIttbltJVN0l5Wddw1cIk/edit?usp=sharing) by a week in order to allow time to respond for those who first heard about it at the ROR annual meeting last week. Take a look at the proposals for changes to **name fields** , **location fields** , **domain fields,** and **external identifier fields** and comment by **February 12, 2023** (aka this Sunday).