LBRYCommunity/types
1
0
Fork 0
Code Issues13 Pull requests Projects Releases Packages Wiki Activity

Add tags to schema #16

New issue
Closed
opened 2019-01-25 14:45:51 +01:00 by tzarebczan · 2 comments
tzarebczan commented 2019-01-25 14:45:51 +01:00 (Migrated from github.com)

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.

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.
kauffj commented 2019-01-25 16:23:45 +01:00 (Migrated from github.com)

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 n tags (~5).

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 `n` tags (~5).
tzarebczan commented 2019-02-12 15:31:12 +01:00 (Migrated from github.com)

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.

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.
Sign in to join this conversation.
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
Epic
good first issue
hacktoberfest
help wanted
icebox
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/types#16
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?