You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In DIYHub we categorize posts when we curate them with a 1:1 category relation.
We use MySQL for our curation database and I imagine a folder-like structure for users to explore the community on a dedicated page.
by clicking on one of those they get to another level where all the specific categories are listed.
This is just an idea - if a tree is easier to implement I think that would work too.
Our database:
Table "curationChoices"
postAuthor
postPermlink
category
Table "curationCategories"
categoryShort
categoryLong
mainCategory
The relation between both tables is via category <> categoryShort ( I know I should have used the id ;) )
We could create a database view where the postAuthor is combined with the postPermlink and the mainCategory+categoryLong are already joined.
In the best case there is a new admin part:
enter the curation database system (MySQL, ms SQL, etc.)
enter host, port, credentials
pick the post table / database view
pick the 3 important columns from 3.
post identifier (@author/permlink)
post main category
post sub category
The text was updated successfully, but these errors were encountered:
In DIYHub we categorize posts when we curate them with a 1:1 category relation.
We use MySQL for our curation database and I imagine a folder-like structure for users to explore the community on a dedicated page.
by clicking on one of those they get to another level where all the specific categories are listed.
This is just an idea - if a tree is easier to implement I think that would work too.
Our database:
We could create a database view where the postAuthor is combined with the postPermlink and the mainCategory+categoryLong are already joined.
In the best case there is a new admin part:
The text was updated successfully, but these errors were encountered: