This project has received funding from the European Union’s FP7 Infrastructures programme under grant agreement No 283646 and the European Union’s Horizon 2020 research and innovation programme under grant agreement No 654221.

The EC is not responsible for the content of this site. Neither the EC nor the project beneficiaries are liable for any use made of the information contained herein or for the content of linked external websites or pages.

The key aim of the DASISH QDDT is to provide a system for developing and documenting the entire questionnaire development of cross-national survey programmes, from the first concepts and questions to the final questionnaire. This will improve not only the quality and transparency, but also the efficiency, of the questionnaire design process. The requirements for the QDDT are defined as follows:

• The system can handle differing amounts of information at different times during the design process.
• Internal users can use the tool to document the question design process, whilst external users can use it to understand how each item and concept was developed
• Different levels of access rights can be awarded to different users
• Once the design for a module in a round has been completed, the information can be made available for download and be permanently stored in the database for future use and reference.
• Compatibility with the DDI-Lifecycle is achieved, to allow for interoperability with other tools and systems.
• A system architecture that enables easy exchange of metadata in DDI format to other task 3.2 tools has been built.
• This should comprehend file-based import and export, as well as communication by web-services.
• The QDDT has been tested for compliance with the identified use cases by members of WP3.2 as well as by selected external persons.

This project was generated with Angular CLI version 6.0.0

Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.

Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the -prod flag for a production build.

Run ng test to execute the unit tests via Karma.

Run ng e2e to execute the end-to-end tests via Protractor.

To get more help on the Angular CLI use ng help or go check out the Angular CLI README.