all changes of a graph must be logged, e.g. create_graph(), add_n_nodes(), add_edge(), delete_node(), combine_graphs(), ...
we will use a simple text file for this. The log could look like this:
it must contain:
a log entry identifier, e.g. "# Log 1"
in the future we could add the option to remove entries from the logging, e.g. "revert all steps before '# Log xy'"
a timestamp
the userId of the person who changed the graph
the function that was applied and the parameters that were used
in essence, based on the logging, a graph must be reproducible otherwise reverting steps will not be possible
@f-lukas Let us check above points if there is something missing before we start to work on this task.
Following points from the task list are related and updated with the above description:
This instance file can be saved, loaded, and edited. A log is kept of any change, including the identification of the users who made the edits and the time when edits were made.
create_graph(), add_n_nodes(), add_edge(), delete_node(), combine_graphs(), ...log entry identifier, e.g. "# Log 1"timestampuserIdof the person who changed the graph@f-lukas Let us check above points if there is something missing before we start to work on this task.
Following points from the task list are related and updated with the above description: