This paper is part of a series that focuses on DDI usage and how the metadata specification should be applied in a variety of settings by a variety of organizations and individuals. Support for this working paper series was provided by the authors' home institutions; by GESISLeibniz Institute for the Social Sciences; by Schloss Dagstuhl -Leibniz Center for Informatics; and by the DDI Alliance. B Y A L E R K A M I N W I T H M I C H E L L E E D W A R D S , O L I V E R H O P T , J A N N I K J E N S E N , D A N K R I S T I A N S E N , O L O F O L S S O N A N D J O A C H I M W A C K E R O W ABSTRACTQuestasy is a Web application developed to manage the dissemination of data and metadata for panel surveys. It was primarily developed for the LISS Data Archive, but was designed to be repurposed for other surveys. The structure of the application, from the underlying database to the generated Web pages, is based on DDI 3. This paper describes how Questasy was designed and implemented.
This paper is part of a series that focuses on DDI usage and how the metadata specification should be applied in a variety of settings by a variety of organizations and individuals. Support for this working Building a Modular DDI 3 Editor B Y J A N N I K J E N S E N A N D D A N K R I S T I A N S E N W I T H A L E R K A M I N , A R O F A N G R E G O R Y , A G O S T I N A M A R T I N E Z , M A R T I N M E C H T E L , M A R Y V A R D I G A N , A N D W O L F G A N G Z E N K -M Ö L T G E N ABSTRACTDevelopers at the Danish Data Archive (DDA) have built an open source DDI 3 editor using a layered architecture. The tool plays a critical role in the work flow at the DDA, providing needed integration of information. The design decisions made during development may be instructive for others building tools based on DDI 3.
Intended audience:This document is for software designers who are developing DDI applications. The designers may be familiar or unfamiliar with the DDI specification. Abstract:This best practices document looks at a possible way to design components that can be combined to create DDI applications. Given that object-oriented design is the most common programming paradigm, and that systems are often based around service-oriented principles, and given the modular design of DDI 3.0 itself, this document provides an architectural model that can be a reference point for implementers. The document also takes into consideration issues of maintenance and management of DDI applications, and discusses best practices for application documentation and configuration. The focus is on interoperability of DDI applications. Status:This document is updated periodically on no particular schedule. IntroductionThis best practices document looks at a possible way to design components that can be combined to create DDI applications. The paper is targeted at developers, but it does not assume a high level of DDI knowledge. It is intended to serve as a starting point for developers new to the DDI. Problem statement 50Software developers who are new to the DDI 3.0 standard may find the standard daunting. This best practices document provides an overview of how an application may be structured so that developers have a starting point for the design of their application. Terminology Definitions59 DDI: When used without a version, DDI refers to the latest DDI specification, currently version 3.0. When older versions are referenced, the version number will be explicitly specified.DDI community: Any person or organization working with the DDI specification.DDI application: A software application that reads and/or writes DDI XML.Specification: The DDI specification.Component: A piece of software with a specific purpose with a well-defined input and welldefined output.Middleware: In the context of this best practices paper, middleware refers to utilities that manage the interface between the DDI metadata model and application services or high-level end-user tools.Task: An activity that a person undertakes in order to create, edit, or view documentation about data.End user: Person performing work in the data life cycle for whom DDI metadata is required. The end user will likely not even be aware of the DDI metadata in the application he or she is using.
This paper is part of a series that focuses on DDI usage and how the metadata specification should be applied in a variety of settings by a variety of organizations and individuals. Support for this working paper series was provided by the authors' home institutions; by GESISLeibniz Institute for the Social Sciences; by Schloss Dagstuhl -Leibniz Center for Informatics; and by the DDI Alliance. ABSTRACTA questionnaire is usually revised several times during construction, and documenting those revisions in detail is important for understanding the lineage of the questions asked and for further questionnaire development in future studies. This documentation is also indispensable for teaching survey research methods.Nonetheless, this documentation is usually done only partially or not at all, due to a lack of useful documentation tools. The aim of the Questionnaire Development Documentation project was the development of a system to permit permanent electronic documentation of questionnaire development and the final state of the instrument.QDDS is a useful and effective system but may be improved by moving to DDI 3 to take advantage of enhanced functionality, especially in terms of versioning. DDI 3 also has the potential to provide the framework for a question bank.
No abstract
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.
hi@scite.ai
10624 S. Eastern Ave., Ste. A-614
Henderson, NV 89052, USA
Copyright © 2024 scite LLC. All rights reserved.
Made with 💙 for researchers
Part of the Research Solutions Family.