1 / 38

C. Huc/CNES, D. Boucon/CNES-SILOGIC

NSSDC Use case analysis. C. Huc/CNES, D. Boucon/CNES-SILOGIC. Contents. NSSDC Use Case presentation Model 1 Model 2 Conclusion. NSSDC Use Case Introduction.

roger
Download Presentation

C. Huc/CNES, D. Boucon/CNES-SILOGIC

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. NSSDC Use case analysis C. Huc/CNES, D. Boucon/CNES-SILOGIC

  2. Contents • NSSDC UseCase presentation • Model 1 • Model 2 • Conclusion Specification for the Formal Definition and Transfer Phase

  3. NSSDC Use CaseIntroduction • The NSSDC USC-1 is based on a view of the NSSDC Version 3 Archival Information Package (AIP), which is also used as a Submission Information Package (SIP). • NSSDC is planning to use this particular AIP form to contain muliple data objects (files) along with metadata attributes. • The AIP package is an SFDU structure, with one LVO being a PVL object referred to as the NSSDC Attribute Object (AO). • This use case works back from an AIP to the data and metadata objects contained and referenced therein. Specification for the Formal Definition and Transfer Phase

  4. NSSDC Use CaseInformation Objects 1. Package Header Attributes Object 2. Multi-stream attributes object 3. Directory Pathname to original Data Object 4. Attributes of corresponding Data Object prior to packaging 5. Attributes of corresponding Data Object after packaging 6. Supplementary attributes of Data Object after packaging 7. Binary Data Object stream Specification for the Formal Definition and Transfer Phase

  5. NSSDC Use CaseSIP Content Z Label K Label PVL AO group label Package Header Attributes Object PVL Multi-stream group label Multi-stream Attributes Object PVL stream group label Stream Instance Pointer = 1 Directory Pathname Attributes of corresponding Data Object stream prior to packaging Attributes of corresponding Data Object stream after packaging Supplementary attributes of corresponding Data Object stream PVL stream group end label PVL Multi-stream group end label PVL AO group end label U Label Stream Instance Identifier =1 I Label Binary Data Object stream 1 2 3 4 5 6 1..n 7 1..n Specification for the Formal Definition and Transfer Phase

  6. NSSDC Use CaseModels NSSDC-Use Case NSSDC-Use Case MODEL 1 This model considers the NSSDS package as a whole and as an elementary “Data Object”. NSSDC-Use Case MODEL 2 • This model considers the science data files • as the granules of the model, and is made up of • a decomposition of the different • NSSDC package elements. Specification for the Formal Definition and Transfer Phase

  7. Reminder • Specification documentprovides a standard method to • formally define the digital information objects to be transferred by a Producer to an Archive • actually transfer these objects in the form of SIPs Specification for the Formal Definition and Transfer Phase

  8. NSSDC Use CaseGuidelines - steps Formal Definition Phase Step1: Descriptor Model definition Step 2: Descriptor Instanciation Step 3: Slip Model Definition Step 4: MOT design Step 5: SIP Model Definition Transfer Phase Slip Instanciation Slips and SIPs transfer Specification for the Formal Definition and Transfer Phase

  9. COLLECTION_DESCRIPTOR DO_DESCRIPTOR DO_DESCRIPTOR NSSDC Use CaseModel 1 ROOT SPMS-00216-CO SPMS-00217-CO SPMS-00216-PKG (N) SPMS-00217-PKG (N) Specification for the Formal Definition and Transfer Phase

  10. NSSDC Use Case - Model 1Step 1: Descriptor Model Definition • NSSDC-SE-COLLECTION-DESCRIPTOR • NSSDC-PACKAGE-OBJECT-DESCRIPTOR Specification for the Formal Definition and Transfer Phase

  11. Reminder • Descriptor Model: attributes (meaning, syntax, defined occurrence) to: • Identify the type of object described. • Define the relations between the objects described and the other Model objects. • Describe the object content. • Give a name to the Slip Model to be delivered. Specification for the Formal Definition and Transfer Phase

  12. NSSDC Use Case - Model 1 Step 1: Descriptor Model Definition NSSDC-SE_COLLECTION_DESCRIPTOR Specification for the Formal Definition and Transfer Phase

  13. NSSDC Use Case - Model 1 Step 1: Descriptor Model Definition NSSDC-PACKAGE_OBJECT_DESCRIPTOR Specification for the Formal Definition and Transfer Phase

  14. NSSDC Use Case - Model 1 Step 2: Descriptor Instanciation NSSDC-SE-collection-descriptor instance There are many possible instances of this model because there are many different data collections, Example: Specification for the Formal Definition and Transfer Phase

  15. NSSDC Use Case - Model 1 Step 2: Descriptor Instanciation NSSDC-PACKAGE_OBJECT_DESCRIPTOR INSTANCE Specification for the Formal Definition and Transfer Phase

  16. NSSDC Use Case - Model 1 Step 3: Slip Model Definition • NSSDC-PKG-DO-slip Specification for the Formal Definition and Transfer Phase

  17. Reminder Slip: A Data Object that conveys information related to another Data Object which is transferred between two entities. This information will allow the addressee to identify, locate and if needed process the various transferred bit sequences which compose this Data Object. Specification for the Formal Definition and Transfer Phase

  18. NSSDC Use Case - Model 1 Step 3: Slip Model Definition NSSDC-TRANSFERRED-PACKAGE-OBJECT-SLIP Specification for the Formal Definition and Transfer Phase

  19. NSSDC Use Case - Model 1 Step 4: MOT Definition ROOT SPMS-00216-CO SPMS-00217-CO SPMS-00216-PKG (N) SPMS-00217-PKG (N) Specification for the Formal Definition and Transfer Phase

  20. NSSDC Use Case - Model 1 Step 5: SIP Model Definition A SIP may contain many packages (coming from different collections). NSSDC_SIP_MULTI-FILE INSTANCE Specification for the Formal Definition and Transfer Phase

  21. NSSDC Use Case - Model 1 Transfer Phase NSSDC_DATA_OBJECT_SLIP INSTANCE Specification for the Formal Definition and Transfer Phase

  22. COLLECTION_DESCRIPTOR DO_DESCRIPTOR NSSDC Use CaseModel 2 ROOT NSSDC-PKG-Views CCSCS-ADID-CO SPMS-00216-CO SPMS-00217-CO NSSDC-PKG-DO (N) ADID-DO (N) SPMS-00216-DO (N) SPMS-00217-DO (N) Specification for the Formal Definition and Transfer Phase

  23. NSSDC Use Case - Model 2Step 1: Descriptor Model Definition • NSSDC-SE-COLLECTION-DESCRIPTOR • NSSDC-PKG-VIEWS-COLLECTION-DESCRIPTOR • NSSDC-SE-OBJECT-DESCRIPTOR • NSSDC-PKG-OBJECT-DESCRIPTOR Specification for the Formal Definition and Transfer Phase

  24. NSSDC Use Case - Model 2 Step 2: Descriptor Model Definition NSSDC-SE-OBJECT_DESCRIPTOR Specification for the Formal Definition and Transfer Phase

  25. NSSDC Use Case - Model 2 Step 1: Descriptor Model Definition NSSDC-PKG-OBJECT_DESCRIPTOR Specification for the Formal Definition and Transfer Phase

  26. NSSDC Use Case - Model 2 Step 2: Descriptor Instanciation NSSDC-SE-OBJECT_DESCRIPTOR INSTANCE One instance for each science data collection. Specification for the Formal Definition and Transfer Phase

  27. NSSDC Use Case - Model 2 Step 2: Descriptor Instanciation NSSDC-PKG-OBJECT_DESCRIPTOR INSTANCE Specification for the Formal Definition and Transfer Phase

  28. NSSDC Use Case - Model 2 Step 3: Slip Model Definition • NSSDC-data-object-slip • NSSDC-PKG-DO-slip Specification for the Formal Definition and Transfer Phase

  29. NSSDC Use Case - Model 2 Step 3: Slip Model Definition NSSDC-TRANSFERRED-DATA-OBJECT-SLIP The elementary science data files and their metadata package are linked via the specific attribute Related_Package_Object_ID. Specification for the Formal Definition and Transfer Phase

  30. NSSDC Use Case - Model 2 Step 3: Slip Model Definition NSSDC-TRANSFERRED-PACKAGE-OBJECT-SLIP Specification for the Formal Definition and Transfer Phase

  31. NSSDC Use Case - Model 2 Step 4: MOT Design ROOT NSSDC-PKG-Views CCSCS-ADID-CO SPMS-00216-CO SPMS-00217-CO NSSDC-PKG-DO (N) ADID-DO (N) SPMS-00216-DO (N) SPMS-00217-DO (N) Specification for the Formal Definition and Transfer Phase

  32. NSSDC Use Case - Model 2 Step 5: SIP Model Definition A SIP may contain many packages, coming from different collections. NSSDC_SIP_MULTI-FILE INSTANCE This SIP can contain a number of science data files from the SPMS-00216 or SPMS-00217 collections, with their associated metadata package. Specification for the Formal Definition and Transfer Phase

  33. NSSDC Use Case - Model 2 Transfer Phase: NSSDC-TRANSFERRED-PACKAGE-OBJECT-SLIP INSTANCE NSSDC_DATA_OBJECT_SLIP INSTANCE Specification for the Formal Definition and Transfer Phase

  34. Conclusion • One Use Case: not only one model design. Each model has advantages and disadvantages. • Choice of Descriptors and attributes • Associate transfer information via Slip reference in Descriptors? • Descriptors and Slips – Independant? • Only Descriptors and SIPs? • How should we implement and transfer SIPs? • …. Specification for the Formal Definition and Transfer Phase

  35. Conclusion • Reach an Agreement on • Concepts (Descriptors, Slips, SIPs, sequencing constraints), • Process. Specification for the Formal Definition and Transfer Phase

  36. End of presentation Specification for the Formal Definition and Transfer Phase

  37. 1 Generic Slip Model OBJECT_ID TRANSFERRED_DO_FILES LAST_OBJECT TRANSFERRED_METADATA_FILES Instantiated Slips and General principlesOverall view Formal Definition Phase Object Description 4 Generic Descriptor Models 4 Specialised Descriptor Models Type of Object MOT Model of Objects to be Transferred: SIPs definition Relations in the Model Data Objects, Complementary Data Objects Collections, Complementary Collections Descriptor Object Instantiated Descriptor Models APPLICABLE_SLIP Slip Transfer information Specialisation Transfer Phase Transferred Objects in SIPs SIPs Specification for the Formal Definition and Transfer Phase

  38. General principlesOverall view Attribute = SLIP_MODEL_ID Attribute = OBJECT_ID Attribute = DESCRIPTOR_ID …… Attribute = TRANSFERRED_FILE Attribute = DESCRIPTOR_ID …… Attribute = APPLICABLE_SLIP Generic Descriptor Model Generic Slip Model Attribute = SLIP_MODEL_ID = TNR_L2_DO Attribute = OBJECT_ID Attribute = DESCRIPTOR_ID …… Attribute = TRANSFERRED_FILE Attribute = DESCRIPTOR_ID …… Attribute = APPLICABLE_SLIP Specialised Descriptor Model Specialised Slip Model SLIP_MODEL_ID = TNR_L2_DO OBJECT_ID = Wind_waves_tnr_l2_20040610 DESCRIPTOR_ID = WIND_WAVES_TNR_L2_DATA …… TRANSFERRED_FILE = Wind_waves_tnr_l2_20040610.dat Wind_waves_tnr_l2_20040610.xml DESCRIPTOR_ID = WIND_WAVES_TNR_L2_DATA …… APPLICABLE_SLIP = TNR_L2_DO Instantiated Slip Instantiated Descriptor Wind_waves_tnr_l2_20040610 Specification for the Formal Definition and Transfer Phase

More Related