3 phase workflow for TM Contribution

[egekorkan]

After talking with @TejInaco , we think that a 3 phase process to commit TMs. They can be all separate pages of the Contribution Pop-up.

1. Adding metadata and validation (author, license etc.). The validation is purely JSON Schema based
2. Device Interactions. The browser interacts (over a gateway) with the Thing. All properties are shown in the page with their values. They should be all readable and the values are saved as a JSON and will be contributed as an attachment to the TMC. The user should give their OK that the values make sense (not reading -1000 Volts for a voltage in domestic settings)
3. The TMC Endpoint information are given, the TM is submitted and the user receives the id.

[yashgoyal0110]

Hey @egekorkan
can i take this one?

[egekorkan]

@yashgoyal0110 thank you for the offer but @TejInaco is on this one :)

[TejInaco]

This issue will change the "Contribute To Catalog" feature in the following way:

a) [Already implemented] When the user clicks the "Contribute To Catalog" button, a dialog is shown with the following fields:

Model
Author
Manufacturer
License
Copyright Year
Copyright Holder
The "Validate" button will retain its current logic.

b) The user needs to click the "Next" button to proceed to step 2.

c) In step 2, the user will fill in the following fields:

TM Catalog Endpoint [Already implemented]
Name of the repository [Already implemented]
d) The user needs to click the "Next" button to proceed to step 3.

e) A new section will be implemented to test the endpoints. This is the final step, and the "Submit" button will be shown.

A "Test Endpoints" button will be available.
If the user clicks "Test Endpoints", it will start the same logic as implemented on the To Td "button".
After getting the converted TM, the new TD, it is necessary to test all forms in all properties for the status 200.
If a different status is shown, the error must be sown to the user with the corresponding name of property and number of the form

[egekorkan]

@TejInaco this is correct but the following point needs to be changed

After getting the converted TM, the new TD, it is necessary to test all forms in all properties for the status 200.
If a different status is shown, the error must be sown to the user with the corresponding name of property and number of the form

It is not just about getting status 200. The user needs to verify the values make sense. If the user is interacting with an energy meter in a low voltage setup and the voltage shows 10000 volts, the TM is wrong somewhere.