Create record for derived data for 2011 jet validation step

[katilp]

FIles from /afs/cern.ch/user/m/mhaapale/work/public/Jet-Tuples-Summer2016
need to uploaded to a record (similar to http://opendata.cern.ch/record/230)
@tamshai can provide the metadata details.
It will refer to the new sw records (in #1191)

[katilp]

@tiborsimko Could you kindly move these files to eospublic so that Freya can check the code:
/afs/cern.ch/user/m/mhaapale/work/public/Jet-Tuples-Summer2016

The parent dataset for data is: /Jet/Run2011A-12Oct2013-v1/AOD
For MC, as indicated in https://github.com/cms-opendata-validation/2011-jet-inclusivecrosssection-ntupleproduction/blob/master/tuple_info_mc

[katilp]

So for data, they could be under
https://eospublichttp01.cern.ch/eos/opendata/cms/Run2011A/Jet
What kind of naming we had for ther derived datasets? I see that for evt display file they are under IG
and in https://eospublichttp01.cern.ch/eos/opendata/cms/Run2011A/DoubleElectron
we have PATtuples, so their directory could be call jettuples
(output of http://opendata.cern.ch/record/5104)

[tiborsimko]

@katilp I get permission denied:

$ ls -l /afs/cern.ch/user/m/mhaapale/work/public/Jet-Tuples-Summer2016/
ls: cannot access /afs/cern.ch/user/m/mhaapale/work/public/Jet-Tuples-Summer2016/: Permission denied

Could be due to CMS-only access, I guess.

Could you move the files to some fully public AFS space?

we have PATtuples, so their directory could be call jettuples

PAT was referring to Physics Analysis Toolkit. Could be used here too perhaps? (I haven't seen the what the files are...)

[katilp]

@tiborsimko OK, it is the same for me, and I'm following with the afs support, I've added you in cc, it should be possible to copy them still.
For the naming, PATtuples is no good here as it is a specific well-defined format while this are plain root tuples containing jets. But it is the same format as in use in the CMS jet group so I would go for jettuples.

[katilp]

@tiborsimko The files can now be uploaded (https://cern.service-now.com/service-portal/view-request.do?n=RQF1000758)