Skip to content

Qualiservice file naming conventions

QualiService provides conventions for file names (TBD). Here is an excerpt of the most important content:

The file names should be standardized across all projects. The following scheme can be used as a guide:

ProjectID_Data-type_Assignment-by-organization_Further-specifications

(e.g. consecutive number or name of the research participant + interview number)

  • ProjectID:
  • first position should always contain an assignment of the file to a project.
  • The project name or ID is identical for all files in a project. Each project is given its own project ID. This is developed manually from the initials of the project and is intended to ensure the recognition value of all files belonging to a project during data management. As already described, the project ID occupies the first position in the name of all associated files. Project IDs are unique and project-specific. It is therefore not permitted to assign more than one ID per project or to use one ID for several projects at the same time.
  • Data-type: provides information on the data type,
  • Assignment-by-organization: cohort or the organization of the interviewee
  • Further-specifications: e.g. the specific research participant and interview.

Example: SVB_IT-U_01_C102-01

  • SVB: ProjectID - The accronym refers to Soziale Verantwortung im Beruf
  • IT-U: Data-type
  • 01: Assignment-by-organization - It refers to the first interviewed/inquired organization in the project.
  • C102-01: Identification of participant (C102) and interview (01 - as it is the first interview with this interviewee)

Please note that the four positions in the file name are always separated by an underscore. Neither spaces nor other punctuation marks may be used as separators. The underscore may only be used to separate two positions. However, the four positions are defined flexibly and can therefore vary in length depending on the project and data type. Nevertheless, the recognition value and assignability of a file within a project should be guaranteed by the file name. In this respect, as much uniformity as possible should be created in the file names for each project.