...
- Speed: speed is a feature. Predictably say how long some ingest will take.
- Allowing recovery from failure; pick up where it left off. Speed affects this; if it's fast enough you don't have to worry about it. Otherwise, make sure there's recovery. Harvesters should allow recovery, where possible. Indexers could also be less speedy than mappings and enrichments, and may deserve recovery features.
- Adding automation that was originally specified: have a program that shepherds the process all the way through. Scheduling.
- Eventually, provide a useable mapping DSL
- Needs real market research
- This is not a turnkey solution yet. Some things like DSLs will be evaluated later when we can more confident in understanding how big the user base is.
- Writing mappings ourselves w/out in the third system without a DSL will how we allow us to understand the problem space better.
- Ability to debug things, especially mappings
...