Browse Components - Code Extractor

function node_exists

Checks if a node with a specific UID exists in a Neo4j graph database by querying for the node and returning a boolean result.

File: /tf/active/vicechatdev/CDocs/db/db_operations.py | Lines: 932-962

neo4j graph-database node-validation existence-check database-query

function create_node_with_uid

Creates a new node in a Neo4j graph database with a specified UID, label, and properties, automatically adding a creation timestamp if not provided.

File: /tf/active/vicechatdev/CDocs/db/db_operations.py | Lines: 883-930

neo4j graph-database node-creation database uid

function check_node_exists

Checks if a node with a specified label and matching properties exists in a Neo4j graph database.

File: /tf/active/vicechatdev/CDocs/db/db_operations.py | Lines: 836-881

neo4j graph-database node-validation database-query existence-check

function get_document_with_relationships

Retrieves a complete document from Neo4j graph database along with all its related entities including versions, reviews, approvals, and authors.

File: /tf/active/vicechatdev/CDocs/db/db_operations.py | Lines: 761-834

neo4j graph-database document-management relationships cypher-query

function batch_create_nodes

Creates multiple Neo4j graph database nodes in batches for improved performance, automatically generating UIDs and timestamps for each node.

File: /tf/active/vicechatdev/CDocs/db/db_operations.py | Lines: 712-759

neo4j graph-database batch-processing bulk-insert database

function execute_transaction

Executes a database transaction function within a Neo4j session, handling connection management and error logging automatically.

File: /tf/active/vicechatdev/CDocs/db/db_operations.py | Lines: 691-710

database neo4j transaction wrapper error-handling

function get_related_nodes

Retrieves nodes from a Neo4j graph database that are related to a source node identified by its UID, with optional filtering by relationship type, target node label, and relationship direction.

File: /tf/active/vicechatdev/CDocs/db/db_operations.py | Lines: 637-689

neo4j graph-database relationships traversal query

function run_query

Executes a custom Cypher query against a Neo4j database and returns the results as a list of dictionaries, handling conversion of Neo4j-specific types.

File: /tf/active/vicechatdev/CDocs/db/db_operations.py | Lines: 598-635

neo4j cypher database graph-database query-execution

function run_query_v1

Executes a Cypher query against a Neo4j database session and returns the result, with optional parameterization for safe query execution.

File: /tf/active/vicechatdev/offline_docstore_multi_vice.py | Lines: 54-72

neo4j graph-database cypher query-execution database

function get_nodes_by_label

Retrieves nodes from a Neo4j graph database by label with optional property filtering, pagination, and sorting capabilities.

File: /tf/active/vicechatdev/CDocs/db/db_operations.py | Lines: 538-596

neo4j graph-database query node-retrieval filtering

function get_node_by_uid

Retrieves a node from a Neo4j graph database by its unique identifier (UID) and returns it as a dictionary.

File: /tf/active/vicechatdev/CDocs/db/db_operations.py | Lines: 502-536

neo4j graph-database node-retrieval database-query uid-lookup

function delete_node

Deletes a node from a Neo4j graph database by its unique identifier (UID), with optional cascade deletion of connected nodes and relationships.

File: /tf/active/vicechatdev/CDocs/db/db_operations.py | Lines: 454-500

neo4j graph-database delete node-deletion cascade-delete

function update_node

Updates properties of a Neo4j graph database node identified by its unique UID, automatically adding a modification timestamp.

File: /tf/active/vicechatdev/CDocs/db/db_operations.py | Lines: 414-452

neo4j graph-database update node-update database-operation

function create_relationship

Creates a directed relationship between two Neo4j graph database nodes identified by their UIDs, with optional properties attached to the relationship.

File: /tf/active/vicechatdev/CDocs/db/db_operations.py | Lines: 360-412

neo4j graph-database relationship edge-creation cypher

function create_node_and_ensure_relationships

Creates a new node in a Neo4j graph database and establishes multiple relationships to existing nodes within a single atomic transaction.

File: /tf/active/vicechatdev/CDocs/db/db_operations.py | Lines: 258-358

neo4j graph-database node-creation relationship-management transaction

function get_next_document_number

Atomically retrieves and increments the next sequential document number for a specific document type and department combination from a Neo4j graph database.

File: /tf/active/vicechatdev/CDocs/db/db_operations.py | Lines: 190-256

document-management counter sequential-numbering neo4j graph-database

function create_node_with_relationship

Creates a new node in a Neo4j graph database and optionally establishes a relationship with an existing node in a single atomic operation.

File: /tf/active/vicechatdev/CDocs/db/db_operations.py | Lines: 98-188

neo4j graph-database node-creation relationship cypher

function _sanitize_properties

Sanitizes a dictionary of properties to ensure compatibility with Neo4j by converting complex objects to primitive types, extracting UIDs from DocUser objects, and preserving datetime objects.

File: /tf/active/vicechatdev/CDocs/db/db_operations.py | Lines: 21-39

neo4j data-sanitization type-conversion graph-database property-mapping

function get_next_status

Determines the next logical status in a document lifecycle workflow based on the current status, using either configured transitions or a predefined fallback flow.

File: /tf/active/vicechatdev/CDocs/models/document_status.py | Lines: 61-95

workflow status-management document-lifecycle state-machine business-logic

function is_published_status

Validates whether a document status string represents a published or non-editable state by checking against a predefined list of non-editable statuses.

File: /tf/active/vicechatdev/CDocs/models/document_status.py | Lines: 44-59

validation document-management status-check workflow permissions