# Inconsistency between organization name used for settings files and for macOS bundle identifier

**URL:** <https://discourse.slicer.org/t/inconsistency-between-organization-name-used-for-settings-files-and-for-macos-bundle-identifier/26547>\
**Category:** Development\
**Created:** [December 2, 2022, 7:22am UTC](https://discourse.slicer.org/t/inconsistency-between-organization-name-used-for-settings-files-and-for-macos-bundle-identifier/26547 "2022-12-02T07:22:24Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [December 2, 2022, 7:22am UTC](https://discourse.slicer.org/t/inconsistency-between-organization-name-used-for-settings-files-and-for-macos-bundle-identifier/26547/1 "2022-12-02T07:22:24Z")

</div>

There are inconsistencies between the organization associated with the [settings file location](https://slicer.readthedocs.io/en/5.2/user_guide/settings.html#settings-file-location) and the value set as macOS bundle identifier.

| Settings file location | macOS bundle identifier |
| --- | --- |
| ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/e/d/ed360beb0c0ea77af0bf6a4c9dd24bc6158ed508.png) | |

These correspond to the default values associated with the following variables:

| CMake variable | Default value |
| --- | --- |
| `Slicer_ORGANIZATION_NAME` | `NA-MIC`\[1\] |
| `Slicer_ORGANIZATION_DOMAIN` | `www.na-mic.org` \[2\] |
| `Slicer_MACOSX_BUNDLE_GUI_IDENTIFIER` | `org.slicer.slicer`\[3\] |

**Question:** Should we update the value of `Slicer_ORGANIZATION_NAME` and `Slicer_ORGANIZATION_DOMAIN` to respectively be `Slicer` and `www.slicer.org` (`slicer.org`) ?

* * *

1. [https://github.com/Slicer/Slicer/blob/v5.2.1/CMake/SlicerApplicationOptions.cmake#L67](https://github.com/Slicer/Slicer/blob/v5.2.1/CMake/SlicerApplicationOptions.cmake#L67) 

2. [https://github.com/Slicer/Slicer/blob/v5.2.1/CMake/SlicerApplicationOptions.cmake#L60](https://github.com/Slicer/Slicer/blob/v5.2.1/CMake/SlicerApplicationOptions.cmake#L60) 

3. [https://github.com/Slicer/Slicer/blob/v5.2.1/CMake/SlicerApplicationOptions.cmake#L126](https://github.com/Slicer/Slicer/blob/v5.2.1/CMake/SlicerApplicationOptions.cmake#L126)

---

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [December 2, 2022, 12:42pm UTC](https://discourse.slicer.org/t/inconsistency-between-organization-name-used-for-settings-files-and-for-macos-bundle-identifier/26547/2 "2022-12-02T12:42:53Z")

</div>

Yes, using Slicer as the organization makes sense. I was recently helping a user find the settings file in AppData and they had trouble finding it because it wasn’t immediately obvious that Slicer was under a NA-MIC organization directory.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [December 3, 2022, 5:15am UTC](https://discourse.slicer.org/t/inconsistency-between-organization-name-used-for-settings-files-and-for-macos-bundle-identifier/26547/3 "2022-12-03T05:15:06Z")

</div>

I think the only remaining activity of the NA-MIC organization is the Project Week ([https://projectweek.na-mic.org/](https://projectweek.na-mic.org/)), but I think even that is only a label that is attached to the group of organizers. So, it would be probably more accurate to say that today Slicer is developed by the Slicer community ([www.slicer.org](http://www.slicer.org)) and not the NA-MIC community ([www.na-mic.org](http://www.na-mic.org)) and we could reflect that by changing the organization name/domain on all platforms.

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [December 3, 2022, 3:59pm UTC](https://discourse.slicer.org/t/inconsistency-between-organization-name-used-for-settings-files-and-for-macos-bundle-identifier/26547/4 "2022-12-03T15:59:26Z")

</div>

Yes, I think that using Slicer consistently would be more logical. It’s always been weird that the config paths on mac and linux aren’t consistent so clearing that up too would be nice.

---

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [December 23, 2022, 5:45pm UTC](https://discourse.slicer.org/t/inconsistency-between-organization-name-used-for-settings-files-and-for-macos-bundle-identifier/26547/5 "2022-12-23T17:45:39Z")

</div>

To follow up on this:

> <https://github.com/Slicer/Slicer/pull/6750>
>
> See discussion at https://discourse.slicer.org/t/inconsistency-between-organizat…ion-name-used-for-settings-files-and-for-macos-bundle-identifier/26547

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [August 22, 2023, 2:02pm UTC](https://discourse.slicer.org/t/inconsistency-between-organization-name-used-for-settings-files-and-for-macos-bundle-identifier/26547/6 "2023-08-22T14:02:49Z")

</div>

For completeness, the organization name and domain were ultimately changed from `Slicer` to `slicer.org`.

> <https://github.com/Slicer/Slicer/pull/6879>
>
> Commit https://github.com/Slicer/Slicer/commit/b0b9be57cb7d1a1e462143ec74e3d37d2…71d114d modified the organization name to Slicer from NA-MIC, which caused a name clash with the Slicer executable.
> 
> This commit changes the organization name to slicer.org. The final decision on the used organization name has not been made yet, this commit is a quick fix to resolve a blocking issue.
> 
> see https://github.com/Slicer/Slicer/issues/6878
> 
> We also change the organization domain name from www.slicer.org to slicer.org for consistency.