Device and Group datamodels used in API requests differ from data models used internally or in MongoDB

[AlvaroVega]

IoT Agent Node Lib version the issue has been seen with

1.X, 2.X, 3.X

Bound or port used (API interaction)

Other

NGSI version

NGSIv2

Are you running a container?

None

Image type

None

Expected behaviour you didn't see

I.E:

• Attributes are stored into mongo DB as active but in Group and Device model are called attributes
• Groups are managed internally (and not only into the as services (refer to PR Add new /iot/groups API route #1648 and Issue [Remove] /iot/services API path #1649 )

All datamodels used across codebase, API requests and DB models should be homogeneus

[AlvaroVega]

We should review doc about ensure API s properly described.
Possibly a db script update should be needed to solve this issue if finally should be fixed.

[Madhu1029]

Hi @AlvaroVega ,

Could you please explain this issue in detail? I want to work on this issue.

[AlvaroVega]

Hi @AlvaroVega ,

Could you please explain this issue in detail? I want to work on this issue.

Not sure if this is the best issue to implement now, since implements changes in database (mongo) model and has some impact in current production deploys.

[fgalan]

As part of this issue, analyze which exact adaptations are needed.

The final objective is that API, code and DB model get aligned (code-API adaptation is also mentioned here).

[fgalan]

Maybe both #1649 and this issue should be addressed together.