| | |
|---|
Catch up and progress update | | Liz - How does the system deal with plant and scion differently? Guy - We have entity Biomaterial that covers different types of sample sources. Detail to be discussed. Polyploid support - requires BE updates, volume depends on how much details will be supported ie just ingest allele calls OR info in the entire vcf incl. quality score etc. Set up a meeting asap in next two weeks with John, Susan and Tim to discuss in detail. Three months behind on contract. But both parties are flexible and are happy with progress. Need to meet end of the year to review objectives on contract.
|
Review results of Web framework technologies | @Yaw Nti-Addae | |
Review Web loader UI prototype
|
@Yaw Nti-Addae
| Theme should be driven by css so colour scheme and picture displayed in the application can be customised by institutes Currently user login is crop-based (individual user table in each crop database). Guy requested to have one user system shared by crops. User generally deals with multiple crops in PFR Current Portal is developed in html5. Portal can be redeveloped in Angular which would provide user authentication for Portal access. Job status application development in Angular in scope GOBii will work with graphic design expert on logos (and probably icons too if any) Some of the backend services for web loader already exist. The rest and also ones for Job status application require development Priority - Job Status BE, Loader FE, Job Status FE? All could happen in parallel if resources available Mock is written concept focused so look and feel is open for suggestion. Rule is to have uniform look and feel across all front ends Yaw presented new idea of the Master Wizard which leads user through the full process - Selecting or creating Project, Experiment and Dataset → Selecting or loading DNA Sample, Marker and Dataset → Validation → Proceed Guy suggested process in the Master Wizard to be customisable on deployment. Eg Institute might wish to disable DNA Sample loading feature in the loader for certain crops Since web loader will be used as exploration purpose, Guy suggested loader features should be under role-based control, esp Template creation. Suggested roles - Read, Create, Admin. Currently access to desktop loader requires curator role.
|
Review contract | @Elizabeth Jones | @Elizabeth Jones - Contract will be reviewed towards the end of year Both PFR and GOBii are content with progress of contract, although it’s 2 months behind schedule
|
Discuss joint development | @Guy Davenport (Deactivated) and @Elizabeth Jones | PFR Chetan - Lead FE Dev Hymmi - BA, Testing Gaurav - FE Dev Support Guy, Barry - BE Dev Support Lee / DevOps - Deployment Support Rest of the team - Support
GOBii Yaw Liz Angel - FE Dev Vishnu - BE Dev Deb - BA
|
Discuss deployment travel | @Elizabeth Jones | |