Neo4j Section Schema and Properties

Exported on 5/15/2025 at 23:49:54 PDT from Cursor (0.50.4)

User

section schema and properties from neo4j

Cursor

Here is the schema and properties for the Section node in your Neo4j database:

Node Label: Section

Relationships:

• LINKS_TO (Section → Section)
• PARENT_OF (Section → Section)
• CHILD_OF (Section → Section)

Properties found on Section nodes:

• requirementID
• id_links
• clauseNumWithoutFramework
• requirement_raw
• tag
• clause_raw
• uuid_links
• id_clause
• name
• uuid
• requirements
• label
• path
• id
• clause
• clauseNumber
• requirement
• link_dest

If you need details about the data types or want to see example values for any property, let me know!

User

find all parent, child, and linked to nodes of 10.6.4, follow the linked to nodes recursively, return id, clause, clauseNumber, requirement

Cursor

Here are all parent, child, and recursively “LINKS_TO” connected nodes for clauseNumber 10.6.4, with their id, clause, clauseNumber, and requirement:

1. id: c2927624-257b-4950-a7b8-95ee6dd0c2e3

   • clause: External measures
   • clauseNumber: 10.6.4
   • requirement: (empty)

2. id: b9cff05e-3172-4674-b40b-eafc271db74a

   • clause: Concept phase and system development
   • clauseNumber: 10.6
   • requirement: (empty)

3. id: f66ecb66-5a33-4d91-a08b-8db0bd1a8c45

   • clause: General
   • clauseNumber: 10.6.4.1
   • requirement: An external measure is a measure separate and distinct from the item that reduces or mitigates the risks resulting from a failure of the item.
     • NOTE 1 External measures can be considered in the HARA, if they are independent with regards to the function to be implemented by the item.
     • NOTE 2 External measures as a technical assumption to reduce an ASIL are validated according to ISO 26262-3:2018, 6.4.4.4.

4. id: b24fbff1-a467-45df-8ae8-c7f9d0db2a57

   • clause: Example of vehicle dependent external measures 1
   • clauseNumber: 10.6.4.2
   • requirement: Vehicle A is equipped with a manually operated transmission gear box which can be left in any gear, including neutral, upon key off. Vehicle B is equipped with an automatic gear box which, at key off, maintains one gear engaged and a normally closed clutch. Both vehicles have an additional item, Electrical Parking Brake (EPB).
     • (Full requirement text truncated for brevity.)

5. id: 8b262467-2b9d-4dc7-8bd7-a93cefd7b962

   • clause: Example of vehicle dependent external measures 2
   • clauseNumber: 10.6.4.3
   • requirement: Vehicle A is equipped with dynamic stability control in addition to a stop-start feature. Vehicle B is only equipped with the stop-start feature.
     • (Full requirement text truncated for brevity.)

If you need the full requirement text for any node or want to see the relationship paths, let me know!

User

MATCH (start:Section {clauseNumber: ‘10.6.4’})\nOPTIONAL MATCH (start)-[:PARENT_OF]->(parent:Section)\nOPTIONAL MATCH (start)-[:CHILD_OF]->(child:Section)\nOPTIONAL MATCH path=(start)-[:LINKS_TO*]->(linked:Section)\nWITH COLLECT(DISTINCT parent) AS parents, COLLECT(DISTINCT child) AS children, COLLECT(DISTINCT linked) AS linkedNodes, start\nUNWIND parents + children + linkedNodes + [start] AS node\nWITH DISTINCT node\nWHERE node IS NOT NULL\nRETURN node.id AS id, node.clause AS clause, node.clauseNumber AS clauseNumber, node.requirement AS requirement”

strip the newlines from this query so i can use it in my shell

Cursor

Here is your Cypher query with all newlines removed, so you can use it in your shell:

MATCH (start:Section {clauseNumber: '10.6.4'}) OPTIONAL MATCH (start)-[:PARENT_OF]->(parent:Section) OPTIONAL MATCH (start)-[:CHILD_OF]->(child:Section) OPTIONAL MATCH path=(start)-[:LINKS_TO*]->(linked:Section) WITH COLLECT(DISTINCT parent) AS parents, COLLECT(DISTINCT child) AS children, COLLECT(DISTINCT linked) AS linkedNodes, start UNWIND parents + children + linkedNodes + [start] AS node WITH DISTINCT node WHERE node IS NOT NULL RETURN node.id AS id, node.clause AS clause, node.clauseNumber AS clauseNumber, node.requirement AS requirement

