I've never faced with accents, so, not sure about this case. But I see many useful use cases for using slugify in SQL. But this feature looks more complex in realization. There are many realizations in many languages, but no standard at all.

For the info, slug, slugify, translates string in any language to ASCII, URL compatible string.

For instance, it would help to get a cost-effective, language-independent index, but with a quite correct order.

In VSCode you just had to open any local folder. And it's a manual choice. 

When you opened any folder, which is supposed to be as a project root. Configured the server connection, you then should be able to open ObjectScript Server Explorer (by InterSystems logo icon). There you can observe your code on the server, and do export from context menu. Export will be logged to ObjectScript output, with full path's of exported items. Go to File explorer in VSCode (default view), and from context menu on any folder or class, you will have action Import and compile.

Extracting such amount of data with using JDBC/ODBC, will be much slower than any sort of native access in Cache.

InterSystems Cache offers a way to export the whole table, with selected columns

Open System Management Portal, System Explorer, SQL. Switch to the desired namespace. Click on Wizards and select Data Export

The next steps should be pretty much simple, just select what you need to export and starts in the background. So, you will be able to control how it is going.

Look at the documentation for more details

@Bob Kuszewski, what do you mean by better processes? What does it mean for jdbc driver or any other jar files, which have only one place where they supposed to be published is, maven central. Currently, InterSystems - JDBC and InterSystems XEP just contain empty files, which have to be deleted.

JAR files here, just only 155 bytes in size or even less.

https://repo1.maven.org/maven2/com/intersystems/intersystems-jdbc/3.0.0/

https://repo1.maven.org/maven2/com/intersystems/intersystems-jdbc/2018.1...

https://repo1.maven.org/maven2/com/intersystems/intersystems-xep/2018.1....

At the same time, I would not recommend spending time on official webgateway docker image, as it made to be too specific for ICM and/or Durable %SYS. And at the same time, needs some magic to get it working. e.g. apache will not start without specifically saying so. And even if it started, it does not mean, that it will be started with the CSP module enabled.

Instructions of what? If saying just about Apache+webgateway.

The repo I've provided is quite complete. With some basic knowledge of docker.

So, you just have to build the docker image, publish it to some docker registry, public or private and deploy it with AWS

Deploying just IRIS itself as a container does not make so much sense at all. As it needs to be packed with some application it should run. Containerized IRIS it's not the same as IRIS running on a virtual machine, it's very different, and not so easy to explain it in a simple way.

For instance, you can look at this article, about deploying some web-based IRIS application on Amazon

I would recommend, to contact me through info@caretdev.com, so, we could schedule a discussion, where you could give more details, and I will say the ways how it can be solved.