Skip to content
This repository has been archived by the owner on Aug 26, 2022. It is now read-only.

Roadmap

Christian Gendreau edited this page Mar 20, 2017 · 4 revisions

Project milestones (Roadmap)

Table of Contents

Introduction

Below is a list of project milestones for the GBIF Data Validator tool. Each milestone consists of a list of requirements. Upon completion of a milestone, the product owner and testers will verify that each requirement has been implemented and is working as expected.

Milestone 1 - API functionality

See here

Milestone 2 - Existing UI functionality

Summary: The tool should cover all existing UI functionality that the Darwin Core Archive Validator (2013) currently offers users.

Due date: 31 December, 2017

Requirements:

  • Landing (home) page requirements:
    • The page explains what the tool can be used for and how to use it
    • The page allows users to validate a DwC-A via file upload, up to 100MB in size
    • The page allows users to validate a DwC-A by specifying its location online (URL) with no limit in their size.
  • The validation report page requirements:
    • Shows archive source
    • Shows date validated
    • Shows meta.xml file validation results
    • Shows metadata file validation results, with overview of
      • important fields such as title, description, license, contacts, citation, etc.
    • Shows mapping validation results for each archive file, with overview of:
      • which GBIF registered extension the mapping corresponds to
      • which column is the core/ID column
      • which columns were mapped to valid concepts in the latest version of a GBIF registered extension
    • Shows summary for each archive file, with overview of:
      • how many records the file contains
      • how many columns it contains
      • whether all records have the same number of columns or not
      • whether all extension records refer to a core record (referential integrity)
    • Shows referential integrity validation results:
      • between core and extension records
      • between additional ID terms (e.g. each parentNameUsageID has a corresponding acceptedNameUsageID)
    • Visualise first 100 records, showing the complete one-to-many relationship for each record in tabular format