2 ms·
> Second: I know I haven't given nearly enough information for detail, but are there existing technologies on the receiving end that could ingest disparate, non
by shakna 5y ago
> Second: I know I haven't given nearly enough information for detail, but are there existing technologies on the receiving end that could ingest disparate, non-mapped, schema-less data of all flavours? Should we look at something like Node Red or Parabola do so some mapping, or are there other generic data receiving technologies we should be aware of that can cope with a multitude of data types, shapes, sizes?
Traditionally, the answer to this is... Data entry. You hire people to convert the data. Because you don't have any guarantee that the data you are getting is clean, nor do you have any guarantee it is compatible, even when getting it from the same source.
Until you're at a rather large scale, it is cheaper to hire a bunch of people willing to do drudge work, than it is to try and automate this. ISPs have rounds of hiring for data entry every year, right before the end of the financial year, because it's still cheaper to hire people for data entry for two or three weeks than it is to make all their receipt handling systems automated.
- dmje 5y agoThat's a great point, and one I'd totally missed. Thanks!