Coder Social home page Coder Social logo

knowagelabs / knowage-documentation Goto Github PK

View Code? Open in Web Editor NEW
12.0 14.0 27.0 138.99 MB

Documentation for Knowage Server

Home Page: http://knowage-suite.readthedocs.io/

License: GNU Affero General Public License v3.0

Python 92.56% CSS 7.44%
restructuredtext documentation readthedocs sphinx

knowage-documentation's Introduction

Knowage Documentation

Documentation badge

How to contribute

Knowage is open to external contributions. You can submit your contributions into this repository through pull requests. Before starting, here there are a few things you must be aware of:

  • This project is released with a Contributor Code of Conduct. By participating in this project, you agree to abide by its terms.
  • When you open a pull request, you must sign the Individual Contributor License Agreement by stating in a comment "I have read the CLA Document and I hereby sign the CLA"
  • Please ensure that your contribution passes all tests. If there are test failures, you will need to address them before we can merge your contribution.

Contributions are taken into account as soon as possible, reviewed by Knowage Labs team and merged only if they comply with our standard (see below).

How to write it

This documentation is written using reStructuredText format. reStructuredText is an easy-to-read, what-you-see-is-what-you-get plaintext markup syntax and parser system.

Official resources to learn:

Other useful resources:

This documentation is intent to be used as source for Sphinx (http://www.sphinx-doc.org/en/master/index.html) and Read the Docs (https://readthedocs.org/) to render the documentation.

Our standards

If you wish to contribute, in the following sections you can find standards and best practices.

Structure

Titles are underlined with a nonalphanumeric character at least as long as the text.

  • # for parts
  • = for chapters
  • - for sections
  • ~ for subsections
  • ^ for paragraphs

Example

Part I
########

Chapter 2
===========

Section 3
-----------

Codes

To adding a code you need to use this syntax:

.. code-block:: Type of language
    :linenos:
    :caption: Title.
      Text of the code

Example

.. code-block:: xml
    :linenos:
    :caption: Pointing at a numerical column.
    
      <COLUMNS> 
        <COLUMN field="store_id" visible="false" editable="false" /> 

Images

There are three differents way to add an image, its depend if it is inline of the text, if it is out of the text or if it is inside a table.

  1. Added an image inline:

Insert the |imageX| inside the text and then recall it outside the text (anywhere in the text) whit this syntax:

.. |imageX| image:: media/imageX.png
            :width: dimension
  1. Added an image oustide:

At the point you need to insert an image use this:

.. figure:: media/imageX.png

  Caption of the image.
  1. Added an immage inside a table:
   +-------------------------------+-----------------------+
   |    Icon                       | Name                  |
   +===============================+=======================+
   | .. figure:: media/imageX.png  | Name ImageX           |
   |                               |                       |
   |                               |                       |
   +-------------------------------+-----------------------+
   | .. figure:: media/imageY.png  | Name ImageY           |
   |                               |                       |
   |                               |                       |
   +-------------------------------+-----------------------+
 

Example

1. If your dataset is similar to another existing dataset, you can click the **Clone** icon |image16|.

    .. |image16| image:: media/image23.png
       :width: 30
   
2. In the **Detail** tab you define the Name, the Label and an optional Description of the dataset (refer to figure below). 

    .. figure:: media/image22.png

        Dataset Panel.
 
3. +-------------------------------+-----------------------+-----------------------+
   |    Icon                       | Name                  | Description           |
   +===============================+=======================+=======================+
   | .. figure:: media/image8.png  | Knowage user          | Open a hidden menu    |
   |                               |                       | with extra            |
   |                               |                       | functionalities.      |
   +-------------------------------+-----------------------+-----------------------+
   | .. figure:: media/image9.png  | Select role           | Select the            |
   |                               |                       | authentication role   |
   |                               |                       | (available if you are |
   |                               |                       | associated to more    |
   |                               |                       | than one role).       |
   +-------------------------------+-----------------------+-----------------------+
        

Tables

To create a table into the document you need to "draw" the contours of the table physically as shown below.

 +------------+------------+--------------+
 | HeaderA    | HeaderB    | HeaderC      |
 +============+============+==============+
 |    AA      | BA         | CA           |
 |            |            |              |
 +------------+------------+--------------+
 |    AB      | BB         | BC           |
 |            |            |              |
 +------------+------------+--------------+

Example

     +-----------------------+-----------------------+-----------------------+
     |    Dataset            | Private               | Public                |
     +=======================+=======================+=======================+
     |    User               | Created from file     | Dataset created from  |
     |                       | (CSV, XLS) or from    | file (CSV, XLS) or    |
     |                       | QbE (My Data) for     | from QbE (My Data)    |
     |                       | personal use only.    | and shared with other |
     |                       |                       | users.                |
     +-----------------------+-----------------------+-----------------------+
     |    Technical          | Not applicable.       | Dataset created by a  |
     |                       |                       | BI developer to be    |
     |                       |                       | used in one or more   |  
     |                       |                       | documents.            |
     |                       |                       |                       |
     |                       |                       | Not visible to end    |
     |                       |                       | users.                |
     +-----------------------+-----------------------+-----------------------+
     |    Enterprise         | Not applicable.       | Dataset of any type   |
     |                       |                       | created by a          | 
     |                       |                       | technical user and    |
     |                       |                       | certified by a        |
     |                       |                       | trusted entity within |
     |                       |                       | the organization, and |
     |                       |                       | made available to all |
     |                       |                       | end users for reuse.  |    
     +-----------------------+-----------------------+-----------------------+

Text style

There are several ways to optimize parts or words in the text.

  1. Bold text:
**text to be emphasized**
  1. Italic text:
*text to be emphasized*
  1. Highlighted text (e.g. code, filename, parameter, and so on):
``text to be emphasized``
  1. Bulleted list:
- First step
- Second step
- Third step

Example

1.
Let us suppose to enter, with end user credentials, the data management area clicking on the **Workspace** icon from BI functionalities menu as shown in figure below and the **Data** section of the window.
2.
Click the *Add* icon
3.
Define the ``JAVA_HOME`` variable inside the users’ file ``.bash_profile`` used in the installation process
4.
- **My dataset**: datasets created by yourself uploading a CSV or XLS file or creating a query on a business model using the Qbe interface;
- **Enterprise dataset**: certified datasets,namely datasets created by the technical/experts users and shared with the end user.
- **Shared dataset**: datasets created and shared by other end users;

Box

Sometimes into the text you need to draw attention with a box. We use four differents type of boxes.

.. note::
      **Read more**
         
      Text of the note.
         
.. warning::
      **Warning**
         
      Text of the warning.
         
.. hint::
      **Advice**
         
      Text of the hint.
         
.. important::
      **Notable content**
         
      Text of the important.  

Example

.. hint::
     **Authentication Management**:
     The choice of handling authentication internally or delegating it to an external SSO system typically depends on the presence of an authentication system already in place. If this is the case, Knowage can seamlessly integrate with the existing authentication infrastructure.

knowage-documentation's People

Contributors

abotlegacy avatar anbernabei avatar andrijanaeng avatar davide-zerbetto avatar fralucch avatar github-actions[bot] avatar gmansueto avatar iiennaco avatar irefas avatar kerny3d avatar marioabb avatar matmassa avatar mbalestri avatar mcortella avatar mesecarbg avatar n3ils avatar nunziam avatar predragjosipovic avatar primenzi avatar redjaw avatar rselakovic avatar sbigiachino avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

knowage-documentation's Issues

ISSUE: connectionName parameter does not works!

knowage server: 8.1
ubuntu os: 22.04
BIRT-report-designer: 4.13.0

  1. Datasource Connection:
    image
  2. Dataset Preview
    image
  3. Report Parameters
    image
  4. connectionName parameter:
    image
  5. Parameter Binding
    image
  6. Birt Report Execution:
    image
  7. Data Source configured at knowage server:
    image
  8. Deployed at Knowage server:
    image
  9. Analytical Driver:
    image
  10. Report Executed at knowage server
    image

Now, Compare the data of screenshots of No.6 and No. 10. it is same!
The Knowage server is not using the correct data source when running reports. Even though a connection name parameter is passed when executing the report on the server, it is not pulling data from that data source.

Instead, it is always using the data source defined in the original BIRT report design, regardless of the connection name passed.

The behavior should be:

When a report runs on Knowage server and a connection name parameter is provided, it should fetch and display data from that specified data source.

But it is not working that way. It always defaults back to using the data source hardcoded in the BIRT report design, rather than using the one provided in the connection name parameter as it's supposed to.

So in short, the server is not respecting the connection name parameter and using the wrong data source when reports are executed.

Help Me
Thank You

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.