Understand relationship aggregation

You've learned how to use existing relationshipA named, directed connection between two nodes. Every relationship has a type, a start node and an end node. propertiesA named value stored on a node or a relationship. as weights in your projectionsAn in-memory copy of part of your database that graph algorithms run against. You choose which nodes and relationships it holds.. You have also learned how to project undirected relationshipsA relationship with no direction. Neo4j GDS represents them as parallel relationships in opposite directions..

But what if you need to create weights by combining multiple relationships?