Unified (Federated) Listing validation procedure

From wiki.gpii
Revision as of 09:46, 20 November 2012 by Valerio (talk | contribs) (Created page with "This page is used to work at the "validation procedure" that will be followed to store information on AT product in the Unified Listing database (also known as Solution Regist...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
This page is used to work at the "validation procedure" that will be followed to store information on AT product in the Unified Listing database (also known as Solution Registry). The figure below shows where the validation procedure fits in the connection scheme between EASTIN and the GPII Unified Listing.
Error creating thumbnail: Unable to save thumbnail to destination
.

1. Who will do the validation

validation is not completely automatic, it must be done by a human aided by automatic functions. He/she must be an expert in ICT assistive technology products; he/she should have a deep knowledge of the AT products available on the market (ideally have used most of them or have the possibility to test them in a Laboratory)

2. Steps of the validation procedure

the results of the query (i.e. the data retrieved form EASTIN) are analized by the validator that has to:

  1. decide what products are of interest for GPII unified listing (according to Inclusion/exclusion criteria described below)
  2. find out duplicated products (aided by automatic functions)
  3. information of duplicates is merged into one record (automatic procedure) that will include:
    • all the commercial names (alias)
    • all the manufacturer names (In principle only one manufacturer name should be present for a product. Anyway there might be the case of products whose manufacturer is not easily identifiable (in case of open source software for example)).
    • all the ISO codes
    • all the images
    • all the text descriptions
    • the sum of the detailed information
  4. Validator reads the merged information and, if needed, completes the data
  5. Validator adds settings for the product (automatically if the product is Cloud4all compliant??)