EPGRIS template - PowerPoint PPT Presentation

1 / 14
About This Presentation
Title:

EPGRIS template

Description:

NI code' to identify the data set. ISO 3166-1 3 digit country code ... downloadable institution and country codes. current country codes are only available in ... – PowerPoint PPT presentation

Number of Views:29
Avg rating:3.0/5.0
Slides: 15
Provided by: theovan
Category:
Tags: epgris | template

less

Transcript and Presenter's Notes

Title: EPGRIS template


1
(No Transcript)
2
EPGRIS half way project meeting
MCPDL v2
3
MCPDL v2
  • process compilation MCPDL v2
  • major changes in MCPDL v2 (compared to v1)
  • necessary additions for EURISCO data exchange

4
MCPDL v2
  • process compilation MCPDL v2
  • compilation draft based on input from EPGRIS
    (sep)
  • consolidated comments from the first regional
    EPGRIS meetings regarding the Multi Crop Passport
    Descriptor List
  • circulation draft to crop networks, CG centres
    and others involved in the discussion (oct)
  • compilation and distribution final version (dec)

5
MCPDL v2
  • major changes in MCPDL v2 (compared to v1)
  • principle
  • no separation FAO - IPGRI descriptors
  • keep it brief its no lecture PGR documentation
    (attempt failed)
  • introduction
  • multiple values separated by (no space)
  • missing values empty (ASCII) or NULL (database)
  • dates YYYYMMDD, missing parts with hyphens
  • latitude DDMMSSH , missing parts with hyphens
    (longitude similar)
  • country codes ISO 3166-1 plus deleted codes
  • institute codes FAO numeric (no reference to
    preliminary codes)
  • preferred language English

6
MCPDL v2
  • major deletions in MCPDL v2 (compared to v1)
  • availability of additional data (3 descriptors)
  • acquisition type of the accession

7
MCPDL v2
  • major additions in MCPDL v2
  • collecting institute code
  • species authority
  • subtaxa authority
  • common crop name
  • acquisition date
  • breeding institute code
  • ancestral data

8
MCPDL v2
  • major modifications in MCPDL v2
  • format dates, locations (see before)
  • biological status of sample
  • always a 3 digit code - several states added
  • levels of specificity (400 breeding/research
    material, 410 breeders line, 412 hybrid)
  • collecting/acquisition source
  • always two digit code - several states added
  • type of germplasm storage
  • always two digit code
  • remarks
  • only for 99 values, prefixed by fieldname

9
MCPDL v2
  • necessary additions for EURISCO data exchange
  • NI code to identify the data set
  • ISO 3166-1 3 digit country code
  • could also be part of the name of the data set
    (EURISCO_NLD.TXT)
  • record date to show the age of the information
  • could also be the date of the file or upload
  • accession link to link with additional data
  • can be rather long (www.cgn.wageningen-ur.nl/pgr/c
    ollections/passdeta.asp?accenumbCGN04848)

10
(No Transcript)
11
(No Transcript)
12
MCPDL v2
  • desired facilities
  • downloadable institution and country codes
  • current country codes are only available in html,
    to get the deleted codes one has to mail IPGRI
  • institution codes are downloadable for registered
    users only
  • on line data checker
  • send the data to address and receive directly
    automatically generated report

13
MCPDL v2
  • address codes
  • IPGRI / FAO considers it possible to add all
    addresses in the WIEWS Institute Table, even if
    it is used only once
  • some numbers
  • CGN has 2816 distinct address codes of which 399
    have a FAO code
  • current FAO list contains 8386 codes
  • if all genebank would add all their addresses the
    FAO list would explode
  • how to handle this problem?

14
MCPDL v2
  • Dear Theo,
  • I have gone through the recent "Progress in
    EURISCO" discussions with
  • Adriana and would like to make the following
    comments
  • I am happy to see that the MCPD seem to be useful
    for EURISCO and would like
  • to see all of the descriptors used in EURISCO, if
    possible. We wanted to
  • make progress on the development of the MCPD and
    have therefore included
  • some descriptors than are not (yet) standardized
    with the hope that through
  • their use we can eventually develop standards. If
    these descriptors are not
  • used in EURISCO it will be more difficult to
    develop standards.
  • ...
  • Best regards,
  • Thomas
Write a Comment
User Comments (0)
About PowerShow.com