z-logo
Premium
Root‐Knot Nematode Interaction with Berseem Clover and Other Temperate Forage Legumes 1
Author(s) -
Baltensperger D. D.,
Quesenberry K. H.,
Dunn R. A.,
AbdElgawad M. M.
Publication year - 1985
Publication title -
crop science
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.76
H-Index - 147
eISSN - 1435-0653
pISSN - 0011-183X
DOI - 10.2135/cropsci1985.0011183x002500050029x
Subject(s) - trifolium alexandrinum , biology , agronomy , terra incognita , trifolium subterraneum , population , meloidogyne incognita , medicago sativa , forage , nematode , ecology , demography , sociology , pasture
Potential acreage of berseem clover has been increased by the recent release of ‘Bigbee’ berseem clover ( Trifolium alexandrinum L.). Bigbee berseem clover was evaluated to determine if root‐knot nematodes ( Meloidogyne arenaria, M. incognita , and M. javanica ) may be a limiting factor in new berseem production areas compared with other legumes with similar geographic adaptation. Root‐knot nematode interaction with 15 other germplasm sources of berseem clover was also evaluated in at least one of three separate tests. Eight berseem germplasms were severely galled by the mixed population of Meloidogyne spp. present in the field test. All nine germplasm sources of berseem clover, including Bigbee, were severely galled by M. arenaria , M. javanica , and M. incognita race 3 in the two greenhouse experiments. Gall scores were not significantly different than for the known susceptible host ‘Amclo’ arrowleaf clover ( T. vesiculosum Savi.), but were signficantly more severe than for ‘Dixie’ crimsom clover ( T. incarnatum L.). ‘Florida 77’ alfalfa ( Medicago sativa L.) proved to be highly resistant to all three Meloidogyne species studied. Field investigations are needed to determine if root‐knot nematodes would limit the production of Bigbee berseem clover similarly to the way they limit production of arrowleaf clover.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here