The Draft-Publishing Cycle

improvement
feature

(Niklas Schwibbe) #1

In short:

The draft-publishing cycle is aimed at users who intensely want to ensure that their content is meeting their quality standards. If you are willing to go the extra mile for content quality, then this feature is for you.

The use case in detail:

Although we normally are more invested into cutting edge technology topics, from time to time a very time-tested problem comes our way and warrants investment of time and effort to improve the AX platform.
To prevent grammatical, orthographical or logical errors and all other kinds of mistakes, it is good practice to prepend your final action of publishing with some form of Q&A cycle like the dual control principle or forms of statistical control.
To reflect these requirements in our platform, we have long since implemented a standard publishing cycle for our automated content, to improve your quality and provide you with the tools and opportunity for meeting the highest quality standards for online publishing.
This is realized by offering our users an additional step in their content delivery process. All changes in a training are at first applied to a draft version of your training, which is then available for normal editing, extensive testing and quality control. After all precautions and steps to ensure perfect content are taken, you then are able to actively set the status of the training to „Publish“, which transfers the changes you made to your production environment and enables you to apply the new version of your training to a new production cycle.

Example Workflow for editorial staff / computer linguists:

This feature improves your workflow quite a bit. First of all you can utilize the draft state to push your changes to the test environment.

Step by step:

You do this by committing a change to the Training.

After you implemented all changes into your training you can navigate to the tools menu, where you find the draft and publishing option.

By default all trainings are set to automatically be drafted as soon as a change in text or logic ruleset is detected.

40

This means all changes are instantaneously applied to your test environment.
If you want to gain further control in regard to your test content you can deactivate the automatic draft and instead use the manual button next to it.

06

When all your changes are on the testing environment, feel free to apply your respective quality assurance to ensure that no errors were implemented in the training.

34

If you have confirmed that no errors are left in the generated content, feel free to return to the tools menu and press „Publish Training“, thus transferring your changes to the public version of your collections.

After that, the content generation can begin and the content can be delivered to your productive infrastructure.

Requirements:

Set up your data sources
To setup the above workflow you need to configure your test and productive environment this can very easily be done by configuring your collections to draft or published mode.
To do this you navigate to a collection of your choice and start to edit it.
One option to choose is the used ruleset drop down in which two options exist:

Draft:

And published:

After you have set up your collections this way you are all set up to use the above workflow.

Roll Out

This feature has been active for quite some time now. We invite you to try it out as soon as an occasion arises. It would also be marvelous if you could provide us with feedback regarding your experience with the new functionalities.

Best regards
Niklas