search

MusicConnectionMachine / StructuredData

In this project we will be scanning structured online resources such as DBPedia, Worldcat, MusicBrainz, IMSLP and other databases
GNU General Public License v3.0
4 stars 3 forks source link

Model #8

Closed simonzachau closed 7 years ago

simonzachau commented 7 years ago

@MusicConnectionMachine/group-1 & @MusicConnectionMachine/group-2

Have you thought about how the data model of the entities is going to look like? We would like to build on it for our relationship algorithms in the near future.

Henni commented 7 years ago

This was posted a while back on gitter: https://imgur.com/a/2gRzu

simonzachau commented 7 years ago

@Henni: what in this image is coming from Project A? Some parts look more like relationships than entities, which is our job. E.g. wife, children, students are likely going to not be filled by A because it's a relation? It'd be nice to have an official documentation of what we get, then we add the relationships on top of it.

Henni commented 7 years ago

I would be surprised if team1 wouldn't find any relationships. And of course they should store them instead of just dropping them. There is no point in doing this twice. Also team3&4 mostly concentrate on relationship extraction from text. Team1 has structured data like this: http://imslp.org/wiki/List_of_works_by_Wolfgang_Amadeus_Mozart Relationship extraction won't be able to detect these connections easily so we have to rely on team1 to import them.

metavaults commented 7 years ago

@MusicConnectionMachine/group-3 and @MusicConnectionMachine/group-4 How do you expect the data from us to be?

@MusicConnectionMachine/group-2 guys, how do you expect the vocabulary we provide should look like?

simonzachau commented 7 years ago

@LukasNavickas I think you are going to extract entities and maybe you are going to find additional attributes for those entities, which you are going to save, too, instead of dropping it (like @Henni suggested). Our job is to find relationships in texts, that occasionally overlaps the mentioned attributes. So it's good for us to know the model, but for now we have no exact expectations ;-).

kordianbruck commented 7 years ago

@LukasNavickas whats the update here? Did you implement the models?

TimHenkelmann commented 7 years ago

@kordianbruck The models have been created in the api project. Should we provide a separate documentation for them?

kordianbruck commented 7 years ago

@TimHenkelmann no, but please make sure all of your code is properly documented!

Gillian0023 commented 7 years ago

@TimHenkelmann Thanks for your documentation ! MusicConnectionMachine/api#28

TimHenkelmann commented 7 years ago

closing this issue as this is done in the api project