We need a solution for the review of AOP that have shared KEs and KERs.

This is especially important if these KEs/KERs have been borrowed from AOPs that have already been reviewed.

One suggestion is that during the review, each KE and KER gets reviewed independently of each other, and each have their own "review documentation" attached to them.

This way, any review conducted will "follow" that KE/KER wherever they go. This is the same as all the other information related to KEs and KERs

i.e. We should consider making AOP reviews "modular" as well. Or rather, a "review" is an attribute/property for each KE, KER and AOP in KB.

just like AOPs are make up of KEs and KERs, the "AOP Review" can be "made of" its component "KE Reviews" and "KER reviews", along with any higher level synthesis that occurs at the AOP level.

All of these "sub-reviews" can be conducted by the same group of reviewers (as is currently done) or can optionally be conducted individually, as needed.

I've included an image describing this idea (hope it makes sense :))


  modular review.png (Size: 232.63 KB / Downloads: 3)

Create umbrella key events that could encompass multiple KEs that encompass a set of related KEs.

Attached Files

  umbrellaKE-3-11-21-lightest.pdf (Size: 1.05 MB / Downloads: 6)

A suggestion to tag AOPs that have sufficient quantitative understanding or aligned computational models to facilitate their use for quantitative applications (suggestion from webinar 1).

Knapen et al. 2018 described concepts for sorting and filtering AOP networks based on key event components and other structured ontologies in the AOP-Wiki.  However, to date there are no features in the wiki to help implement those concepts.  These would be nice to add to AOP-Wiki 3.0 (idea from webinar 1).

The evidence map pilot study facilitates generation of an evidence table on the KER pages. It would be nice to be able to download the evidence tables supporting an individual KER or the AOP as a whole (suggestion from webinar 1).

The new data model must explicitly include the concept of related KEs whereby they share some (but not all) of the same features, which could represent a source of crosstalk between AOPs containing those KEs that is distinct from the sharing of a single KE.

This data model should also facilitate the reuse of this shared information among those related KEs to avoid increasing the burden on KE authors.

Capture information in a single place, but allow sharing of information between entities

• Identify the appropriate level for each piece of information
  
• For concepts defined at a higher level, enforce compliance with those constraints when entering information at lower levels.
  
• For concepts defined at lower levels, roll up information at higher levels rather than capturing the information separately
  
• Reduce the number of free text inputs for all entities except the AOP and capture information through more structured forms
  

Improving the provenance for the information in the AOP-Wiki by ensueing uses of the system can Trust the information provided. 

For this, the new wiki data model should support three major features.

• Make it clear who contributed which content. While this information is currently available, it can be laborious to identify all the contributions from a single user using the edit history associated with each page.
  
• Document the strategy used to assemble literature when evaluating the evidence. This requires not only that contributions from individual users are tracked, but the individual references used must be tracked and tied to the strategy used to assemble the literature.
  
• Provide a more consistent format for the information in the AOP-Wiki. Users don’t have time to decipher many different ways of capturing the information. If the provenance of the wiki knowledge is not readily apparent, it will be invisible to most consumers of that information.
  

Please use this thread to post comments about the AOP Developers Handbook Version 2.6.

Please use this thread to post comments about the AOP Developers Handbook Version 2.5 released on July 14th, 2022.