dmwm / PHEDEX

CMS data-placement suite
8 stars 18 forks source link

feature request: improve PhEDEx Data::Subscriptions page to aggregate results by dataset #934

Open ericvaandering opened 10 years ago

ericvaandering commented 10 years ago

Original Savannah ticket 101751 reported by wildish on Thu Jun 13 10:44:37 2013.

Hi, I am using PhEDEx's Data::Subscriptions page to keep track of the datasets subscribed by my group ("trigger") on the various sites.

I would find it very useful to be able to aggregate the BLOCK-based data into DATASET entries.

For example, at the moment [https://cmsweb.cern.ch/phedex/prod/Data::Subscriptions#] gives a lot of BLOCK-level entries like

391460 /Commissioning/Run2012C-v1/RAW#e02be7ba-03c4-11e2-861e-842b2b4671d8 T2_ES_CIEMAT trigger 2 2.9 GB ... 391460 /Commissioning/Run2012C-v1/RAW#431d70a8-03d1-11e2-861e-842b2b4671d8 T2_ES_CIEMAT trigger 1 122.6 KB ... etc.

all coming from the same request and concerning the same dataset. It would be very useful to be able to switch to an "aggregated" view, where they would show up as a single entry, like

391460 /Commissioning/Run2012C-v1/RAW T2_ES_CIEMAT trigger xx xxx TB ...

(if it makes things easier, it would still be useful to limit such aggregated view only to BLOCKS coming from the same request id)

Thanks, .Andrea

P.S. I wouldn't know which "Category" to use, but I had to pick one as it is mandatory.

ericvaandering commented 10 years ago

Comment by magini on Thu Jun 13 10:44:37 2013

This item has been reassigned from the project CMS Computing Infrastructure Support support tracker to your tracker.

The original report is still available at support #138096

Following are the information included in the original report:

I would find it very useful to be able to aggregate the BLOCK-based data into DATASET entries.

For example, at the moment [https://cmsweb.cern.ch/phedex/prod/Data::Subscriptions#] gives a lot of BLOCK-level entries like

391460 /Commissioning/Run2012C-v1/RAW#e02be7ba-03c4-11e2-861e-842b2b4671d8 T2_ES_CIEMAT trigger 2 2.9 GB ... 391460 /Commissioning/Run2012C-v1/RAW#431d70a8-03d1-11e2-861e-842b2b4671d8 T2_ES_CIEMAT trigger 1 122.6 KB ... etc.

all coming from the same request and concerning the same dataset. It would be very useful to be able to switch to an "aggregated" view, where they would show up as a single entry, like

391460 /Commissioning/Run2012C-v1/RAW T2_ES_CIEMAT trigger xx xxx TB ...

(if it makes things easier, it would still be useful to limit such aggregated view only to BLOCKS coming from the same request id)

Thanks, .Andrea

P.S. I wouldn t know which "Category" to use, but I had to pick one as it is mandatory.