All Projects

IDProjectCategoryTask TypeSeveritySummaryStatusProgress  desc
148ManagerDrag & DropBug ReportLowTime field in EpiData ManagerWaiting on Feedback
0%
Task Description

EpiData Manager
Program Version: 2.0.2.28 r1115
Core version: 2.0.0.0 r1126
FPC Version: 2.6.4
Platform: x86_64-Win64

I have a time field on opening a new record and a time field on first save.

1) It is unclear where and how to put the interval calculation, if the second to last field is one that either jumps to save record or goes to the last field
2) In analysis, the two fields are read as floats and have the form 0.852616. It is not clear what this is. Assuming that it could be a fraction of the day (as in EpiData Entry 3.1), I multiply (end-start)*86400 but the result does not make sense, giving something like 22.98 up to 73.01. I doubt that I took that many seconds (should be more like in the order of 10 seconds per record)

158ManagerFunctionalityFeature RequestLowjump based on value on other dataformAssigned
0%
1 Task Description

Details
Currently jumps can only be defined based on fields on current dataform

Sometimes the field to reference is on another dataform.

Jumps should therefore be possible such as:

dataform1 fields v1 v2 v3
dataform2 fields v17 v19 v21

From field dataform1.v2 we wish to jump to dataform2.v21 if dataform1.v2 is = 1
From field dataform1.v2 we wish to jump to dataform2.v17 if dataform1.v2 is <> 1

160ManagerOtherBug ReportLowManager/EntryClient preference fonts sometimes impose b...Assigned
0%
Task Description

EpiData Manager: (2015/10/16 - 14:44:50)
Program Version: 2.0.7.53 r1213
Core version: 2.0.0.0 r1206
FPC Version: 2.6.4
Platform: i386-Darwin
(same behaviour with EntryClient)

For some fonts (e.g. Menlo on my MacBook - el Capitan OS), Manager imposes bold/italic even though I request regular. I wonder if there is something different about the new fonts (Menlo) in el Capitan.

I cannot find where the font preferences are stored (not in com.company.epidatamanager.plist)

165Manager"Document"Feature RequestLowGCP Report on specific recordAssigned
0%
Task Description

We need a report which can print the content of a single parent record and ALL records in child datasets related to the parent record.

178ManagerOtherBug ReportMediumExport to Stata - missing values incorrectAssigned
0%
1 Task Description

See attached .epx

Export to Stata (tested with V8 and V12) does not use Stata missing values for declared missing data (i.e. data matching one of the missing value label values).

System missing fields are always exported properly and recognized as system missing in Stata.

In this test file:
missing value of 9 / 99 in a 1 / 2 digit integer has value 100 in Stata, while the value labels include large values as missing
*** 100 is the largest legal number in byte data; first missing value (corresponding to Epidata system missing) is 101
missing value of 999 / 9999 in a 3 / 4 digit integer has value 32740, with the same large values as missing
*** 32740 is the largest legal number in small integer data; first missing value (corresponding to Epidata system missing) is 324701
value labels have the value 132417700 for the missing values of (8 / 88 / 888 / 8888)
and the value 132417701 for the missing values of (9/ 99 / 999 / 9999 )

With larger integers (5+ digits), the value labels for missing also follow this pattern, but at least the data are coded to match the new missing values.

**The bug**: declared missing values in the data should match the value label for that type of missing data.

While the user should be able to adapt to this by deleting the missing data values in analysis, it would make most sense to retain the original values.

**The feature request**: perhaps as an option, transform all declared missing values to Stata's missing values that represent .a, .b, .c, etc.
so for byte data, system missing remains 101, first missing value becomes 102 (.a), next becomes 103 (.b), etc.
for small integers (3-4 digits), system missing remains 32741, first missing becomes 32742 (.a), etc.
for long integers (5 and up), system and declared missing should match the .dta specification:

maximum nonmissing +2,147,483,620 (0x7fffffe4)
code for . +2,147,483,621 (0x7fffffe5)
code for .a +2,147,483,622 (0x7fffffe6)
code for .b +2,147,483,623 (0x7fffffe7)
...
While value labels for floats are not exported, they can also follow the same pattern for missing values (e.g. properties of the field include a range and declared missing values)

----------- Output from Analysis after reading the Stata 8/9 export file -------------
.list v;
Name Type Length Decimal Label Valuelabels Missing
V1 Integer 3 0 1 digit 1 = OK
2 = OK too
134217700 = N/A
134217701 = Missing
V2 Integer 3 0 2 digits 134217700 = N/A
134217701 = Missing
1 = OK
2 = OK too
V3 Integer 5 0 3 digits 1 = OK
2 = OK too
134217700 = N/A
134217701 = Missing
V4 Integer 5 0 4 digits 1 = OK
2 = OK too
134217700 = N/A
134217701 = Missing
V5 Integer 10 0 5 digits 1 = OK
2 = OK too
134217700 = N/A
134217701 = Missing
V6 Float 18 4 float 5.2
V7 Float 18 4 float 12.8
V8 String 207 0 text
V9 Date (DMY) 10 0 date
V10 Float 18 4 time
V11 Integer 3 0 boolean

.list vl;
_V1 (Integer)
Value Label Missing
1 OK
2 OK too
134217700 N/A
134217701 Missing

_V2 (Integer)
Value Label Missing
134217700 N/A
134217701 Missing
1 OK
2 OK too

_V3 (Integer)
Value Label Missing
1 OK
2 OK too
134217700 N/A
134217701 Missing

_V4 (Integer)
Value Label Missing
1 OK
2 OK too
134217700 N/A
134217701 Missing

_V5 (Integer)
Value Label Missing
1 OK
2 OK too
134217700 N/A
134217701 Missing

.list data !vl; // data as read into Analysis; this matches exactly data as read into R
Obs. No 1 digit 2 digits 3 digits 4 digits 5 digits float 5.2 float 12.8 text date time boolean
1 1 OK 1 OK 1 OK 1 OK 1 OK 1 1 abcdefg 24/10/2017 43200000 1
2 2 OK too 2 OK too 2 OK too 2 OK too 2 OK too 2 2 ccc 11/10/2017 43200000 0
3 100 100 32740 32740 134217700 N/A 99.99 999.99999999 . . .
4 . . . . 134217701 Missing . . . . .
5 . . . . . . . . . .

179ManagerFunctionalityFeature RequestLowContent of a Textfield in PicklistAssigned
0%
Task Description

Description:
In a Trial we have to compile used substances for Drug-consumption.
Therefore a textfield is appointed. In Statistics we need a categorized numeric field with collected Text as Labels.
(In Stata-> encode , in SPSS-> autorecode)
But incorrect input (for example different shifted input, some uses abbreviations othes not ect.) creates more categories then needed.

Feature Request:
It would be nice, to have an "advanced Textfield" . You enter an item, which is choosable for coming enters, like a dropdownfield or a picklist.
This field should be exportet as an Integer with Labels.

214ManagerOtherBug ReportMediumManager: With Cocoa widgetset, Copy a field failsAssigned
0%
Task Description

Situation: Select one or more fields, Edit, Copy leads to fatal error

Format for the copy operation is not registered.

in /Library/Lazarus/lcl/interfaces/cocoa/cocoaWSClipboard.pas
Failure at line 329, because lCurFormat points to invalid location

Is this a Cocoa bug? Not sure where the formats are to be registered.

57Test ProjectBackend / CoreBug ReportLowtesting notificationsResearching
0%
Task Description

asdfasdfasdfasdfasdfasdf

Showing tasks 51 - 58 of 58 Page 2 of 2 - 1 - 2

Available keyboard shortcuts

Tasklist

Task Details

Task Editing