Data validation quality checks

This section is used to document the validation and quality checks that are present in SDF manager tool.

Checks in Perform Checks menu

• Find sites that include species with unknown name
• Find sites that include species with unknown code
• Find sites that include birds with unknown name
• Find sites that include birds with unknown code
• Find sites that include other species with unknown name
• Find sites that include other species with unknown code
• Find sites that include unknown habitat types
• Find sites that include unknown habitat classes
• Find sites that include unknown NUTS regions

Checks performed by clicking on validate button when editing a site

• Checks if site compilation date is present
  • ✔: Check passed
  • ✘: Error in site validation
• If site compilation is not missing, checks if compilation date is before update date
  • ✔: Check passed
  • ✘: Error in site validation
• In Natura2000 mode: Checks if respondent name or e-mail is prenset (TODO: POSSIBLE IMPLEMENTATION ERROR - check for name isn't working)
  • ✔: Check passed
  • ✘: Error in site validation
• In Natura2000 mode: Checks if respondent address and admin unit are present (TODO: POSSIBLE IMPLEMENTATION ERROR - checks if both address AND admin unit are present)
  • ✔: Check passed
  • ✘: Error in site validation
• In Emerald mode: Checks if respondent address is present
  • ✔: Check passed
  • ✘: Error in site validation
• Checks if site type is present.
  • ✔: Check passed
  • ✘: Error in site validation

Checks Site classification dates

• In Natura2000 mode:
  • If type = A
    • Checks if date classificated as SPA in Identification section is present
      • ✔: Check passed
      • ✘: Error in site validation
  • If type = B
    • Checks if date proposed as SCI in Identification section is present
      • ✔: Check passed
      • ✘: Error in site validation
  • If type other than A or B
    • Checks if date classificated as SPA in Identification section is present
      • ✔: Check passed
      • ✘: Error in site validation
    • Checks if date proposed as SCI in Identification section is present
      • ✔: Check passed
      • ✘: Error in site validation
• In Emerald mode: Checks the chronological order of site ASCI dates in Identification section (proposedASCI < confirmedCandidateASCI < confirmedASCI < designatedASCI)
  • ✔: Check passed
  • ✘: Error in site validation
• Checks if site regions are present
  • ✔: Check passed
  • ✘: Error in site validation
• Checks if site biogeographical regions are present
  • ✔: Check passed
  • ✘: Error in site validation

Habitat checks

• If there are habitats defined, for each Habitat
  • Checks if the habitat code is present
    • ✔: Check passed
    • ✘: Error in site validation
  • Checks if the habitat representativity is present
    • ✔: Check passed
    • ✘: Error in site validation
  • If representativity other than "D"
    • Checks if Data quality is present
      • ✔: Check passed
      • ✘: Error in site validation
    • Checks if relative surface is present
      • ✔: Check passed
      • ✘: Error in site validation
    • Checks if conservation of the habitat is present
      • ✔: Check passed
      • ✘: Error in site validation
    • Checks if global of the habitat is present
      • ✔: Check passed
      • ✘: Error in site validation

Species checks

• If there are species defined, for each species
  • If Natura2000 mode: Checks if species group is present
    • ✔: Check passed
    • ✘: Error in site validation
  • Checks if species name is present
    • ✔: Check passed
    • ✘: Error in site validation
  • If Species population other than "D"
    • Checks if species data quality is present
      • ✔: Check passed
      • ✘: Error in site validation
    • Checks if species conservation is present
      • ✔: Check passed
      • ✘: Error in site validation
    • Checks if species isolation is present
      • ✔: Check passed
      • ✘: Error in site validation
    • Checks if species Global is present
      • ✔: Check passed
      • ✘: Error in site validation

Other species checks

• If there are other species defined, for each other species
  • Checks if group for the other species is present
    • ✔: Check passed
    • ✘: Error in site validation
  • Checks if scientific name for other species is missing
    • ✔: Check passed
    • ✘: Error in site validation

Other Generic checks

• Checks if habitats and species are present
  • ✔: Check passed
  • ✘: Error in site validation
• If Natura2000 mode and (site type = "A" or type = "C")
  • Checks If species group is "B"
    • ✔: Check passed
    • ✘: Error in site validation

Checks on Description tab

• Checks if Impacts are present
  • ✔: Check passed
  • ✘: Error in site validation
• If site Impacts are defined
  • For each impact
    • Checks if impact code is present
      • ✔: Check passed
      • ✘: Error in site validation
    • Checks if impact rank is present
      • ✔: Check passed
      • ✘: Error in site validation
    • Checks if impact occurrence is present
      • ✔: Check passed
      • ✘: Error in site validation
  • Checks if impact type is "P" or "N"
    • ✔: Check passed
    • ✘: Error in site validation

Checks on Protection tab

• If site relations are defined, for each relation
  • Checks if relation site name is present
    • ✔: Check passed
    • ✘: Error in site validation
  • Checks if relation type is present
    • ✔: Check passed
    • ✘: Error in site validation

Checks on Management tab

• Checks if management section is defined
• If site management is defined
  • For each body
    • Checks if body organisation is present
      • ✔: Check passed
      • ✘: Error in site validation
    • If body address is missing
      • Checks if body admin unit is present
        • ✔: Check passed
        • ✘: Error in site validation
  • If management status = "Y"
    • Checks if management plans is present
      • ✔: Check passed
      • ✘: Error in site validation

Checks Map section

• Checks if Site map section is present
  • ✔: Check passed
  • ✘: Error in site validation

Checks performed when trying to import files

• If XML radio button is selected
  • Checks if the file extension is an XML file
    • ✔: Check passed
    • ✘: Import stops immediately.
  • Checks if any sites are already stored in database
    • ✔: Check passed, then tries to Import data from XML to database.
    • ✘: Import stops immediately.
• If old MDB is selected
  • Checks if any sites are already stored in database
    • ✔: Check passed, tries to import each site
    • ✘: Logs already imported sites
  • If single site is selected
    • Checks if all tables are present in the selected ms-access database
      • ✔: Check passed
      • ✘: Import stops immediately.
    • Checks if the specific site is present in destination database
      • ✔: Check passed
      • ✘: Import stops immediately.
• If new MDB is selected
  • Checks if any sites are already stored in database
    • ✔: Check passed
    • ✘: Logs already imported sites

Checks performed when trying to export files

• If XML radio button is selected
  • Validates XML file with the selected dataflow schema
    • ✔: Check passed
    • ✘: Logs validation errors
• If MS-Access radio button is selected
  • Validates each site in a similar way like if the user had clicked on the validate button in the SDF Editor.
    • ✔: Check passed
    • ✘: Error in site validation