If you already have an Unstructured Starter or Team account and are not already signed in, sign in to your account at
https://platform.unstructured.io. For an Enterprise account, see your Unstructured account administrator for instructions,
or email Unstructured Support at support@unstructured.io.
After you sign in, the Unstructured user interface (UI) appears, which you use to create your source connector.After you create the source connector, add it along with a
destination connector to a workflow. Then run the worklow as a
job. To learn how, try out the hands-on UI quickstart or watch the 4-minute
video tutorial.You can also create source connectors with the Unstructured API.
Learn how.If you need help, email Unstructured Support at support@unstructured.io.You are now ready to start creating a source connector! Keep reading to learn how.
Ingest your files into Unstructured from Couchbase.The requirements are as follows.
To learn more about how to set up a Couchbase cluster and play with data, refer to this tutorial.To create the source connector:
On the sidebar, click Connectors.
Click Sources.
Cick New or Create Connector.
Give the connector some unique Name.
In the Provider area, click Couchbase.
Click Continue.
Follow the on-screen instructions to fill in the fields as described later on this page.
Click Save and Test.
Fill in the following fields:
Name (required): A unique name for this connector.
Bucket (required): The name of the bucket to connect to on the cluster.
Connection string (required): The connection string for the Couchbase cluster.
Scope: The name of the scope in the bucket. The default is _default if not otherwise specified.
Collection: The name of the collection in the scope. The default is _default if not otherwise specified.
Batch Size: The maximum number of documents per transmitted batch. The default is 50 if not otherwise specified.
Collection ID key (source connector only): The name of the collection field that contains the document ID. The default is id if not otherwise specified
Username (required): The cluster access name (username) that has access to the cluster.
Password (required): The password for the corresponding username.