Selection
---------

Admin wants to select files based on input datasets, collectons, production date
(+ since/before), file names, location, production stream or physics  
group, whether file is active/close etc.

Dataset/File Operations
---------------
Admin wants to do most of file operations remotely, i.e. without logging
into to a data server.

Admin wants to list files with attributes, i.e. a,m,c- times, file size,
full path, file permissions,

Admin wants to check whether file ison disk, in hpss.
Admin wants to check whether file is backed up or needs back up.
Admin wants to pre-stage a file from hpss into disk cache, with confirmation
Admin wants to migrate a file to hpss, with confirmation.
Admin wants to remove a file from disk cache.
Admin wants to copy/relocate a file to another disk cache.
Admin wants to change file permissions.
Admin wants to pin files on disk for specified time.

Admin wants to combine some operations into one, like: migrate+remove,
migrate+copy, stage+chmod,

Admin wants to check file for corruption/readability.

Admin wants to check what "run files"(or "job files", those produced by a 
  single job) are included in the composite file.

? Admin wants to exclude some "atomic" files from the composite file.

Monitoring
----------

Admin wants to analyze access patterns on disk and hpps, + trends.

Server Pool management
----------------------

Admin wants to set a pool of hosts for readonly data.

Admin wants to set a pool of hosts for user's production data. This is totally 
  separate from readonly hosts.

Admin wants to dynamically add or remove a host from a readonly or write pools.


User production
---------------

User produced data (reading off PR collections in analysis environment)
  is placed on dedicated servers with writing/reading via xrootd enabled,
  and load balancing disabled. Files are not backed up, until merged into
  a big file.

User's generated files can be read immediately after production, but
  since load balancing is disabled, files can not be restaged/copied to
  another server.

When user decides to merge small files, new dataset is created, merged
  file is archived and pruged off production host. From that time it can
  only be accessed in the readonly pool.

Users should have a good way to manage their jobs and datasets. If a user
  wants to make his data publicy available, he needs to make a dataset
  in skimdata, (which will be done at the same time with a data backup,
  i.e. atomically).

===> needs thinking - how readonly jobs are configured to select the data 
     servers pool?

Debugging
---------

Admin wants to find out what site/farm the file was generated at and when.

Admin wants to disable access to certain data sets, should it need
  so. This means tcl files should not be generated for a user jobs. ??Other
  ways to prevent user from accessing some data?? A la inhibit??