Download the PHP package ride/app-orm-survey without Composer

On this page you can find all versions of the php package ride/app-orm-survey. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package app-orm-survey

Ride: ORM Survey Model

This module will add models to the Ride ORM to create and manage surveys.

Models

Survey

The model holds the available surveys. A survey is a container of questions which belong together. You can set a name and description for a general introduction.

SurveyQuestion

The model holds the definitions of the questions. A question belongs to one survey only. You can set the question and a description to give an explaination about the question.

A question can hold predefined answers.

You can a flag a question to allow multiple answers. This is for the frontend to know if a radio button should be used to allow only one answer, or checkboxes to allow multiple answers.

You can flag a question as being open. When the open question has no answers, a single text area should be displayed for an open answer. If the open question has answers, an "other" option should be added with a text area for an open answer.

SurveyAnswer

The model holds the predefined answers.

Each answer can have a score for evaluating the question. More on evaluations later on.

An answer can also contain a Likert scale. See the next topic to see what it is.

SurveyLikert

The model holds the available Likert scales.

A Likert scale is used for a question which should look like this:

very bad bad average good very good
answer 1 X
answer 2 X
answer 3 X

In this example, the very bad ... very good is the Likert scale. The answer 1 ... answer 3 are the regular answers which hold the Likert scale.

You set a name for the scale and add the available answers.

SurveyEvaluation

The model is used to create evaluations. An evaluation can evaluate a single question or a complete survey.

You set a number of questions to the evaluation in combination with a set of rules.

When a is being evaluated, a total score is calculated for the questions selected in the evaluation. The result of an evaluation is the total score of these questions, combined with the rule which applies to this score.

The evaluation can calculate an average score for all logged evaluations.

SurveyEvaluationRule

The model holds the rules of the evaluations. These rules hold a title and a body, as well as a minimum and maximum score.

The rule is considered an evaluation result when the score of the answers of the evaluation questions is between the minimum and maximum score of the rule.

SurveyEvaluationLog

The model is a history of evaluations.

Keeping this history is optional but adds the functionality to calculate an average score for an evaluation. This can be done at any time with the CLI command provided by the ride/cli-orm-survey module.

SurveyEntry

The models is used to register when somebody fills in a survey.

Out of the box, it holds a name, the survey and the given answers.

This is a simple model which, most of the time, will be extended to add more information about the person who filled in the survey. Just keep the and fields.

SurveyEntryAnswer

The model holds all registered answers of a survey entry.

This model has 2 relationships with the answer model.

The field holds the selected predefined answer.

When a Likert is used, the field holds the Likert answer while the field holds the answer of the question which uses the Likert scale.

So applied on our Likert example from above: the field holds the very bad ... very good answer, while the holds the answer 1 ... answer 2.

The answer of an open question is set in the field.

Related Modules

Installation

You can use Composer to install this application.

All versions of app-orm-survey with dependencies

PHP Build Version
Package Version
Requires ride/app Version ^1.0.0
ride/app-orm Version ^1.0.0
ride/lib-orm Version ^1.0.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package ride/app-orm-survey contains the following files

Loading the files please wait ....