Looks like the issue is happening since the CKAN 2.3 upgrade on catalog, it could be an issue in the upstream CKAN as well.
The issue was noticed on the MCC organization at https://catalog.data.gov/organization/mcc-gov, there was a typo in the organization name, when the organization name is corrected, the new name didn't get reflected through out the site. All the existing datasets had to be re-indexed in Solr to reflect the correct name.
Change in organization name after the datasets are harvested is a very much applicable scenario, to resolve the issue completely we need to make the necessary code updates to fetch the latest organization from database instead of Solr index, indexing all datasets in an organization when the name change happens is not realistic.
Looks like the issue is happening since the CKAN 2.3 upgrade on catalog, it could be an issue in the upstream CKAN as well.
The issue was noticed on the MCC organization at https://catalog.data.gov/organization/mcc-gov, there was a typo in the organization name, when the organization name is corrected, the new name didn't get reflected through out the site. All the existing datasets had to be re-indexed in Solr to reflect the correct name.
Change in organization name after the datasets are harvested is a very much applicable scenario, to resolve the issue completely we need to make the necessary code updates to fetch the latest organization from database instead of Solr index, indexing all datasets in an organization when the name change happens is not realistic.