analysis of most used neighbors

[CSchott]

create separate table neighborTags

• key -> hastag
• family -> neighbortag
• value -> amount
  or
• qualifyer -> amount

[merando]

@CSchott & @martingrimmer what is the status of this issue?

[merando]

I'd like to suggest that we also add the hashtag without a neighbortag. This field would count the total occurences of the hashtag. We can use this for a propper visualization of the tag graph later on.
Any objections @CSchott or @martingrimmer ?

[CSchott]

Currently i am getting the hastags by the entities: hastag attribute of the json from the rawtwitterdata table. Currently i am working on storing them again in the neighbourTags table.
So you would like to store the hastags without neighbour in the same table with empty family. Is this correct?

[martingrimmer]

my suggestion:
key: hashtag
family: one of those values: "c" for count, "n" for neighbours
qualifier: if family == "c": neighbour hashtag (eg. "yolo"), otherwise: empty
value: count of the hashtag or the neighbour hashtag

[merando]

I think thats the way to go. Good suggestion @martingrimmer .
@CSchott please implement this, if you have questions feel free to contact us