-
Notifications
You must be signed in to change notification settings - Fork 9
Table Requirements
Andy edited this page Apr 28, 2016
·
1 revision
general requirements
- the tables should be in german
nominal and ordinal variables with <=20 values
- the table consists of the attributes: Code (Values); Label; Frequencies; Percent; Valid Percent; sum (valid); sum (total).
- valid and missing values should be seperated in the backend via the missing attribute ("missing":true/false)
- missing values should be situated below the valid values and seperated by \hline ( see also example table, sheet Tabellen Layout )
nominal (and ordinal) variables with >20 values
- use the table for nomial/ordinal variables as defined above
- if a variable has more than 20 values display only the first and last 10 values and seperate them with one line consiting of three dots (...) (see also example table, sheet Tabellen Layout )
metric variables
we upated our decisions concering tables for metric variables
- there should be a table for metric variables with reduced informations in the valid section and full information in the missing section.
- for the valid cases the table should onyl include the total number of cases
- for the missing cases the table should include the differentiated missing codes with corresponding case numbers
- the bottom line of the table should include the total number of cases (valid and missing)
- the table should include a cloumn with percentages (including all cases)
see also example table, sheet Tabellen Layout
Developer Docs
- Entwickler:innen-Doku
- Scrum Artifacts
- Architecture
- Domain
- Search
- UI
- DevOps Process
- Authentication and Authorization
User Docs
- ID-Generation
- Metadata Import
- Metadata and DOI registration at dara
- PID Registration
- Variable (Data Set) Reports
- Übersicht R-Scripte
- Web Analytics