Attending

• Jack, Jerry, Marco

Agenda

• DSS Status and Progress
• Sofware Week reports (feedback, comments)
• xrootd TAG creation (David' email)

Discussion

• files are in LRC
• develop a local service (for OSG Tier2 and similars, with skims running on local queue, distributed runs later)
  • no dependency on external components (more reliable)
  • maintain visibility as a independent software, not included in bigger packages
• able to work with both local copy and shared access to the input files
• hardcode most of the choiches: keep the software flexible but don't expose too many options to the users

• TAG (DB and root file) provenance could be stored in the TAG DB in a dedicated table since they are closely related (DS, TAG root files DS, date, trf used)
• Skim provenance should probably in a separate DB: Skim DB (TAG table, date, query, ...). This DB should be available to access the information from the outside (which TAGs are at MWT2?) but should be specific to the Site, not shared (at least for now)

• produced from the same DS and TAG?
• never (only if they are replicas of the same skim)?

• users expect a certain structure (prepackaged queries with summary data on the DS)
• no ideal reusable composer is known
• Julius interface is an option (download JAS and use it)
• check with Sasha and Torre for existing possibilities
• looking for a flexible MySQL GUI (to execute query, hiding DB structure - no phpMyAdmin)

• E.g. ESD or RAW data could be skimmed
• no big requests so far: Tom is skeptical but it is a possibility that may be requested in the future
• for now DSS will work with AODs. Go ahead and hardcode that (do not expose alternatives to the user) but be prepared anyway for ESD and RAW (keep the sw flexible)
• Current TRFs work for AOD. Jack will check if they are more general than expected (at least the ones used in extraction - TAGs will be still generated from AODs).