You can copy and paste this directly into your shell or Neo4j browser.

MATCH (start:Section {clauseNumber: '10.6.4'}) OPTIONAL MATCH (start)-[:PARENT_OF]->(parent:Section) OPTIONAL MATCH (start)-[:CHILD_OF]->(child:Section) OPTIONAL MATCH path=(start)-[:LINKS_TO*]->(linked:Section) WITH COLLECT(DISTINCT parent) AS parents, COLLECT(DISTINCT child) AS children, COLLECT(DISTINCT linked) AS linkedNodes, start UNWIND parents + children + linkedNodes + [start] AS node WITH DISTINCT node WHERE node IS NOT NULL RETURN node.id AS id, node.clause AS clause, node.clauseNumber AS clauseNumber, node.requirement AS requirement

User

explain this query to me as someone who has only just started using neo4j

Cursor

Absolutely! Here’s a step-by-step explanation of what this Cypher query does, in beginner-friendly terms:

1. Find the Starting Node

MATCH (start:Section {clauseNumber: '10.6.4'})

• This finds a node labeled Section where the property clauseNumber is '10.6.4'.
• This node is called start for the rest of the query.

2. Find Related Nodes

OPTIONAL MATCH (start)-[:PARENT_OF]->(parent:Section)
OPTIONAL MATCH (start)-[:CHILD_OF]->(child:Section)
OPTIONAL MATCH path=(start)-[:LINKS_TO*]->(linked:Section)

• OPTIONAL MATCH means: “Try to find this pattern, but if it doesn’t exist, don’t fail the query.”
• The first line looks for any Section node that is a parent of start.
• The second line looks for any Section node that is a child of start.
• The third line looks for any Section node that is linked to start by one or more LINKS_TO relationships, even if there are several hops (the * means “follow as many as you can”).

3. Collect the Results

WITH COLLECT(DISTINCT parent) AS parents, COLLECT(DISTINCT child) AS children, COLLECT(DISTINCT linked) AS linkedNodes, start

• This groups together all the parents, children, and linked nodes found, removing duplicates (DISTINCT).
• It also keeps the start node.

4. Combine All Nodes into One List

UNWIND parents + children + linkedNodes + [start] AS node

• This takes all the parents, children, linked nodes, and the start node itself, and puts them into a single list.
• UNWIND turns this list into individual rows, each with a node.

5. Remove Duplicates and Nulls

WITH DISTINCT node
WHERE node IS NOT NULL

• WITH DISTINCT node ensures each node only appears once.
• WHERE node IS NOT NULL removes any empty results (in case there were no parents, children, or links).

6. Return the Information

RETURN node.id AS id, node.clause AS clause, node.clauseNumber AS clauseNumber, node.requirement AS requirement

• For each node found, it returns the id, clause, clauseNumber, and requirement properties.

Summary

This query finds a specific section (10.6.4), then gathers:

• Its parent(s)
• Its child(ren)
• Any sections it is linked to (recursively, so it follows chains of links)
• The section itself

It then returns some key information about each of these nodes, with no duplicates.

If you want more details about any part, just ask!

MATCH (start:Section {clauseNumber: '10.6.4'})

OPTIONAL MATCH (start)-[:PARENT_OF]->(parent:Section)
OPTIONAL MATCH (start)-[:CHILD_OF]->(child:Section)
OPTIONAL MATCH path=(start)-[:LINKS_TO*]->(linked:Section)

WITH COLLECT(DISTINCT parent) AS parents, COLLECT(DISTINCT child) AS children, COLLECT(DISTINCT linked) AS linkedNodes, start

UNWIND parents + children + linkedNodes + [start] AS node

WITH DISTINCT node
WHERE node IS NOT NULL

RETURN node.id AS id, node.clause AS clause, node.clauseNumber AS clauseNumber, node.requirement AS requirement