however, during development it is possible to change the format to our needs
[x] export button
Note: In the future we will have a second export button, called e.g. "Export with signature", that will add a signature to the .json just before the download
Following points from the task list are related and updated with the above description:
User can create and share a template json file, where this defines the elements to be included (see family example below).
This template json file consists of which network elements can be used and which metadata is associated to each. Users load one of these json files and can then start defining their relational structure. For instance, a json file may be used to link family relationships (metadata could be name of each person, date of birth, etc.) and there could be two main elements (male or female).
Based on the template json file users can then describe an actual network which is saved as a separate json file (instance). Continuing with the family example, users would enter the different individuals (their metadata) and define their relationships (represented using arrows). A visual representation of this would look something like a family tree.
.json
file.json
(check below or https://github.com/Pandora-IsoMemo/TraceR/issues/1#issue-1963851137)Note: In the future we will have a second export button, called e.g. "Export with signature", that will add a signature to the
.json
just before the downloadFollowing points from the task list are related and updated with the above description: