Our use-case is such that DI Studio is used for data prep within the context of a given project, so there is no broader ETL concern beyond the scope of that given project.   For what we're doing now: we support Subversion, so we can utilize the DI Studio tools menu to point at a given Subversion repository, then right-click to archive anything in particular to that repository. Combining that with check-out/check-in works, but is not very smooth.   Want: they already have check-out/check-in... if that tied into the source-control repository directly, it would be so much easier: every time you check something back in, you provide a check-in comment and it gets a new version automatically. For any of those micro-versions, we generally don't care what they are. But at any given time (say, release time), we should have the ability to tag everything under a given hierarchy (say, a project) with a tag, which would tie the version of each component in the hierarchy at the time of tag to the given tag. So basically, everything is always source controlled, and tagged with a "release tag" for any given release. This means the production system only needs to keep track of "which release" it is.  Rollbacks to a previous release should be allowed by providing the tag and the system should roll everything back to the check-in version corresponding to the provided tag.  This is all common practice, and should be supported by any decent source control platform (TFS, GIT, SVN, perhaps others).   Options evaluated... nothing really. I'm not aware of any solutions other than the CVS/SVN tabs in the DI Studio options; and then archiving there. Thus this question fishing for 3rd party addons/plugins/extension. 🙂   Comments appreciated: Metadata seems to be history with SAS Viya, no DI Studio analog as yet in SAS Viya... any comments about the future of DI Studio are welcome also. If it's simply "going away" and if we should perhaps prepare for that possibility, it would be nice to know.     ... View more

Can we summarize this briefly to state that, even during development, one should not expect to be prompted to supply "user prompts" when running a job directly in DI Studio? For instance, I've created a simple job that has a test prompt (in the job properties)... when I run it, right from DI, there is no prompt displayed: it just uses the default and runs with it. I assume that's normal, but is there a way I can ever supply the prompt manually while testing in DI Studio, (without needing to modify the default and/or deploy/integrate with a testing tool)? Thanks! ... View more

I know this is an old question... but I believe OCR is improving now, and even open source approaches are coming along and being integrated into R: https://ropensci.org/blog/technotes/2017/08/17/tesseract-16 BR is interesting in that they appear to offer a solution which can generate a catalog of all your documents and then retrieve relevant ones based on search of just about anything in addition to text (Example: search on the Nike "swoosh" logo). I believe they can also make corrections to the entire catalog if, say, a very specific "glyph" was mis-recognized as a B rather than an 8: if you make the correction anywhere, it automatically applies to every document in the catalog. I never actually got my hands on BR, but it was this facet of the overall BR solution that made it sound interesting to me. ... View more