@ddeboer @Baachi @sagikazarmark - I just want your opinion on a new Reader use case. If you agree, I'll get going on writing it. Most importantly, perhaps you can tell me if this is a use case that can be achieved using one of the current readers that are implemented (but I doubt it :P)
A large part of our workflow is allowing people to import data. By far the biggest use is import via CSV.
The second largest use case is the import of files that reside on an SFTP server somewhere.
The reader would essentially follow the spec:
connect to the FTP / SFTP using an appropriate, well maintained library.
read the contents of the directory specified in the connection
optionally, move those files into another remote 'working' directory (like a timestamp folder)
read the full file paths relative to the connection base into the $items array
The rest will follow the reader interface.
Let me know if you think there is enough of a use case to include this. Also, if you have any suggestions on FTP/SFTP libraries, that would be welcome too - I have some idea but I'm not sure if you have any minimum criteria in mind.
@ddeboer @Baachi @sagikazarmark - I just want your opinion on a new Reader use case. If you agree, I'll get going on writing it. Most importantly, perhaps you can tell me if this is a use case that can be achieved using one of the current readers that are implemented (but I doubt it :P)
A large part of our workflow is allowing people to import data. By far the biggest use is import via CSV. The second largest use case is the import of files that reside on an SFTP server somewhere.
The reader would essentially follow the spec:
$items
arrayThe rest will follow the reader interface.
Let me know if you think there is enough of a use case to include this. Also, if you have any suggestions on FTP/SFTP libraries, that would be welcome too - I have some idea but I'm not sure if you have any minimum criteria in mind.