Looking at the JSON feed in the "scenegraph-master-sample" I now wonder if the JSON for Direct Publisher is NOT what SceneGraph can use. I tried finding a JSON feed for Roku SDK specification but all I find is the Direct Publisher one. Since it is specifically labeled as being for Direct Publisher does it include things that SDK examples CANNOT USE?! (Such as the Categories functions!)
Some actual statements from ROKU seem to be in order, since all the "Categories" in the GridScreen example in the master ZIP have every "Named Category" in a different sub-list under the heading of the "Specific Category Named" in the JSON feed. So they don't use any Category functions to compile and sift and sort the feed contents based on TAGS for listing in the rows/categories displayed.
If they actually wanted to be helpful (which the obviously DON'T!) they would just publish the Roku Channel SDK so people can see what they do on their own stuff.
jsonnentag Have you tried using the wizard tool I wrote? It was designed to relieve the stress of converting from DP to SceneGraph. And, yes, it will parse your feed file according to your defined categories.
I guess you are referring to this here:
https://github.com/rrirower/DP2SceneGraphWizard
What does this mean exactly?
"NOTE: Your feed file MUST use an extension of '.JSON' or '.XML' and MUST conform to the Direct Publisher JSON and MRSS feed specifications AND define Category objects."
What kind of "Category objects" are required? Only the list of specific episodes or are the Tag based categories supported as well?
Right now (and since I setup the Direct Publisher JSON feed 6 years ago) DP was set to use TAGS to determine what items to list in which Categories. The Note states Categories must be defined, but are both types of categories supported?
https://developer.roku.com/docs/specs/direct-publisher-feed-specs/json-dp-spec.md#content-categories
The feed specification says:
"* A category must contain either a playlistName or query field."
Are both supported in your wizard or only the "playlistName" style where "itemIds" are listed out for each Category? (Either way - whichever you set things up for - I'm going to have to manufacture something before it could hope to work at all.)
The wizard tool generates code that supports the full Json spec. So, categories are fully supported. Categories based on queries and playlists are supported.
If you have further questions or would like to discuss further, please do so on the GitHub site.
I installed the latest version downloaded from github and it mostly works OK for the JSON I have.
BUT there is a problem with the way "query" based Categories are created. I attempted creating a github "issue".
Basically, rather than the "AND" requiring all the Tags to be present for a video to be in a Category it is processed like "find everything with Tag #1 and then start over and find everything with Tag #2 . . ." for as many Tags as you list out in the "query". So you get a pile of duplicates in Content Categories when multiple Tags are required in the query.
