80 likes | 208 Views
NSSDC Delivery Working Group. MC Face-to-Face Washington, DC March 25-26, 2010. Topics. Progress Node Delivery Schedule Next Steps. Progress. Finalized electronic delivery process Updated submission process document Delivery Manifest V1 schema baselined
E N D
NSSDC Delivery Working Group MC Face-to-Face Washington, DC March 25-26, 2010
Topics • Progress • Node Delivery Schedule • Next Steps
Progress • Finalized electronic delivery process • Updated submission process document • Delivery Manifest V1 schema baselined • Delivery Manifest generator prototyped • Online harvesting software in place to create config files / IDs (reduce submission request turn around) • NSSDC archive ingest software in place • Manual tracking process in place • Created wiki page http://oodt.jpl.nasa.gov/wiki/display/NDWG/Home
Delivery Progress (1 0f 4) • Atmosphere • 71 volumes delivered and ingested • Preparing 42 volumes (have config files / IDs), loading data brick, plan to fill it up close to full before delivery • ~40% of entire holding delivered and ingested into NSSDC • Geosciences • 13 volumes delivered and ingested • Preparing 28 volumes (have config files / IDs) for data brick delivery
Delivery Progress (2 0f 4) • Imaging • 58% of completed missions have been delivered to NSSDC • Schedule to deliver active/Accumulating missions (THEMIS, Messenger, MER, MRO (CTX,HiRISE, MARCI) data later this year • NAIF • 12 volumes delivered and ingested • ~80% of entire holding delivered and ingested into NSSDC • Delivery schedule annually
Delivery Progress(3 0f 4) • PPI • 32 volumes delivered to NSSDC, 1 ingested • 31 volumes waiting for config files / IDs • Planning to send a copy of all data on hand on a data brick for safe keeping • RINGS • 13 volumes delivered and ingested with 3 volumes to be redelivered in near future • ~90% of entire holding delivered and ingested into NSSDC
Delivery Progress(4 0f 4) • SBN - UMD • 32 volumes delivered and 31 ingested into NSSDC • Waiting for 18 config files / IDs • Preparing 54 (received config files / IDs) volumes for delivery • Wrote SBN specific Delivery Manifest generation script • SBN - PSI • 6 volumes delivered and ingested into NSSDC • Waiting for 24 config files / IDs • Preparing 34 (received config files / IDs) volumes for delivery
Next Steps • Node Future delivery • Periodically (annually), or on an as ready basis • Via data brick, electronically , or RAID as appropriate • Experiment and define RAID delivery process • Develop operational Delivery Manifest generation software