Add channel related metadata columns

kauffj commented

2017-10-02 14:43:53 +02:00

(Migrated from github.com)

Copy link

At a minimum:

Name
Thumbnail
Cover
Description

Other considerations:

Primary Language
Featured video
Other channels
Playlists?

Internal Use

Acceptance Criteria

Definition of Done

Tested against acceptance criteria
Tested against the assumptions of the user story
The project builds without errors
Unit tests are written and passing
Tests on devices/browsers listed in the issue have passed
QA performed & issues resolved
Refactoring completed
Any configuration or build changes documented
Documentation updated
Peer Code Review performed

At a minimum: 1) Name 2) Thumbnail 3) Cover 4) Description Other considerations: 1) Primary Language 2) Featured video 3) Other channels 4) Playlists? ## Internal Use ### Acceptance Criteria 1. 2. 3. ### Definition of Done - [ ] Tested against acceptance criteria - [ ] Tested against the assumptions of the user story - [ ] The project builds without errors - [ ] Unit tests are written and passing - [ ] Tests on devices/browsers listed in the issue have passed - [ ] QA performed & issues resolved - [ ] Refactoring completed - [ ] Any configuration or build changes documented - [ ] Documentation updated - [ ] Peer Code Review performed

KamilPiekutowski commented

2017-10-12 03:56:44 +02:00

(Migrated from github.com)

Copy link

How is channel added to lbry now?

tzarebczan commented

2017-10-18 18:35:55 +02:00

(Migrated from github.com)

Copy link

Check out this documentation on channels/schema, maybe it will help:https://github.com/lbryio/lbryschema/tree/master/docs

A channel is created via the Publish screen right now - all that's really captured is a channel name. I think this would lay the initial groundwork to be able to capture additional information when channels are created.

Check out this documentation on channels/schema, maybe it will help:https://github.com/lbryio/lbryschema/tree/master/docs A channel is created via the Publish screen right now - all that's really captured is a channel name. I think this would lay the initial groundwork to be able to capture additional information when channels are created.

tzarebczan commented

2018-07-10 21:43:10 +02:00

(Migrated from github.com)

Copy link

Just came into my mind now that we are working on cleaning up NFSW: Should there be an NFSW setting on channels? What if a channel uses an NSFW thumb - how would we know not to display that.

kauffj commented

2018-07-10 23:27:58 +02:00

(Migrated from github.com)

Copy link

We need channel attributes but I am disinclined to double-down on the poor choice that was a single boolean property called is_nsfw.

We need channel attributes but I am disinclined to double-down on the poor choice that was a single boolean property called `is_nsfw`.

tzarebczan commented

2018-07-10 23:30:57 +02:00

(Migrated from github.com)

Copy link

We can discuss what else to call this self imposed categorization, both on channels and claims. I think this is outside of the opt in filtering to tags idea we've tossed around.

alyssaoc commented

2018-11-19 20:27:05 +01:00

(Migrated from github.com)

Copy link

we should consider this after the signature changes

lyoshenka commented

2019-02-14 00:23:08 +01:00

(Migrated from github.com)

Copy link

moving discussion to https://github.com/lbryio/types/pull/17