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
The sample data looks like it was based on some real data at one point. It would be good to refresh this data so that this is no longer the case.
It would also be an oppurtunity to tweak the structure of the sample data, so that it better mirrors present data - i.e. contains multiple NGIs (one of which isn't under a project) like below (the sites should also have dummy services.):
P1
/ \
N1 N2 N3
/ \ | |
S1 S2 S3 S4
Users should be given unique, but still dummy, emails so they are easier to differentiate (i.e. in dry runs of scripts that generate emails).
There exists some "simple sample data" which would be a good starting point to expand and replace the existing sample data.
As a follow on, the example API output used in the docs should be updated to reflect the new sample data, see: GOCDB/GOCDB.github.io#12.
The text was updated successfully, but these errors were encountered:
The sample data looks like it was based on some real data at one point. It would be good to refresh this data so that this is no longer the case.
It would also be an oppurtunity to tweak the structure of the sample data, so that it better mirrors present data - i.e. contains multiple NGIs (one of which isn't under a project) like below (the sites should also have dummy services.):
Users should be given unique, but still dummy, emails so they are easier to differentiate (i.e. in dry runs of scripts that generate emails).
There exists some "simple sample data" which would be a good starting point to expand and replace the existing sample data.
As a follow on, the example API output used in the docs should be updated to reflect the new sample data, see: GOCDB/GOCDB.github.io#12.
The text was updated successfully, but these errors were encountered: