Open matentzn opened 1 year ago
Add obsolesence reasons (and comments?) to obsoletes table to make it a bit more informative? Perhaps even aggregated xrefs?
I think for the obsoleted comment the following fields would be interesting:
generally, 1 row per obsolete class, and where there are multiple values of the attributes above, just roll them into a pipe-separated string.
FYI I know this because I just generated some similar, ad hoc report, the predicate for obsolescence reason is IAO_0000231.
IAO_0000231
Add obsolesence reasons (and comments?) to obsoletes table to make it a bit more informative? Perhaps even aggregated xrefs?
I think for the obsoleted comment the following fields would be interesting:
generally, 1 row per obsolete class, and where there are multiple values of the attributes above, just roll them into a pipe-separated string.