25 Feb 2022, 14:53
1st SAAOP AOP Community of Practice Symposium – Day 3, Breakout group 3, 22.2.22, 11.00-12.00 (CET)
Moderator: You Song (NIVA)
Rapporteur: Simon Schmid (NIVA)
Discussion points:
• Meaning of AOP community of practice
• Possible Improvements of the Wiki
• Future of the Wiki
Notes:
Meaning of AOP community of practice
• Community of practice is generally be hoped to be a place where experts from different discipline can gather and discuss
• The need for more workshops/symposia of this kind has been expressed (e.g. for AOP-NW analysis)
• For younger developers, the CoP should be a place to ask for advice from experienced AOP developers and a place to share experiences, learn and discuss
• “Offline” coaching was discussed, i.e. coaching outside the OECD AOP development program there seems to be a clear need for that many training resources are available online, Shihori was already approached for such informal coaching through the AOP Forum
• Need for tutorial videos online
• Inexperienced AOP wiki users want to know who the experts are Need for contacts
• AOP Forum was considered an important resource to get help from experienced users
• The AOP Review process was briefly discussed, the question of why only one reviewer was appointed and not a reviewer team in such an interdisciplinary manner arose efforts in that direction are underway
• How to bring in the regulators? The AOP-CoP symposium is seen as an important event to start a dialogue
Possible Improvements of the Wiki
• For cross species extrapolation/taxonomic applicability domain Why is SeqAPASS not integrated in AOP wiki improvement if it would be linked to wiki
• AOP Networks: Issue of complexity was addressed, in particular BH considerations for whole networks are regarded to be laborious
• Increasing complexity of AOP-NW especially when it comes to quantification
• Further Improvements: use IDs on everything (e.g. chemicals, references), cleaning of KEs (many duplicates), multiple KEs make AOP-NW even more complicated, two options for cleaning of KEs contact gardener or KE authors directly
• Consistency in vocabulary and machine readability were also named as possible improvements
• There should be a possibility to integrate homeostatic responses into AOP-NW
• KEs: need for documenting test strategies/standardized protocols, method database linked to wiki to register protocols?
• OECD reporting template for high throughput data in progress, should make the use of HT data for KE support easier problem: usually only 1 KE measured, not linked to the next one in AOP, so only the KE is supported not the KER
• General data quality/availability was discussed, use of existing data for qAOP development usually difficult because methodology is not transparent enough or data not available
• Building networks is in the “figuring out phase” everyone has their own preferred approach
• Use of AOPs/AOP-NW: regulators want to use it but do not see how yet
Future of the Wiki
• Trust issue was mentioned briefly missing references etc., reason for that could be that there is no “reward” for developers (e.g. publication)
Moderator: You Song (NIVA)
Rapporteur: Simon Schmid (NIVA)
Discussion points:
• Meaning of AOP community of practice
• Possible Improvements of the Wiki
• Future of the Wiki
Notes:
Meaning of AOP community of practice
• Community of practice is generally be hoped to be a place where experts from different discipline can gather and discuss
• The need for more workshops/symposia of this kind has been expressed (e.g. for AOP-NW analysis)
• For younger developers, the CoP should be a place to ask for advice from experienced AOP developers and a place to share experiences, learn and discuss
• “Offline” coaching was discussed, i.e. coaching outside the OECD AOP development program there seems to be a clear need for that many training resources are available online, Shihori was already approached for such informal coaching through the AOP Forum
• Need for tutorial videos online
• Inexperienced AOP wiki users want to know who the experts are Need for contacts
• AOP Forum was considered an important resource to get help from experienced users
• The AOP Review process was briefly discussed, the question of why only one reviewer was appointed and not a reviewer team in such an interdisciplinary manner arose efforts in that direction are underway
• How to bring in the regulators? The AOP-CoP symposium is seen as an important event to start a dialogue
Possible Improvements of the Wiki
• For cross species extrapolation/taxonomic applicability domain Why is SeqAPASS not integrated in AOP wiki improvement if it would be linked to wiki
• AOP Networks: Issue of complexity was addressed, in particular BH considerations for whole networks are regarded to be laborious
• Increasing complexity of AOP-NW especially when it comes to quantification
• Further Improvements: use IDs on everything (e.g. chemicals, references), cleaning of KEs (many duplicates), multiple KEs make AOP-NW even more complicated, two options for cleaning of KEs contact gardener or KE authors directly
• Consistency in vocabulary and machine readability were also named as possible improvements
• There should be a possibility to integrate homeostatic responses into AOP-NW
• KEs: need for documenting test strategies/standardized protocols, method database linked to wiki to register protocols?
• OECD reporting template for high throughput data in progress, should make the use of HT data for KE support easier problem: usually only 1 KE measured, not linked to the next one in AOP, so only the KE is supported not the KER
• General data quality/availability was discussed, use of existing data for qAOP development usually difficult because methodology is not transparent enough or data not available
• Building networks is in the “figuring out phase” everyone has their own preferred approach
• Use of AOPs/AOP-NW: regulators want to use it but do not see how yet
Future of the Wiki
• Trust issue was mentioned briefly missing references etc., reason for that could be that there is no “reward” for developers (e.g. publication)