Community Forum     Helping YOU do what YOU want with YOUR data.
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
Warwick Wood  
#1 Posted : Friday, June 7, 2013 6:39:26 AM(UTC)
Warwick Wood
Rank: Administration

Reputation:

Groups: Registered, Administrators
Posts: 503
Man
Location: Byron Bay

Was thanked: 19 time(s) in 19 post(s)

We've had a few users enquire about Napthalene, along the lines of:

"We have an issue that was raised regarding ‘Naphthalene’ reported for different methods, ie. BTEX and non-BTEX. Would you be able to advise us if there is a chem-code, that we can use to differentiate the results for this analyte?" 

It is fairly common to have a single compound analysed by multiple methods in a lab, potentially returning different results (or detection limits).  ESdat records all of the ChemCode and the Method Type and the Method Name for each result.  The ChemCode is always the same for a compound, and the Method used to obtain the result will often vary.  This means the ChemCode can be used to match data irrespective of the Method, and with guidelines.

If users wish to group their results by Method, that option is available in ESdat, using either the Method_Type or Method_Name grouping option on their output. 

Lots of users don't like those Method groupings because they prefer to use thier own grouping, where specific ChemCodes are grouped together however the user specifies.   (ie not incorporating Method Name or Method Type).  This by definition means that the results are not differentiated or grouped on the basis of the Method.  This may result in two different results are presented together for the Analyte, typically presented as a range in tables.

It may be that with Napthalene there is a significant need to use a different ChemCode for each Method, so that users can use their custom Grouping, but also, for Napthalene, incorporate grouping on the basis of Method.  We are cautious in doing so, for the reasons outlined above, and because it could quickly become a mess if this was done for all compounds.  However, if the preference for doing this for Napthalene is fairly unanimous after users have considered the reasons spelled out we are happy to look into it.

Warwick

Edited by moderator Friday, August 9, 2013 12:25:44 AM(UTC)  | Reason: Not specified

ntumney  
#2 Posted : Tuesday, June 11, 2013 7:40:07 PM(UTC)
ntumney
Rank: Advanced Member

Reputation:

Groups: Registered, Administrators
Posts: 1
Australia
Location: Melbourne

Hi Warwick,

This is something that we've encountered for multiple chemicals, not just naphthalene.  Our solution is to have multiple ChemCodes as suggested, and use a post-import custom calculation to assign this based on the laboratory method.

The great thing about using this solution is that we can vary our reporting groups on a site by site basis by only assigning the custom calc to the appropriate site.  For chemicals such as N in BTEXN, we apply the custom calculation to all sites.

wnunn  
#3 Posted : Thursday, July 31, 2014 1:59:58 AM(UTC)
wnunn
Rank: Newbie

Reputation:

Groups: Registered
Posts: 3
Location: Australia

Hi Warwick,

Is there any chance of making a post-import calculation (as described by ntumney) available to all users? Unfortunately I don't have the SQL language skills to write the function myself.

Will

 

mkidd  
#4 Posted : Thursday, April 15, 2021 4:10:00 PM(UTC)
mkidd
Rank: Newbie

Reputation:

Groups: Registered
Posts: 3
Australia

Thanks: 2 times

Hi, 

Was the "post-import custom calculation" discussed by ntumney ever released to users to assist with separating analytes with the same chem-code but different analysis methods? Or is there some other solution now available? Thanks

You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.