2023-08-21 10:27:32 -07:00
Confluence
==========
feat: jira connector (cloud) (#1238)
This connector:
- takes a Jira Cloud URL, user email and api token; to authenticate into
Jira Cloud
- ingests:
- either all issues in all projects in a Jira Cloud Organization
- or
- issues in user specified projects, boards
- user specified issues
- processes this kind of data:
- text fields such as issue summary, description, and comments
- dropdown fields such as issue type, status, priority, assignee,
reporter, labels, and components
- other data such as issue id, issue key, project id, information on
subtasks
- notes down attachment URLs, however does not process attachments
- stores each downloaded issue in a txt file, in a predefined template
form (consisting of the data above)
- then processes each downloaded issue document into elements using
unstructured library
- related to: https://github.com/Unstructured-IO/unstructured/issues/263
To test the changes, make the necessary setups and run the relevant
ingest test scripts.
---------
Co-authored-by: ryannikolaidis <1208590+ryannikolaidis@users.noreply.github.com>
Co-authored-by: ahmetmeleq <ahmetmeleq@users.noreply.github.com>
2023-09-06 13:10:48 +03:00
Connect Confluence to your preprocessing pipeline, and batch process all your documents using `` unstructured-ingest `` to store structured outputs locally on your filesystem.
2023-08-21 10:27:32 -07:00
First you'll need to install the Confluence dependencies as shown here.
.. code :: shell
pip install "unstructured[confluence]"
Run Locally
-----------
.. tabs ::
.. tab :: Shell
2023-12-11 16:29:41 -05:00
.. literalinclude :: ./code/bash/confluence.sh
:language: bash
2023-08-21 10:27:32 -07:00
.. tab :: Python
2023-12-11 16:29:41 -05:00
.. literalinclude :: ./code/python/confluence.py
:language: python
2023-08-21 10:27:32 -07:00
Run via the API
---------------
feat: jira connector (cloud) (#1238)
This connector:
- takes a Jira Cloud URL, user email and api token; to authenticate into
Jira Cloud
- ingests:
- either all issues in all projects in a Jira Cloud Organization
- or
- issues in user specified projects, boards
- user specified issues
- processes this kind of data:
- text fields such as issue summary, description, and comments
- dropdown fields such as issue type, status, priority, assignee,
reporter, labels, and components
- other data such as issue id, issue key, project id, information on
subtasks
- notes down attachment URLs, however does not process attachments
- stores each downloaded issue in a txt file, in a predefined template
form (consisting of the data above)
- then processes each downloaded issue document into elements using
unstructured library
- related to: https://github.com/Unstructured-IO/unstructured/issues/263
To test the changes, make the necessary setups and run the relevant
ingest test scripts.
---------
Co-authored-by: ryannikolaidis <1208590+ryannikolaidis@users.noreply.github.com>
Co-authored-by: ahmetmeleq <ahmetmeleq@users.noreply.github.com>
2023-09-06 13:10:48 +03:00
You can also use upstream connectors with the `` unstructured `` API. For this you'll need to use the `` --partition-by-api `` flag and pass in your API key with `` --api-key `` .
2023-08-21 10:27:32 -07:00
.. tabs ::
.. tab :: Shell
2023-12-11 16:29:41 -05:00
.. literalinclude :: ./code/bash/confluence_api.sh
:language: bash
2023-08-21 10:27:32 -07:00
.. tab :: Python
2023-12-11 16:29:41 -05:00
.. literalinclude :: ./code/python/confluence_api.py
:language: python
2023-08-21 10:27:32 -07:00
2023-09-11 11:40:56 -04:00
Additionally, you will need to pass the `` --partition-endpoint `` if you're running the API locally. You can find more information about the `` unstructured `` API `here <https://github.com/Unstructured-IO/unstructured-api> `_ .
2023-08-21 10:27:32 -07:00
For a full list of the options the CLI accepts check `` unstructured-ingest confluence --help `` .
feat: jira connector (cloud) (#1238)
This connector:
- takes a Jira Cloud URL, user email and api token; to authenticate into
Jira Cloud
- ingests:
- either all issues in all projects in a Jira Cloud Organization
- or
- issues in user specified projects, boards
- user specified issues
- processes this kind of data:
- text fields such as issue summary, description, and comments
- dropdown fields such as issue type, status, priority, assignee,
reporter, labels, and components
- other data such as issue id, issue key, project id, information on
subtasks
- notes down attachment URLs, however does not process attachments
- stores each downloaded issue in a txt file, in a predefined template
form (consisting of the data above)
- then processes each downloaded issue document into elements using
unstructured library
- related to: https://github.com/Unstructured-IO/unstructured/issues/263
To test the changes, make the necessary setups and run the relevant
ingest test scripts.
---------
Co-authored-by: ryannikolaidis <1208590+ryannikolaidis@users.noreply.github.com>
Co-authored-by: ahmetmeleq <ahmetmeleq@users.noreply.github.com>
2023-09-06 13:10:48 +03:00
NOTE: Keep in mind that you will need to have all the appropriate extras and dependencies for the file types of the documents contained in your data storage platform if you're running this locally. You can find more information about this in the `installation guide <https://unstructured-io.github.io/unstructured/installing.html> `_ .