-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changing database schema #48
Comments
@csala's comment:
For this, we should:
Can we adapt the changes to this schema? |
Merged
Closed in #58 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@kveerama and I discussed some changes of the DB schema:
Datarun
collectionExperiment
collection, which consists of multipleDataruns
. (We might want to restrict it such that oneExperiment
can only consist of multipleDataruns
with sameDataset
)The idea is that the first screen a user would see is the
Experiments
overview. If anExperiment
is clicked, the differentDataruns
belonging to theExperiment
are shown. Thus,Experiments
are a way of structuring multipleDataruns.
ADatarun
consists of aDataset
and aPipeline.
When aDatarun
is clicked, theDataset
itself and allEvents
andComments
belonging to theDatarun
are displayed.If anyone has additional thoughts on that, please feel free to comment.
The text was updated successfully, but these errors were encountered: