Davinci Library

Overview


The davinci library contains resources that are posted to the library by the davinci community. Resources include apps and toolboxes, document templates and other resources. Resources submitted to the library are screened for spam and checked for security holes, but not tested or verified for functionality.

We rely on the davinci community to test and report any issues concerning resources posted to the library. Resources in the library are provided "as is". Users are responsible to validate the appropriateness of using any resource on the davinci platform for the intended purpose.

Before using resources from the davinci library, be sure to be familiar with davinci terms of use.
Analytics, Modeling and Machine Learning Contains information and resources about various modeling topics. Including : Math and statistics, Business and Markets and Machine Learning
view
Apps applications that can be installed and integrated into your desktop. When you first register, you will have a default set of apps installed.
view
Toolboxes are widgets that you use to edit a davinci page. Once installed they are accessible from your page editor.
view
The Javascript Library contains javascript code that can be used to either process data for analytics or provide additional dynamic behaviour to a page or desktop.
view
Boilerplate contains sample boiler plate text for various documents used in business, such as policy documents or model documents. The content can be used freely in user documents, and can be linked directly into a document using the latex app or into an HTML document.
view
Servers and Desktops section include code for hosting servers that allow your pages and desktops to interact with machines on your network, including your local machine. This is particularly helpful for including data in a page that comes from your local hard drive.
view

Versioning


Versions in the davinci library is specified by three numbers.(major.minor.patch) Example:

v1.2.1

On the davinci platform, the major.0.0 version of any app or library will receive all updates to that app or library, for that version. That is, v.1.0.0 will always be the most recent version of the version 1 of the resource. Additional versions, such as v1.1.0 will be static, and not updated as v1.1.1 is released. However, v1.0.0 will inherit all changes to newer v1 releases.

When a change is made that cannot be pushed to the major version release without breaking it, a new version is created. (such as v2.0.0)

This ensures that users who wish to receive all updates to a resource, can just use the major version.

If you are running a production process where you cannot accept automatic updates to the code, you should use one of the other published versions. (for example, v1.2.1, which will remain static)

During the initial rollout phase of davinci, all libraries and apps are hosted as v1.0.0 versions. That is, there will be no static libraries or apps until davinci exits the launch phase. Changes and fixes to apps and libraries will be pushed out to all users.

Contents