You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 5, 2024. It is now read-only.
The main source for graph data will probably come from tabular data of some form. We will always need a table describing the relations between nodes (edges), in addition, it's possible to have a table that describes attributes of each node (with the node id being the index that is used in the edges table).
Steps
onboard edges file
Copy a file containing tabular edges data (most likely csv, but possibly also json, yaml, ...) from the local file system (or possibly remote/url) into the kiara data store.
Inputs:
file_path (type: string)
Outputs:
file_item (type: file, qualities: tabular, at least 2 columns: 'source'/'target', optionally edge attributes like weight)
onboard nodes file (optional)
Copy a file containing tabular node data (most likely csv, but possibly also json, yaml, ...) from the local file system (or possibly remote/url) into the kiara data store.
Inputs:
file_path (type: string)
Outputs:
file_item (type: file, qualties: tabular, one column referring to the node id, other columns describing attributes for each node)
create network graph item
Read the onboarded file(s) from step 1 (and possibly 2) and parse their content into a database item.
Inputs:
edges file_item: (type: file, from step 1)
nodes file_item: (type: file, optional, from step 2)
Outputs:
network_graph (type: network_graph, stored as sqlite-db-file, qualities: two tables 'edges'/'nodes' -- 'nodes' can be empty)
preprocessingRelated to modules or workflows that do some sort of pre-processing.
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Description
The main source for graph data will probably come from tabular data of some form. We will always need a table describing the relations between nodes (edges), in addition, it's possible to have a table that describes attributes of each node (with the node id being the index that is used in the edges table).
Steps
Copy a file containing tabular edges data (most likely csv, but possibly also json, yaml, ...) from the local file system (or possibly remote/url) into the kiara data store.
Inputs:
Outputs:
Copy a file containing tabular node data (most likely csv, but possibly also json, yaml, ...) from the local file system (or possibly remote/url) into the kiara data store.
Inputs:
Outputs:
Read the onboarded file(s) from step 1 (and possibly 2) and parse their content into a database item.
Inputs:
Outputs:
Beta Was this translation helpful? Give feedback.
All reactions