{"title":"Local File System Connector","nodeType":"Source","id":"*O_PIqTqjlUGuQ19K","factoryName":"org.knime.filehandling.core.fs.local.node.LocalConnectorNodeFactory","factoryId":"org.knime.filehandling.core.fs.local.node.LocalConnectorNodeFactory","path":["IO","Connectors"],"owner":"knime","ownerAccountId":"account:team:b5f0848f-496d-4e6a-b869-fa3532248db7","description":"<p>This node provides access to the file system of the local machine. The resulting output port allows downstream nodes to access <i>files</i> , e.g. to read or write, or to perform other file system operations (browse/list files, copy, move, ...).</p>\n            \n            <p><b>Note:</b> In many cases it is not necessary to use this connector node to access the local file system. Nodes that require file system access (e.g. the File Reader node) typically provide local file system access, for example by choosing <i>Read from</i> &gt; <i>Local File System.</i> The purpose of this connector node is to make file access with <a href=\"https://docs.knime.com/latest/analytics_platform_file_handling_guide/index.html#path-syntax\" rel=\"ugc nofollow noopener noreferrer\">relative paths</a> more flexible, by allowing to explicitly configure the <a href=\"https://docs.knime.com/latest/analytics_platform_file_handling_guide/index.html#working-directory\" rel=\"ugc nofollow noopener noreferrer\">working directory</a> of the resulting file system connection. For example, this makes it easier to relocate (or change) the files that your workflow accesses, because you only need to change the working directory.</p>\n            \n            <p><b>Path syntax:</b> The path syntax is identical to the one used by the operating system of the machine where this node is running, e.g. on Windows a path could look like <tt>C:\\Users\\joe</tt> .</p>\n            \n        \n        ","shortDescription":"Provides a file system connection with access to the file system of the local machine.","keywords":[],"deprecated":false,"streamable":true,"tags":["IO","Connectors","Streamable"],"icon":"data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAABdSURBVHgBzZFBCsAgDARX6Sf6m/b/j9oWURAxxsSDDuxBjMNiAvqwOQdhDlG6IJkiCHVBz+kSNE3sAo39Amk9NM4fAuEg5odPJSmZ4sK40fvnhtJgiVED88pcn/gBau8Xod8R++EAAAAASUVORK5CYII=","sinceVersion":"4.5.0","views":[],"inPorts":[],"outPorts":[{"objectClass":"org.knime.filehandling.core.port.FileSystemPortObject","color":"178ba5","dataType":"File System","optional":false,"name":"Local File System Connection","description":"Local File System Connection"}],"dynInPorts":[],"dynOutPorts":[],"additionalSiteInformation":{"url":"https://update.knime.com/analytics-platform/5.12","trusted":true,"enabledByDefault":true,"name":"KNIME Analytics Platform 5.12 Update Site","version":"5.12.0"},"dialog":[{"sectionName":"Options","fields":[{"name":"Use custom working directory","description":"Whether to set a custom working directory or not. Unless this option is set, the working directory will be the home directory of the current operating system user.","optional":false},{"name":"Working directory","description":"Specify the working directory of the resulting file system connection. The working directory must be specified as an absolute path, for example C:\\Users\\joe. A working directory allows downstream nodes to access files/folders using relative paths.","optional":false}]}],"links":[],"kudos":[],"kudosCount":0,"bundleInformation":{"bundleVersion":"5.12.0.v202605070718","bundleName":"Core file system connector nodes that are always present","bundleSymbolicName":"org.knime.filehandling.core.fs.nodes","bundleVendor":"KNIME AG, Zurich, Switzerland","featureSymbolicName":"org.knime.features.base","featureName":"KNIME Base nodes","featureVersion":"5.12.0.v202606261225","featureVendor":"KNIME AG, Zurich, Switzerland","extensionId":"*bjR3r1yWOznPIEXS"},"frequentSuccessors":[]}
