Closed Alino closed 6 years ago
This was agreed on today on our GALA meeting
Swagger definition updated https://github.com/GALAglobal/TAPICC-API-implementation/commit/de7e3010c3ff2bc977210e09428f05218d003990 Implementation updated https://github.com/GALAglobal/TAPICC-API-implementation/commit/467088890fa438352853eea15c03fd51b2bc8077
It looks like the Swagger definition still shows the assetId path parameter to create a new task:
Thanks for reporting that, fixed https://github.com/GALAglobal/TAPICC-API-implementation/commit/bce8a4e85b6358dd74ba86d958413f93ee0169f6
Currently each Task has to be associated with one Asset by assetId property. There is no way to create an individual Task (not associated with an Asset) with an API endpoint. I thought it is not a problem, but as I was reviewing the Task types document, I found out there are few Task types which are not supposed to be necessarily tied to an Asset.
For example: Content creation
Therefore I suggest to change the following Task related API endpoints
from
to
also