telefonicaid / telefonicaid/iotagent-node-lib
timestamp alternative format support (to allows storing milliseconds timestamps in orion)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 62
- Forks
- 90
- Avg merge
- 2h 35m
- Merged PRs (30d)
- 1
Description
as discussed here:
https://github.com/telefonicaid/fiware-orion/issues/432
for DataTime type orion strips milliseconds.
now timestamp send by the iot agent lib are all in DataTime type. So despite IoT Agent handles milliseconds, these are not stored in Orion.
The proposal then is to be able to configure the "timestamp" type, either Unix timestamp, or to a valid alternative.
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
Start by reading the discussion in linked issue #432 and tracing how the IoT Agent represents and sends DataTime timestamps. Clarify the supported alternative formats and where timestamp configuration belongs before changing behavior. Done means a configured format can preserve milliseconds when timestamps are stored in Orion, with coverage for the supported formats.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100