Adam, Your approach will work (2 branches, each with a card accessed via the same menu). I noticed that your nodes are concepts, so an alternate modeling approach would be to use concept list nodes for both the Archaeological Site Type and Culture. This would allow you to present both nodes on a single card and support one or more values for each node.
-Dennis On Tuesday, October 3, 2017 at 8:24:39 AM UTC-7, Adam Cox wrote: > > Hello all, I'd like to clarify something: > > I am making a simple branch that is meant to record Archaeological Site > Type and Culture. These attributes should not be tied together (there can > be any number of each one), however, I would like them to both be in the > same menu for those who are entering data. It seems that if I include both > attributes in a single branch, my only option is to make "sub-cards" from > them, otherwise they are stored as a pair. > > "Sub-cards" aren't desirable, as each one would have only attribute in it. > > I'm thinking that my best course of action is to split these into separate > branches, each with one node, and then include the card from each branch > into the same menu. Is this true? I don't think there is any further way to > separate them from being saved together but also keep them on the same > screen. > > Thanks, > Adam > -- -- To post, send email to [email protected]. To unsubscribe, send email to [email protected]. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en --- You received this message because you are subscribed to the Google Groups "Arches Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
