The Data Import (DI) SIG had 3 goals:
...
1.) Data Import is reported as serving non-API ready data needs with an active community of users
...
The DI SIG informed many aspects on how Data Import is used today in the field, in service of incorporating non-API ready data into Ed-Fi data infrastructure. With an active SIG with over 40+ members to contribute to the
...
forum, we've learned that the tool is serving needs with non-API ready data
...
. From these conversations, we've learned that Data Import is active in the assessment, educator preparation program (EPP), finance data and
...
other domains where API pathways are non-existent. It is recognized from these conversations, Data Import carries a maintenance burden
...
for the implementer
...
to maintain
...
, which is balanced in its usage along with the need to import such data in Ed-Fi environments. It too is recognized that direct API connections from education data producing products is ideal and preferred, which relieves the maintenance burden of running additional ETL solutions to accomodate.
2.) Numerous viable open-source and low-cost alternatives exist for serving the ETL need
...
4.) Additional Data Import SIG requests lead to these feature requests
- John Bailey - has noticed the first time they are importing data, it seems faster than subsequent imports (SF:
- Emilio and Rosh - Would like improved logging. It logs too much and they have to truncate the table often
- Zurab - duplicated headers in files have posed issues; Emilio - the pre-processor could help with this issue
- DI-1135 - Array Format in CSV
- John Bailey - 1.3.2 included a Docker container, but it is unclear how to kick off a schedule
- Zurab - Source code uses a library to work with FTP servers. The library does not work if the FTP server has a certain setting turned on. Works fine with SFTP, but not FTP.
- Mike Werner - Documentation is lacking