telefonicaid / telefonicaid/iotagent-node-lib
Device and Group datamodels used in API requests differ from data models used internally or in MongoDB
Open
Nobody has claimed this yet.
NGSIv2
- Dominant language
- JavaScript
- Stars
- 62
- Forks
- 90
- Avg merge
- 2h 35m
- Merged PRs (30d)
- 1
Description
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
activebut in Group and Device model are calledattributes - Groups are managed internally (and not only into the as
services(refer to PR #1648 and Issue #1649 )
All datamodels used across codebase, API requests and DB models should be homogeneus
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the Device and Group datamodels used in API requests, internal code, and MongoDB, focusing on the active versus attributes and groups versus services differences described here. Read PR #1648 and Issue #1649 first; done means the affected datamodels are homogeneous across those interfaces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, mongodb
- Domain
- api, backend, database
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100