VOName: CERN-T0

Cloud: CERN (for entry in site table)

DestCloud: CERN

Tier: 0 (for site table as the TIER in the SMRY tables is not used)

Activity is the TASKTYPE column - need to add 't0_' before the activity name BUT probably not on CAF activities.. - Did it from the collector and updated the existing tasktypes.

InputDataType is the DATATYPE column

Project AND OutputProject is the PROJECT column

Group: t0

AGenActivity: we will split them to 'T0 Processing' and to 'CAF Processing' according to the list of activities that were given to us by the ATLAS people:

for the Activities (ADC), I would separate T0 and CAF
T0

   aodmerge
   tagmerge
   rawmerge
   hist1merge
   histmerge
   recon
   ntupmerge
   drawmerge
   dpdmerge

the above includes 'recon' that is confusing with the existing grid job type 'recon'.
probably we should put a prefix 't0_' before all the above

CAF

   physmon
   upload2triumf_fp
   upload2cern_fp
   beamspotproc
   posttag4cern_fp
   upload2cern_mc
   posttag4triumf_fp
   posttag4cern_mc

ResourcesReporting: T0 Processing

NEvProc: NEVENTS

WCTAll and WCTGood: WALLCLOCK *and according if jobs are FAILED or FINISHED jobstatus

CPUAll and CPUGood: CPUCOUNT ** Simone told me that they don't want us to store the CPU consumption AT ALL as it is not accurate ***

For ERROR TABLES same as above but:

ErrorCategory: t0

ExitCode is the ERRORTXT (many times it is null / need to transform to 'unknown') and probably we need to join it with the TRFCODE which is the exitcode (some times it is null!).