-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggested new P02 codes (BODCNVS-1717) #34
Comments
The spreadsheet contains multiple requests/suggestions: @MeganAnneFrench in a first instance we are proposing to only create a new series of P02 for "dioxins"; I think tha the other categories are too fine-grain and present risk of too many overlaps with some chemical substances coming under more than one category. We can review this decision at a later stage. |
2- Broaden MDBO by adding inorganic selenium to Trace metalloid concentrations in biota and remap selenium P01 codes to MDBO instead of BCMT (Metal concentrations in biota) - will make it consistent with what we have done for codes in water bodies and sediments |
3- correct mappings of antimony, arsenic, boron to metalloids instead of metals |
4- to add a new P02 for Organometallic and organometalloid species concentration parameters in suspended particulate material (instead of your suggested very specific "Concentration of methylmercury in suspended particulate material" for methyl mercury @MeganAnneFrench |
|
|
@MeganAnneFrench I think that if we want to align with ICES then we need ICES to be involved too. I was under the impression that ICES was still considering how best to categorise contaminants and the categorisation they currently have one just one of many possible and still being reviewed. But I might have misunderstood. @neil-ices-dk could you relay this to Hans or/and Anna's please? I don't seem to have their github contact. |
@MeganAnneFrench The problem here is that P36 (a EMODnet chemistry grouping vocabulary) is mapped to P02 (a non-EMODnet chemistry grouping vocabulary) instead of being linked directly to the chemical substances. Maybe this is the decision we need to make. Would we be best curating mappings between P36 and S27 instead of between P36 and P02 and trying to change P02 in order to fit EMODnet chemistry's requirements? |
|
And possibly with Dick and the whole Technical Steering Committee too because it might affect other processes in the pipeline. |
thanks for raising @gwemon - i will take this up with the team at ICES |
Adding @HansMJ and @Osanna123 to the thread. Hans and Anna what do you think of Megan's suggestion? Thanks @neil-ices-dk for forwarding. |
@gwemon @MeganAnneFrench Thanks for adding us to the thread. Our Pargroup list (https://vocab.ices.dk/?codetypeguid=9e697af5-d9f9-4ae4-8c14-f1ed3bfab434) is targeting the assessment outputs, where grouping contaminants by chemical structure is not always the focus, so we have a bit of mix of concepts, where contaminants might be characterized by either their chemical class (i.e. nitroaromatics, PAHs) or their target use (i.e.herbicides, pharmaceuticals). Presently, if a contaminant can belong to more than one Pargroup, we map to the one requested by the data submitter (or our content governance bodies). However, I don't think there's a big issue for organobromines and organochlorines. |
Thanks @Osanna123 and sorry for the delay in acknowledging. I have been away from my desk a lot recently. Picking this up again. From your comment I understand that the 2 categories organobromines and organochlorines are well defined and stable grouping categories in ICES and they would be worth creating as separate P02 entities for better alignment between ICES and SDN/EMODnet/NVS. However Organochlorine are also pesticides and from looking at our grouping many currently fall under our P02 groups for "Pesticides in biota/water/sediments". So @MeganAnneFrench if we were to create a set of organochlorine P02 codes for biota/water/sediment then would you suggest deprecating the P02 for "pesticides"? Presumably there must also be some "non-organochlorine pesticides" so would we have to also create a new group for these? |
@MeganAnneFrench have you been able to discuss the S27 route suggested in #34 (comment) ? |
First, I want to apologise for the long response below and say that I understand that the grouping of contaminants can be challenging and frustrating. As mentioned by Anna, as we are dealing with the management of contaminant data that are often used for environmental assessments, it is necessary to group contaminants by their chemical class, main use, or a mixture of both. For instance, organophosphorus substances include pesticides and flame retardants; therefore, ICES’s PARGROUPs include organophosphorus pesticides and organophosphorus flame retardants. |
Update on changes we have made so far:
|
Hi,
Based on Dick's list from November 2022 (unshaded columns), I have listed the P01s that require new P02s to be created, with any change to the P36 listed as well (pale yellow columns with red text). Any notes are shown in the grey shaded columns. Note that these new P02s only relate to the list of P01s provided by Dick in November 2022 and that other P02s may be required to complete the "set" (e.g. I've suggested "Organofluorine concentrations in biota" and "Organofluorine concentrations in sediment" but not "Organofluorine concentrations in water bodies" because no P01 for the latter was included in Dick's list).
Megan
P36s and new P02s.xlsx
The text was updated successfully, but these errors were encountered: