Long Term Preservation Archival Policies and Implementation Archival Standards and Technologies User Needs Provider Interactions Poster Reviews P2 LSST: Preparing for the Data Avalanche through Partitioning, Parallelization, and Provenance (Kirk Borne). Theme: User Interactions? Standards and Technologies Kirk presents some of the challenges that face the Large Synoptic Survey Telescope (Chile). This project will generate data on the order of 30 TB/day (65 PB/life). The data will be processed and parameterized in real-time such that the meta-data associated with each 6 GB (3 gigapixel) is actually larger than the image itself. All of this data must be moved from its acquisition site to the science center in San Diego. In addition, since much of the analysis and parameterization occurs in real-time, the provenance of the images (telescope configurations, software versions, policies, etc.) need to be tracked along with the data. Kirk discusses how the LSST data management team has addressed these challenges and the database principals that they have employed. P3 Science Archives in the 21st Century: a NASA LAMBDA report (Paul Butterworth) Theme: Archival Policies and implementation Paul runs a small data center (2 FTEs) the serves a small user community, the cosmic microwave background (CMB) scientists. The resources are limited so the data center focuses on the specific needs of its user community. If NASA mandates that his system must comply with various information system methodologies, or that he provide complex metadata for Virtual Observatory access, it may bankrupt or cripple his data center. He makes a strong case for developing the Virtual Observatories and other inter-disciplinary data systems in such a way as to have minimal impact on current data providers and small data centers. P8 AND Archives: Freeing ourselves from the "Tyranny of the OR" (Ted Habermann) Theme: Archival Policies and Implementation Ted presents a case for including both GIS (geospatial) and intrinsically scientific data representations. In the NOAA system, data are initially ingested into a GIS database, and then written back out to the file system in more standard forms. This approach allows users to search, retrieve, and analyze the data using standard geospatial techniques AND to access the data files themselves through standard search and retrieve functions. P9 An application of CCSDS archival standards to meet both submitter and archive needs during data ingest (Kent Hills et al.) Theme: Archival Standards and Technologies Kent describes the past, present, and near future of the NSSDC data ingestion process. The process has transitioned from one that relied on human interaction to one that is standards and tools based with only a human review process. This transition will impact both the Center and its users, however, the end result will be a more useable, more reliable system. P13 NASA Datasets Management Using Process Libraries and Electronic Handbook [Where Shakespeare meets Frued] (Barry Jacobs) Theme: N/A Barry presented a real-time demonstration rather than a poster. The demonstration showed a database of project proccess that he has assembled in order to assists new projects with the development of their processes. In the past, this information was placed in project databases and not available to other projects. As a result, each project invents new processes to solve problems that have been previously solved by others. By gathering the process information, and distributing making it available to new projects, the workload for new projects should be reduced and eventually many of the common processes may become standardized. P20 Guidance for Science Data Centers through Understanding Metrics (John Mosses et al.) Theme: Archival Policies and Implementation??? John presents a poster that describes the metrics that the EOSDIS project has been been acquiring. His presentation includes a discussion of some of the pitfalls that arise in the presentsation of metrics. In some cases the raw metrics can easily be misinterpretted. P33 Tradeoffs in the Development in the SPASE Data Model (Jim Thieman et al.) Theme: Archival Standards and Technologies Jim presents a discussion of many of the tradeoffs that were discussed and implemented during the development of the SPASE data model. These include, but were not limited to: data accessiblity: search/retrieve vs analyze/transform documentation level: file collections vs files metadata level: rich, manual vs minimal, automated metadata language: cross-discipline vs intra-discipline metadata content: conceptual vs structural describes objects vs describes bytes