1 / 8

SBN PDS4 Migration Planning

SBN PDS4 Migration Planning. PDS MC at UCLA, 29 November 2012. Considerations. Significantly improved search under PDS4 for SBN products generally, and ground-based data in particular. Significant support for documentation and auxiliary data products under PDS4.

ayita
Download Presentation

SBN PDS4 Migration Planning

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SBN PDS4 Migration Planning PDS MC at UCLA, 29 November 2012

  2. Considerations • Significantly improved search under PDS4 for SBN products generally, and ground-based data in particular. • Significant support for documentation and auxiliary data products under PDS4. • Inclusion of SBN discipline classes could provide even more search benefits, plus automation benefits for SBN website. • Central catalog currently lists 914 SBN datasets. • A significant fraction of these are superseded or safed data.

  3. Selection Criteria • Final/latest versions only – superseded and safed data will not be migrated. • High-interest data sets – current DAP candidates; NASA challenge data; etc. • High-value data sets – property catalogs and collections referenced by many end-users. • Low-hanging fruit

  4. PSI Plans • First draft of conversion tool to handle OLAF-produced data sets done. • LADEE/LDEX data from this tool will be reviewed in December • OLAF-produced data sets can then be migrated largely mechanically and should take 1-2 months. Caveats: • Cannot include improved search parameters • Cannot include non-observational data files.

  5. UMD Plans • Shamelessly pirate other tools for useful code; add code to handle search parameters and node classes. • Plan for hand-crafting non-observational products (documentation, etc.) as part of the migration for each data set. • High-priority data used for migration testing will be the first to be re-migrated to 3b. Beyond that, priorities will be periodically re-assessed. • All migration will have to be on an “as resources are available” basis. Consequently, it will likely take 2-3 years to migrate most of our data sets, and some problematic collections (Rosetta, e.g.) may take substantially longer.

  6. Software Migration • Online Archiving Facility (OLAF): Schedule TBD. The current plan is to use OLAF in conjunction with the PSI migration tool at least until the first public PDS4 release. • IDL tool: readpds.pro – A draft version (browse_pds.pro) is in testing now, awaiting more data products.

  7. Screenshot: browse_pds.pro

  8. Related Topics • Data Ferret migration • Web site upgrades to take advantage of new PDS4 search & packaging capabilities • Acute Russian interest in PDS4 archiving and related IPDA activities, and especially in multi-lingual potential for data dictionary support. • Development of new maintenance procedures for node archives. • Development of new procedures for deep archive delivery/retrieval

More Related