Talk:TDM Breeders Training Course 5.4

From ICISWiki

Jump to: navigation, search

How can we improve the training?

1. Currently the training is conducted as a demo of what the exercise is. And often, trainors are limited to just speak about the steps and not what are those forms for, nor what can be done through them.

Suggested approach:


  • At the start of each topic, explain what the form is for. Different used-cases.
  • like for import list, it is not only used for batch creation of germplasm, but also for creation of lists with germplasms that have already been in the GMS(import by GID), it can only be used to attach information(names, attributes, etc )).
  • Another example is when creating a HB list, there are many ways to add a germplasm. Ie. Via ‘+’, which could be:
a. entirely new germplasm,
b. a germplasm name that was attached to many GIDs
c. adding a GID
d. add a germplasm from Browse window
e. insert a germplasm from browse


This can be approached in a general way, but what is important is to be able to present the “power” of each form/process.


  • Do a walk-through of the process/es either with the used-cases OR the actual exercise.


  • Allow the users to do the exercise.


2. It is also nice to make each training interactive. Arllet is good at doing this(when doing the retriever), asking trainees what sort of things they want to query in their jobs. or for breeders, the usual methods they use.

3. Add training/demo for the following topics:

  • Setgen
a. Germplasm operations(Edit, Delete, Change), view characteristics
b. List operations – delete, lock, export, hide/unhide, print, Fill up columns including SAVE as nametype/attribute
c. Customizing Launcher
d. Right-click menu on the Edit window


  • GMSSearch
a. how to search, options
b. information displayed on this form, Derivative/mgt neighborhood, relatives, descendants, etc


  • Workbook
a. show the different shortcuts/functions.
b. the different scenarios where a workbook can be used.(to store experimental data, to store values for Batch processing, etc)


  • Etc
a. Submitting bugs in cropforge
b. Navigating the cropwiki


3. Explain “concepts”, naming conventions used/enforced in ICIS,

  • Lists – What are these? how should they design their lists? Why germplasms are grouped in a list?
  • Methods – Generative, Derivative, (Management), what are these
  • Dashes (-) and Slashes(/) and other conventions used in ICIS


4. A model for breeding project for training was introduced at the start of the course, BUT it will also be good to present other Model for which ICIS(molecular, maintenance of seeds etc) can be used.

  • Also it will be nice to have ICIS training focused on different models.
  • Or a day that users will use their own data to do ICIS(a breakout session)


5. Technical aspects.

  • What is being projected is not clear from the 2nd last row (Burma Room, IRRI Training Center). Make the training demo appear on each monitor. So that the trainees will really ‘see’ the demo.
  • Some speakers not too audible


6. Some of the users are ‘advanced’ or were previously introduced to ICIS. But there are those who are completely new. Maybe, allot an optional day (ahead of the actual training) as an ‘orientation’ day for those who are completely new?


7. Allot a day to teach how to start-up ICIS in their own institute. They have questions on “where and how do we begin using ICIS if we are not in RICE or Wheat”? “what if we have a blank database”


8. Train the trainors

Less IT/technical language. It seems that the trainors lack the exposure to the field. They usually are limited to use the IT/ICIS technical terms. It'll be better if the trainors know 'field/laboratory' terms as well.


9. Train (or discuss with) the OU Heads.

Some of the trainees expressed that it is better to have a discussion with the Heads of the OU first. This is to decide conventions/methods first. Because once they finish the training and present their suggestions to their OU heads, often they are faced with a blank face. The OU process should be documented and not tied to the current employee who is the ICIS user.


10. Add Extra exercises for more practice, specifically for 'fast-learner' users


11. Advanced training for ICIS - level up the basic training :) Suggested topics:

  • Administering ICIS - HW/ platforms/ODBC/etc
  • Configuring ICIS (INI), and Setting up ICIS from scratch (UDFLDS, Methods, c. Scales, list types etc)
  • Deciding and set-up of user access
  • Curating data
  • Advanced features(Fill-up columns, add extra columns, Mx, search relatives, batch processes)


12. Prior to training, assess the background/experience of the trainees


13. Timekeeping:

  • Stick to the schedule
  • If there are changes in the schedule, give participants an updated copy of the schedule and stick to it.
  • Finish training by noon on the last day OR make it mandatory for participants not to leave by friday afternoon.
Personal tools