Skills and Topic tags about mumbleapi HOT 12 CLOSED

On our last call I think we talked about making this many to many. This way if a tag exists another user can use it. Also makes it easier to assign tags to articles and discussion later down the road. Make sense?

from mumbleapi.

I agree with Dennis. You need a many to many relationship, is the same for Skills and Interests.

from mumbleapi.

for MVP we can start with predefined tags and then feature creating tags if don't exist!

from mumbleapi.

A base app isn't a bad idea if other apps are using this info. Though in this issue @divanov11 did say he wants to add it in the tags for now. Dennis, any pointers?

from mumbleapi.

The Tags can be their own model and it just has a name column (making this the primary key), since we want tags to be unique.

Skills can probably be designed the same way, with a skill name as the column.

Since a user can have many tags and skills, this would be a one-to-many relationship.

I am down to take this issue to work on. If this is okay, then I would love to discuss it before I proceed.

from mumbleapi.

Yes, that makes sense! So a many-to-many relationship in models? I assume we are doing this for the Skills model as well?

from mumbleapi.

Sounds good! I'll be assigning this issue to myself and will be working on this.

from mumbleapi.

Hi there, just wanted to mention something that might be significant.
The skills and tags will be used in several apps e.g user, article, discussion; So I think it would be nice if we define those models in the users' app or preferably in a base app which will contain all the models, utility functions, etc used across the mumble apps. I think the latter is a better approach for scalability.
Thanks

from mumbleapi.

Another doubt I have is how the skills and topics tags will be created. The users will can add new tags? Or there will be a predefined list of tags?
Cheers!

from mumbleapi.

Another doubt I have is how the skills and topics tags will be created. The users will can add new tags? Or there will be a predefined list of tags?
Cheers!

The user can create if that specific tag doesn't exist

from mumbleapi.

Another doubt I have is how the skills and topics tags will be created. The users will can add new tags? Or there will be a predefined list of tags?
Cheers!

I agree. Create tags if it doesn't exist. Probably a future feature.

from mumbleapi.

I think we should add one slug field column in both the model, which can also be used to filter the data. And if we could use django-taggit, I think it will also be good. And I am also in support of many to many relationship for both the table.

from mumbleapi.