HD DCD XLSForm Conventions

Naming convention of the files

"HD_DCD_SPEC_HDBPXXXX_ABBREV_DCD1_VXX_DDMMYYYY"

• HDBPXXXX : authentic source: T_PROJ_BUS.xlsx?
• ABBREV : authentic source: T_PROJ_BUS.xlsx?
• DCD1 : no "name" or abbreviation of DCD, but just "DCD+ number" Then we might need an index somewhere showing the link between number and DCD name?
• VXX : the version of the DCD Can we stick to "x" and small v, for example v1 like it is displayed in HD4DP2 (not V01)?
• DDMMYYYY : date of the version of the DCD Can we stick to YYYYMMDD in line with earlier file naming convention? To be more precise: this will be the date stamp of the document version. I.e. one version of a DCD can have multiple document versions (typo correction , additional validation rule, additional code list option)

Multiple DCD convention

For each DCD, a seperate XLSForm is created and maintained in the relevant HDBPxxxx folder at https://www.dropbox.com/home/HD_DCD/.

Versioning

Workspace

• Conventions regarding the use of XLSForm (in progress)