You can only access the EBS if your name and email address are already registered in the system. If you’re not sure if your account is already made, contact the person in charge of registering EBS accounts in your organization. Once your account is secured, only then can you log in. For the step-by-step process of logging in, you may refer to this guide.

Make sure that you are accessing the EBS using the email that was registered in the system to create your account. If you’re not able to log in, it’s possible that (1) you don't have an EBS account yet or (2) you’re using a different email from the one registered in the system. Either way, check with your administrator about your account details.

First, you should have an account made by the person in charge of creating EBS accounts in your organization. For the step-by-step use of the EBS tools, you may refer to the /wiki/spaces/EBSDrafts/pages/29277880913. Currently, we only have the EBS Core-Breeding but the rest of the tools are underway.

To have a good start on the EBS Core Breeding, we highly encourage that you get familiar with its workflows and some key terms that are used in the tool. In that case, you may refer to the EBS Overview guide to get you started.

You can only finalize your experiment if all of your entries have a designated package or seed source. In the Entries tab, you can check the Availability column and ensure that each entry has a

An

There are two ways to troubleshoot this issue:

1. Check if you already finalized the experiment in the Experiment Creation tool. Once done, the experiments can be accessed in the Experiment Manager tool, or

2. Check if you are using the correct data filter for your program by viewing the program’s acronym displayed in the menu bar. If the program is incorrect, you can change it using the data filter () icon.

A 504 error may be a temporary error caused by a high volume of traffic towards the server or site. You may want to try again later or submit an ESD ticket for further assistance if the problem persists.

This status indicates that the harvest record creation was unsuccessful. You can check if you have incompatible data (e.g., no recurrent parent found for backcross) in the affected plot/cross. If the error persists, send a support ticket in the ESD.

You can see this information in the Inventory Manager tool. if you are expecting to receive packages from another program, you can see a transaction record in the Seed Transfer tab’s data browser. Once the transaction status is set to

Missing field layout coordinates might mean that you did not tick the checkbox for "Design layout matches Planting area and Field layout" when you generated the location. You can still upload your field coordinates by downloading () the mapping file of the occurrence you wish to fill-out and then uploading it back to EBS. You can download the mapping file from the Experiment Manager toolbar or data browser.

Missing design arrays in your occurrence might mean that you did not tick the “Define dimension” checkbox during the experiment creation process in the Experiment Creation tool’s planting arrangement step.

The status indicates that your upload transaction encountered some issues. You can delete () the upload transaction in the data browser and re-upload your data collection file.

You can only commit your harvest if you have provided the following data required for each crop:

• Rice

  • Crossing date for crosses

  • Harvest date for plots

• Maize

  • Harvest date and harvest method for plots and crosses

• Wheat

  • Harvest date and harvest method for plots and crosses

Good catch! This is due to data issues in the tool. Using these occurrences for analyses will only result to

To resolve this, please let us know by reporting the issue as bug as soon as you encounter them.

You can get the latest features, improvements, and bug fixes from the EBS Production Release Notes. Developments done for all EBS tools per version are regularly published in the resource.

The updates are regularly communicated to EBS users through virtual and face-to-face information sessions. Email invitations are sent to participants ahead of time. As an EBS user, you can also be notified of any recent publication via email.

For bugs and feature requests, report your issue to the EBS Service Desk.

If you want to have support or assistance as you use the EBS, report your issue to the EBS Service Desk.

If you wish to have training for your group, you may send your request to the EBS Service Desk. Watch out also for our upcoming eLearning course which is part of our training initiative to get you equipped in the EBS.

For everything you need to get started on the EBS, refer to our EBS Guide.

You may find the latest features, improvements, and fixes on the EBS on the EBS Releases Notes.