Page 1 of 1

Metadata in reports- how much is too much?

Posted: Fri Mar 09, 2018 7:51 pm
by EmpowersBane
I report system suitability on several methods and tend to keep the peak tables basic and to the point- group by peak name, or add an RSD, Mean function at the end of a set of injections area, also USP Tailing and Signal to Noise of a component.

Now my boss wants all the associated data like Result ID, Processing Method ID, Date Acquired, Integration Type, Injection ID, Manual, Processing Locked, Codes, Date Processed, Channel ID etc as well as the pertinent data but when I add these to my tables they start to wrap and are very sore on the eye, big long tables when only the relevant data like RSD of areas etc is lost amongst all the extras.

Is there a way to just have one table at the end (maybe order by Samplename or Injection) with all that data so you want like Result ID etc connected to each sample? Any help with default report methods for this?

Re: Metadata in reports- how much is too much?

Posted: Mon Apr 02, 2018 6:27 am
by ydna1977
Hi ,

Doesn't the Empower default 'sample information' tab not enough?

Currently no set procedure but injection info includes :
Sample Set id
results set id
result id
calib id
channel id
instru ment id

maybe group these ?
I don't know what is best process and empower report content seems to be very much personal opinion /QA

Any fixed /approved process and content much appreciated