2020-04-03 Meeting notes

Demo of Fieldbook

Pete

• ·        Field Book - Authorization similar to Oauth2 for BrAPI calls

  ·        Need to add a notification that upload successful? - see this data and needs reviewing or QC in BMS and B4R. Need to review data first? - can be done in BMS and B4R

  ·        Trial with multiple locations - is there an option to select a location? Each study is a single location. Need to consider this. Mariano - having mechanism to filter fields would be good.

Feedback from BMS

Mariano

·        They are implementing calls to have Field Book function with BrAPI. Have problem with way calls are being invoked from Field Book. All GET calls require client to pass a token but this is not happening.  So will try and create a PULL request in Github for this change.  Pete can help with this.

·        In BMS they have the breeder validate the incoming data - so data has a status of unvalidated until breeder reviews it.  While data is unvalidated it is not available for any downstream analysis or reports. B4R also has this status 'QC'

Feedback from B4R/EBS

Marko

·        Started using Field Book. Using the csv download and upload. Select study and traits and export the csv. User saves csv study and trait file and saves on google docs ahead of data collection. The collects data and saves on google drive. Upload later to a QC staging area in B4R. Can suppress values if they want to.  Not available for data analysis until QCd.

·        Pete - any plans to use BrAPI for upload and download? Marko - for next season hope to use this in EBS with WSO2.  Need to make sure BrAPI works with WSO2. Tim - seems like there is support in WSO2

·        Would like more features for filtering studies and data - how do we make that request to Field Book? Pete- open an issue on github to record it. Who is actively developing? Trevor - is aware of limitations for filtering and multiple field reps. Best way to get it done is to contribute code.

·        Marko - when export data does it export everything? Or just the new data observations? Trevor - always exports everything. Marko - would be good to just export new data to minimize data transfer.  Users have to export every day so lots of data being transferred. Pete - exporting everything is just for csv files. With BrAPI just exporting new values. Trevor - won't be difficult to just export new data for csvs too.

Feedback from BI

Moira

·        BI - actively getting users to use Field Book as a stand alone. Standing up Breedbase instances is taking a while due to ontology discussions. 

·        Looking at integrating Field Book with Vitagen database for grape breeders. 

·        Issues eg perennial crops - data collection over years on same field location - need development for this scenario. Also have fish data and not sure how to integrated phenotyping for this. Will gather requirements and then set up a hackathon.

Fieldbook priorities

Trevor

·        Priorities - supposed to have a developer start in May, but have hiring freeze. Petitioning to have the position hired.

·        Now prioritizing geonavigate features. Catching up on fixing bugs etc.

·        Next big thing - overhaul of traits, how they are managed, database structure to be more BrAPI friendly. Change some export features in UI. In github have feature branch being worked on: right now working on  'quality of life'.

·        Happy to work with other developers to get features done eg BI leading the BrAPI uploads from Field Book. Japanese visitors improved code when they were here. BMS working on BrAPI tokens not currently included in calls.