Skip to content
This repository has been archived by the owner on Jul 25, 2018. It is now read-only.

Rework Relationship Database Structure #39

Closed
Henni opened this issue Mar 29, 2017 · 6 comments · Fixed by #55
Closed

Rework Relationship Database Structure #39

Henni opened this issue Mar 29, 2017 · 6 comments · Fixed by #55

Comments

@Henni
Copy link
Contributor

Henni commented Mar 29, 2017

The outcome of the meeting from @MusicConnectionMachine/group-3 and @MusicConnectionMachine/group-4

relation-schema
Blue: Planned in #28
Green: Stuff from other groups, which might be already there
Red: New stuff decided in the meeting

@simonzachau
Copy link
Contributor

This is our board draft, @SANDR00 is working on the digital version.
img_1558

@Sandr0x00
Copy link

@kordianbruck @sacdallago
Could you please give us some short feedback on what you think about this schema?

@Sandr0x00
Copy link

@kordianbruck @sacdallago
So we will just implement this now.

@Henni
Copy link
Contributor Author

Henni commented Mar 29, 2017

@vviro we would also like to hear your thoughts on this.
We integrated the possibility to store every relationship we detect even if we can't categorize it. This is done by introducing rel_str, subj_str and obj_str so that we can store a relationship even if we aren't able to set a subj_id or obj_id.

RBirkeland added a commit to RBirkeland/api that referenced this issue Mar 29, 2017
Updated to the new model structure as MusicConnectionMachine#39
@kordianbruck
Copy link
Contributor

@SANDR00 can't see anything too wrong with that - proceed

@Sandr0x00
Copy link

Just added the timeline table from #22.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants