Difference between revisions of "Data Entry Form Uncategorised"

From IMSMA Wiki
Jump to: navigation, search
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Note | The table is called ''fieldreport'' and it cannot have CDFs.}}
+
{{Note | The table is called ''fieldreport'' and it cannot have CDFs. The maXML artifact is [[FieldReportInfo Artifact|FieldReportInfo]].
 +
''Date of Information'' and ''Form ID'' are vital for the function of {{IMSMANG}} and should always be filled in. The easiest way to ensure that is to included them as '''required''' fields in all Date Entry Form templates.}}
 
{|
 
{|
 
|- valign="top"
 
|- valign="top"
Line 12: Line 13:
 
| - || Text ||  comment ||  || Comment
 
| - || Text ||  comment ||  || Comment
 
|-
 
|-
| Data Enterer || String ||  DataEnterer ||  || DataEnterer
+
| Data Enterer || String ||  dataenterer||  || DataEnterer
 
|-
 
|-
| '''Last updated''' || Date ||  DataEntryDate ||  || DataEntryDate
+
| '''Last updated''' || Date ||  dataentrydate||  || DataEntryDate
 
|-
 
|-
| Date of Information || Date ||  DateOfReport ||  || DateOfReport
+
| Date of Information || Date ||  dateofreport||  || DateOfReport
 
|-
 
|-
| Form ID || String ||  FieldReport_LocalID ||  || LocalId
+
| Form ID || String ||  fieldreport_localid||  || LocalId
 
|-
 
|-
| Data Entry Form Template || String ||  FieldReportDesc_GUID ||  || Fieldreportdesc
+
| Data Entry Form Template || String ||  fieldreportdesc_guid||  || Fieldreportdesc
 
|-
 
|-
 
| - || Text ||  import_errors ||  || ImportErrorsText
 
| - || Text ||  import_errors ||  || ImportErrorsText
Line 28: Line 29:
 
| Submitted Date || Date ||  reportcompleteddate ||  || ReportCompletedDate
 
| Submitted Date || Date ||  reportcompleteddate ||  || ReportCompletedDate
 
|-
 
|-
| Reported by || Text ||  ReportedBy ||  || ReportedBy
+
| Reported by || Text ||  reportedby||  || ReportedBy
 
|-
 
|-
 
| Reported by position || String ||  reportedbyposition ||  || ReportedByPosition
 
| Reported by position || String ||  reportedbyposition ||  || ReportedByPosition
Line 38: Line 39:
 
| ''Approved by'' || String ||  verifiedby ||  || VerifiedBy
 
| ''Approved by'' || String ||  verifiedby ||  || VerifiedBy
 
|-
 
|-
| Data Entry Form Status || Single-select ||  WorkbenchStatusEnum_GUID || Workbench Status || WorkbenchStatus
+
| Data Entry Form Status || Single-select ||  workbenchstatusenum_guid|| Workbench Status || WorkbenchStatus
 
|}
 
|}
 
|}
 
|}
 
{{NavBox Data Dictionary}}
 
{{NavBox Data Dictionary}}
 
[[Category:NAA]]
 
[[Category:NAA]]

Latest revision as of 22:01, 19 June 2017

Note.jpg The table is called fieldreport and it cannot have CDFs. The maXML artifact is FieldReportInfo.

Date of Information and Form ID are vital for the function of IMSMANG and should always be filled in. The easiest way to ensure that is to included them as required fields in all Date Entry Form templates.

User portal.png

DIM Label Data type Database column name Enumcategory Pojo name
Approvable Boolean approvable Approvable
- Text comment Comment
Data Enterer String dataenterer DataEnterer
Last updated Date dataentrydate DataEntryDate
Date of Information Date dateofreport DateOfReport
Form ID String fieldreport_localid LocalId
Data Entry Form Template String fieldreportdesc_guid Fieldreportdesc
- Text import_errors ImportErrorsText
Import Issues Boolean import_errors_unresolved UnresolvedImportErrorsExist
Submitted Date Date reportcompleteddate ReportCompletedDate
Reported by Text reportedby ReportedBy
Reported by position String reportedbyposition ReportedByPosition
Data Entry Date Date reportreceiveddate ReportReceivedDate
Approved Date Date reportverifieddate ReportVerifiedDate
Approved by String verifiedby VerifiedBy
Data Entry Form Status Single-select workbenchstatusenum_guid Workbench Status WorkbenchStatus