archesproject / arches

Arches is a web platform for creating, managing, & visualizing geospatial data. Arches was inspired by the needs of the Cultural Heritage community, particularly the widespread need of organizations to build & manage cultural heritage inventories
GNU Affero General Public License v3.0
210 stars 139 forks source link

Clarify "Allow multiple Values" dependency on "Place Node in Separate Card" #11048

Open whatisgalen opened 3 weeks ago

whatisgalen commented 3 weeks ago

If you have a nodegroup, you can enable multiple values for it. If the child nodes aren't on their own nodegroups, they shouldn't have the option to "Allow multiple values". This option is disabled for the children, but I think it would be better to hide the option altogether unless a node becomes its own nodegroup. See video:

https://github.com/archesproject/arches/assets/8366985/952efdec-ebaf-4980-845a-621ee3e149d1

chiatt commented 3 weeks ago

Yeah - that can be confusing, but I don't think it should necessarily be hidden. It might be better to leave it visible, and inform the user that the node 'must be placed in a separate card'. Otherwise there is nothing to indicate that changing the cardinality is even possible.

whatisgalen commented 3 weeks ago

Otherwise there is nothing to indicate that changing the cardinality is even possible.

2 thoughts:

chiatt commented 1 week ago

What if we just indented 'Allow Multiple Values' under 'Place Node in Separate Card' so that it is clear that the multiple values is really a dependent condition of being in a separate card.

[toggle] Export via Search Results
[toggle] Place Node in Separate Card
        [toggle] Allow Multiple Values