-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add tags to schema #16
Labels
type: new feature
New functionality that does not exist yet
Comments
tzarebczan
added
type: new feature
New functionality that does not exist yet
type: discussion
A conversation. No specific changes requested
needs: exploration
Solution unclear, needs research
labels
Jan 25, 2019
For a first version of tags my proposal is that we allow a completely free-form system (perhaps autocompleting from chainquery app-side) limiting to |
This was referenced Jan 28, 2019
lyoshenka
added
the
consider soon
Discuss this issue at the next planning meeting, then remove this label
label
Jan 28, 2019
Closed
I also like the idea of a type attribute for the tag, or some way to specify which tags are responsible for things like categories/topics/genres (i.e. first tag is always the category). I think this will aide on the discovery side. |
Closed
lyoshenka
removed
consider soon
Discuss this issue at the next planning meeting, then remove this label
needs: exploration
Solution unclear, needs research
type: discussion
A conversation. No specific changes requested
labels
Feb 15, 2019
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should allow publishers to set tags for their uploaded content. Would need to discuss implementation details, for example, how many tags do we allow and how is it stored in the metadata. If we want community overlays to work properly, each tag may need to exist on its own, as opposed to a list of tags.
The text was updated successfully, but these errors were encountered: