Difference between revisions of "February 2013 Migration Workshop"

From The SBN Wiki
Jump to navigation Jump to search
Line 16: Line 16:
  
 
I plan to address these on the Wiki pages in the next few weeks.  Feel free to add more questions as they come up.
 
I plan to address these on the Wiki pages in the next few weeks.  Feel free to add more questions as they come up.
 +
  
 
=== What do I do with values in the PDS3 label that don't have PDS4 "pds:" namespace equivalents? ===
 
=== What do I do with values in the PDS3 label that don't have PDS4 "pds:" namespace equivalents? ===
Line 26: Line 27:
 
Links to working prototypes are now on the Wiki main page, under
 
Links to working prototypes are now on the Wiki main page, under
 
[[SBN_PDS4_Migration_Wiki#Discipline_and_Mission_Dictionaries | Discipline and Mission Dictionaries]].
 
[[SBN_PDS4_Migration_Wiki#Discipline_and_Mission_Dictionaries | Discipline and Mission Dictionaries]].
 +
 +
  
 
=== Questions as yet Unanswered ===
 
=== Questions as yet Unanswered ===

Revision as of 17:29, 22 February 2013

This goal of this workshop is to have participants work through creating a complete label for a data product to be migrated. It will include working with discipline and mission dictionaries, as appropriate, and validation via the schema-aware editor. At the end, the participants should have a label that can then be turned into a template for converting large numbers of similar labels, or a final product label for a document product.

Time and resources permitting, we will also be validating using the PDS EN validation tool, as well as creating collection and possibly bundle product labels.

Reference Files

I've downloaded copies of the reference files we'll be using for the workshop. You'll probably want them loaded up either in a browser or on your desktop for ready reference. You can download all of them in a zip file, or look at them individually from this URL:

http://pdssbn.astro.umd.edu/PDS4test/WikiSupport/Workshops/2013FebUMD/

This is a version-consistent set. That is, all the files are based on the 0.3.0.0.a version of the Information Model - the one we're supposed to be testing.

Also included is the migration_DS_listV2.xls spreadsheet file, which has been updated with bundle and collection IDs for all the migration test data sets.

Questions Arising

I plan to address these on the Wiki pages in the next few weeks. Feel free to add more questions as they come up.


What do I do with values in the PDS3 label that don't have PDS4 "pds:" namespace equivalents?

You should request that the keywords be added to an appropriate local dictionary. Geometry keywords, for example, will go into our temporary geometry dictionary. Keywords useful across data sets from different sources go in the SBN discipline dictionary. Mission keywords go in a mission dictionary, and so on. Collect the information (keyword name, data type, and definition) and send it to Anne Raugh.


Where are the local data dictionaries?

Links to working prototypes are now on the Wiki main page, under Discipline and Mission Dictionaries.


Questions as yet Unanswered

  • Where are the rules for creating new LIDs?
  • What do I put for Internal Reference LIDs in the Observing System Components?
  • How do I use a local data dictionary?
  • What happens to the PDS3 catalog files?
  • What do I do with the non-data directories in the PDS3 data set?
  • Add info for translating 2D FITS images into PDS4 arrays to get the storage order and notations reference right.