Interface to Group3/4

[ShilpaGhanashyamGore]

@Henni @simonzachau @kordianbruck @sacdallago @vviro @pfent

We want to know what are the kinds of queries we should expect from your module . We can then created prepared statements to help queries return results faster . If you can give us some sample queries then we can start preparing them already . This greatly influences the design of our schema : the foreign keys and many more.

[sacdallago]

@MusicConnectionMachine/group-3 @MusicConnectionMachine/group-4 I think there is an open discussion somewhere about something similar? Makes sense to have @MusicConnectionMachine/group-2 here as well, since ideally you will all (group1/group2) serve the data in the same way and through the same api? Hopefully?

[Sandr0x00]

Do we get an API? I thought we have to get the data directly from the DB? Reference from our group. Reference from @MusicConnectionMachine/group-3. (Like I understand it, group 3 also plans to fetch the data directly from db)

But we can agree on an API. If we agree on an API, do you give us the option to save our relationships in the DB, or do we have to do it ourselves?

Or do you mean, how you plan to save the data in the DB? What data do you have? Composer - Music Piece? Or Composer - Source like described in the project description (Wolfgang Amadeus Mozart → [ https://musicbrainz.org/artist/b972f589-fb0e-474e-b64a-803b0364fa75, soruce2, …])?

[ShilpaGhanashyamGore]

Renaming the issue to "Interface to Group 3/4"

[Sandr0x00]

Reference to a similar topic.

[simonzachau]

this should be resolved by the api

[kordianbruck]

It really is resolved