# Unique name requirement for nodesets and sidesets
**URL:** https://discourse.paraview.org/t/unique-name-requirement-for-nodesets-and-sidesets/8171
**Category:** ParaView Support
**Created:** [October 12, 2021, 3:12pm UTC](https://discourse.paraview.org/t/unique-name-requirement-for-nodesets-and-sidesets/8171 "2021-10-12T15:12:04Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@loganharbour](https://discourse.paraview.org/u/loganharbour)
#### Post date: [October 12, 2021, 3:12pm UTC](https://discourse.paraview.org/t/unique-name-requirement-for-nodesets-and-sidesets/8171/1 "2021-10-12T15:12:05Z")
It appears that in 5.10.0-RC1, it is now required that names are unique across nodesets and sidesets:
```auto
ERROR: Duplicate names detected.
The name 'bottom' was found for both SideSet 0 and NodeSet 0.
Names must be unique over all types in a finite element model.
```
Can someone please explain the rationality for this? Within MOOSE ([GitHub - idaholab/moose: Multiphysics Object Oriented Simulation Environment](https://github.com/idaholab/moose)) we rely significantly on consistency in naming between nodesets and sidesets.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [October 12, 2021, 3:21pm UTC](https://discourse.paraview.org/t/unique-name-requirement-for-nodesets-and-sidesets/8171/2 "2021-10-12T15:21:46Z")
Hi Logan,
This restriction comes from the IOSS library. You might want to inquire over at [GitHub - gsjaardema/seacas: The Sandia Engineering Analysis Code Access System (SEACAS) is a suite of preprocessing, postprocessing, translation, and utility applications supporting finite element analysis software using the Exodus database file format.](https://github.com/gsjaardema/seacas).
---
### Author:  [@loganharbour](https://discourse.paraview.org/u/loganharbour)
#### Post date: [October 12, 2021, 3:22pm UTC](https://discourse.paraview.org/t/unique-name-requirement-for-nodesets-and-sidesets/8171/3 "2021-10-12T15:22:21Z")
Will do. Thanks for the quick response.
EDIT: See [Unique name requirement for nodesets and sidesets · Issue #251 · gsjaardema/seacas · GitHub](https://github.com/gsjaardema/seacas/issues/251) for the continued conversation.
---
### Author:  [@roystgnr](https://discourse.paraview.org/u/roystgnr)
#### Post date: [November 1, 2021, 2:44pm UTC](https://discourse.paraview.org/t/unique-name-requirement-for-nodesets-and-sidesets/8171/4 "2021-11-01T14:44:31Z")
Pinging here because last week’s response on the GitHub discussion seems too good to be true:
> You should not need any changes since the default IOSS now allows duplicate names.
It would be fantastic if this IOSS update could be incorporated into 5.10.0-RC2 when that comes out.
Right now, working around this problem after encountering it requires loading the Legacy Exodus Reader plugin, avoiding the “File / Recent” menu (which seems to encode what loader was used to attempt to load a recent file, even if the load failed!?), and selecting legacy from the popup each time we do a “File / Open” … which isn’t too hard to do, but which is a disaster to _figure out_ how to do based on nothing more than a “Duplicate names detected” error message.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [December 7, 2021, 12:09am UTC](https://discourse.paraview.org/t/unique-name-requirement-for-nodesets-and-sidesets/8171/5 "2021-12-07T00:09:33Z")
Closing the loop here. The IOSS update that supports duplicate names has been included in 5.10.0-RC2.
---
### Author:  [@loganharbour](https://discourse.paraview.org/u/loganharbour)
#### Post date: [December 7, 2021, 12:53am UTC](https://discourse.paraview.org/t/unique-name-requirement-for-nodesets-and-sidesets/8171/6 "2021-12-07T00:53:30Z")
Thanks for the quick turnaround!