Define Schema metadata

[joepavitt]

Follow-on item from Auto-detection of Schema

With a base topic/payload schema in place, users will want to document their UNS/Topic Hierarchy to make it easier to consume and understand.

This issue is to track the development work to add in meta data to the schema that is auto-generated. Such meta data will start with:

• Description Field

Design work was produced in Auto-detection of Schema, and updated designs will be attached here to reflect the new feature.

[joepavitt]

Just a concern I've thought of here, given that topics only persist for 25 hours - that would also remove the descriptions too, right? @hardillb

[hardillb]

The 25hr limit is built into the current Team Broker topic storage, we will move the Team Broker topic storage to the same backend as the 3rd party broker topics.

This storage will not remove topics and metadata unless asked to by the team owner.

[joepavitt]

Which pieces of the puzzle are missing right now for us to start working on this UI piece? Is there an API/DB that we could start integrating with and get this moving, or does the existing Team Broker need to transition over first?

[hardillb]

I need finish the API stuff for topic storage, the 3rd Party broker creds took a little too long yesterday (test problems). Trying to get it done today.