Producer-Archive Interface Methodology Abstract Standard - PowerPoint PPT Presentation

1 / 33
About This Presentation
Title:

Producer-Archive Interface Methodology Abstract Standard

Description:

Archive. specialized independent ... a Producer-Archive Project is a set of activities ... Increase data quality of archive holdings. Have weight and ... – PowerPoint PPT presentation

Number of Views:40
Avg rating:3.0/5.0
Slides: 34
Provided by: chucdbouco
Category:

less

Transcript and Presenter's Notes

Title: Producer-Archive Interface Methodology Abstract Standard


1
Producer-Archive Interface MethodologyAbstract
Standard PAIMAS
C. Huc/CNES, D. Boucon/CNES-SILOGIC,D.M.
Sawyer/NASA/GSFC, J.G. Garrett/NASA-Raytheon

2
Contents
  • Why a new standard?
  • Space data archiving
  • Needs for standardization
  • What standardization will bring
  • Abstract standard status
  • Proposed methodology
  • Context - description
  • The 4 phases
  • Specialization
  • Aid Tool for the use of the Methodology
  • Towards an implementation standard
  • Conclusions

3
Why a new standard?Space data archiving archive
types
4
Why a new standard?Space data archiving key
roles and players
  • Data Producers
  • the operating systems of each mission
  • the mission processing and archiving centres
  • the scientific teams in the laboratories
  • Archive
  • specialized independent organizations (CDS)
  • specialized services within the agencies (NSSDC)
  • services common to several organizations (CDPP)

5
Why a new standard?Needs for standardization
problems
  • The relations between archives and data
    Producers are rarely simple and easy
  • nonconformity of received data
  • unclear and imprecise definition of the data to
    be delivered,
  • failure to meet delivery schedule,
  • late detection of errors in archived data,
  • non-management of modifications
  • gt Can be detrimental to archived information
    quality and the cost of the operation.
  • Ever increasing diversity of the producers
  • Data complexity
  • Each project develops its own methodology on the
    basis of a process that is roughly the same from
    one project to another
  • gt Work duplicated, no generality, excessively
    high costs, etc.

6
Why a new standard?Needs for standardization
multiple standards
PAIMAS Generic abstract standard
Approved by the CCSDS
PAIMAS Implementation standard
Community abstract standard
Development in progress
7
Why a new standard?What standardization will
bring
  • Ease some typical problems (as noted earlier)
  • Make it easier to follow schedules and
    commitments
  • Help with human resources turnover
  • Anticipate new problems
  • Address the legal aspects early
  • Increase data quality of archive holdings
  • Have weight and credibility for adoption
  • And finally, save time (and money)

8
Why a new standard?Abstract standard status
  • Today CCSDS standard (blue book) and
    standardization with ISO in progress
  • Various communities have helped produce this
    document
  • space agencies (CNES, NASA, ESA, )
  • archivists (NARA, ) and
  • librarians (BNF -French National Library,
    RLG-Research Library Group).

9
Contents
  • Why a new standard?
  • Space data archiving
  • Needs for standardization
  • What standardization will bring
  • Abstract standard status
  • Proposed methodology
  • Context - description
  • The 4 phases
  • Specialization
  • Aid Tool for the use of the Methodology
  • Towards an implementation standard
  • Conclusion

10
MethodologyContext OAIS environment

11
MethodologyContext PAIMAS focus
AIP Archival Information Package, SIP
Submission Information Package, DIP
Dissemination Information package
12
MethodologyContext PAIMAS focus
Ingest
AIP Archival Information Package, SIP
Submission Information Package, DIP
Dissemination Information package
13
MethodologyDescription
  • The archive project is broken down into 4 main
    phases
  • Preliminary Phase,
  • Formal Definition Phase,
  • Transfer Phase,
  • Validation Phase.
  • Each phase has extensive action tables.
  • Specification for a community.

14
MethodologyThe phases relationships
  • Negotiate the Submission
  • Develop agreement (data to
  • be delivered, complementary
  • elements, schedule)
  • Identification and preliminary
  • agreement
  • Define the information
  • to be archived
  • resources estimation
  • Actual transfer of the data
  • Actual transfer of the
  • objects

Validate the transferred objects
Phase objective
Transferred object files
Preliminary Phase
Formal Definition Phase
Validation agreement
Preliminary Agreement
Dictionary Formal model Submission Agreement
Anomalies
Data ready to archive
15
Methodology Preliminary phase context
Producer
Preliminary Phase
Preliminary Agreement
Archive
16
MethodologyPreliminary phase sub-phases
17
MethodologyFormal Definition Phase context
Preliminary Agreement
Formal Definition Phase
Dictionary Data Model Submission Agreement
18
MethodologyFormal Definition Phase sub-phases
and action table
19
MethodologyTransfer Phase
Data Model of object files to deliver Schedule
Transfer Phase
  • Actual transfer of the objects
  • carry out the transfer test
  • manage the transfer

Transferred object files
20
MethodologyValidation Phase
Transferred object files
Data ready to archive
Validation Phase
  • Validate the transferred objects
  • carry out the validation test
  • manage the validation

Anomalies
Validation acknowledgement
Producer
21
Contents
  • Why a new standard?
  • Space data archiving
  • Needs for standardization
  • What standardization will bring
  • Abstract standard status
  • Proposed methodology
  • Context - description
  • The 4 phases
  • Specialization
  • Aid Tool for the use of the Methodology
  • Towards an implementation standard
  • Conclusion

22
Specialization
  • Adapt the generic standard to a particular
    community (which can range from an international
    organization to a simple archive service)
  • Steps involved to define a community standard
  • terminology,
  • data dictionary and information model,
  • standards,
  • common tools.
  • Analyze each action of the generic standard (add
    actions if necessary)

23
Specialization Example
  • Example (CDPP -Plasma Physics Data Center-
    Archive)

Generic Action (Methodology)
F-4 Define the formats, coding rules, and
standards to be applied for the objects
to be delivered
24
Contents
  • Why a new standard?
  • Space data archiving
  • Needs for standardization
  • What standardization will bring
  • Abstract standard status
  • Proposed methodology
  • Context - description
  • The 4 phases
  • Specialization
  • Aid Tool for the use of the Methodology
  • Towards an implementation standard
  • Conclusion

25
Aid Tool
A methodology application and archive project aid
tool would be a real advantage for both the
Producer and the Archive. First mockups produced
26
Aid Tool
27
Contents
  • Why a new standard?
  • Space data archiving
  • Needs for standardization
  • What standardization will bring
  • Abstract standard status
  • Proposed methodology
  • Context - description
  • The 4 phases
  • Specialization
  • Aid Tool for the use of the Methodology
  • Towards an implementation standard
  • Conclusion

28
Towards an implementation standardContext
Methodology application aid
PAIMAS Generic abstract standard
Implementation standard
Languages Tools


Archive project
29
Towards an implementation standardApproach
  • generic data model
  • transfer data model (generic objects)
  • transfer data dictionary (generic descriptors)
  • community dictionary
  • diagram of data to transfer for the
  • archive project
  • transfer sequencing and chronology
  • transfer session

Implementation standard
DEDSL
XML Schema
XML
Languages Tools
UML XMLScheme
DTD XMLScheme
XFDU
30
Towards an implementation standardRelationships
CLUSTER
CIS
CODIF
HIA
CLUS-CIS-CODIF-EAST
CLUS-CIS-HIA-EAST
CLUS-CIS-CODIF-Jm
CLUS-CIS-HIA-Jn
31
Towards an implementation standardSchema
  • Delivery plan
  • all the elements to be delivered
  • easy to understand from the Producer side
  • expression of constraints

32
Conclusion
  • PAIMAS identifies
  • the phases in the process of transferring
    information,
  • the objective of the phases,
  • the actions that must be carried out,
  • the expected results.
  • PAIMAS is a basis
  • for the identification of standards and
    implementation guides,
  • for identification and development of a set of
    software tools.

33
End of presentation
Write a Comment
User Comments (0)
About PowerShow.com