PDS4 Mission Proposer's Archive Guide Planetary Data System Mission Proposer's Archiving Guide (MPAG) September 21, 2016 Version 4.0.0
PDS4MissionProposer'sArchiveGuide
Planetary Data System Mission Proposer's Archiving Guide (MPAG)
September21,2016
Version4.0.0
PDS4MissionProposer'sArchiveGuide
i
Contents 1 Introduction.........................................................................................................................................1
2 PDSBackground...................................................................................................................................1
3 ATypicalPDSArchive...........................................................................................................................1
4 PDS4DetailsandDefinitionsofTerms.................................................................................................2
5 PDSArchivingProcess..........................................................................................................................3
6 PDSInvolvementinMissionPlanningandOperations........................................................................4
6.1 Pre-proposalBriefing...................................................................................................................5
6.2 ProposalDataManagementPlan(DMP).....................................................................................6
6.3 AdviseandAssist..........................................................................................................................7
6.4 MemorandumofUnderstanding(MOU).....................................................................................7
6.5 DataManagementPlan(DMP)andSoftwareInterfaceSpecifications(SIS)...............................8
6.6 ArchiveDelivery...........................................................................................................................8
6.7 PeerReview.................................................................................................................................9
7 EstimatingEffortandCostofCreatingaPDSArchive..........................................................................9
8 AdditionalInformation......................................................................................................................12
9 AppendixA:Glossary.........................................................................................................................13
10 References.....................................................................................................................................13
PDS4MissionProposer'sArchivingGuide
ii
CHANGELOG
Revision Date Description AuthorStartDraft April2,2003 Initialoutline R.JoynerVersion2.0 2014-05-1 UpdatedtocomplywithPDS4 R.Joyner
Version2.10 Date Description AuthorSection8 2015-10-19 Removedcostingsectionpendingrewrite
thatisvalidforPDS4(MCAI2015-09-28/01)Simpson
1.26.2
AppendixB
2015-10-19 Removedreferencestocostingsectionandwebpagewithcostingprocedure
Simpson
1.2 2015-10-19 CorrectedreferencetoAppendixC(nowtoB) Simpson1.4 2015-10-19 Updatedlistofapplicabledocuments Simpson2.03.5.23.5.46.5.17.07.5
AppendixA
2015-10-19 Minorgrammatical,wording,font,andpaginationcorrectionsandimprovements
Simpson
4.1.2 2015-10-19 NotedupcomingnodenamechangesatRingsandImaging
Simpson
7.5 2015-10-19 AddedsentencenotingthatENisthestewardforallcontextproducts.
Simpson
7.7 2015-10-19 Removedsectionheading(thereisnocontent)
Simpson
AppendixB 2015-10-19 Updatedreferences3and4,removed5and7;renumberedremainingreferences.
Simpson
4.1 2015-11-27 Changed“ManagementOffice”to“ProjectOffice”andupdatednamesofCISandRMSnodestoreflectnomenclatureasofDecember2015.CorrectedsentencestructurebyaddingverbstoDNsummaries.
Simpson
Version4.0 Date Description AuthorRewrite 2016-09-21 Restructuredandupdatedtobemission
oriented.T.King
PDS4MissionProposer'sArchiveGuide
1
1 Introduction NASA'sPlanetaryScienceDivisionsupportsawidediversityofprojectsrangingfrominvestigationsbyindividualresearcherstolargeflagshipmissions.AcrossthefullspectrumofprojectsNASArequiresthedataandotherresourcesthatareproducedtobepreservedinthePlanetaryDataSystem(PDS)oranequivalentarchive.ThisguidedescribestheprocessandrequirementswhenarchivingdatawiththePDS.ThebasicPDSarchivingrequirementsarethesameforalltypesofprojects.Howevertheroles,detailedsteps,andresponsibilitieswillvaryfromoneprojecttoanother,typicallyrelatedtothescaleoftheproject.ThisguideisaimedatNASA’scompetedflightmissions1.BeingfamiliarwithPDSconceptsandthegeneraldesignofaPDScompliantarchiveiskeytowritingasuccessfulDataManagementPlan(DMP)2inamissionproposal.Thisguidedescribestheitemsthatyou,asamissionproposer,needtoconsiderwhilepreparingaproposaltoaNASAflagship,explorerordiscoveryclassprogram.ThisguidealsoprovidesabriefsummaryofinformationfoundinPDSstandardsandwillhelpyoutoplanandestimatetheeffortofpreparingyourarchiveforsubmissiontothePDS.
2 PDS Background ThePDSarchivesanddistributesscientificdatafrommanysources,includingplanetarymissions,astronomicalobservations,andlaboratorymeasurements.Itspurposeistoensurethelong-termaccessandusabilityofdataandtosupportandstimulateadvancedresearch.AllPDSdataarepeer-reviewed,well-documentedandpubliclyavailable.Thatis,thedatamaybeexportedoutsideoftheUnitedStatesunderthe"TechnologyandSoftwarePubliclyAvailable"(TSPA)classification.
ThePDSisafederationofteamswithexpertiseindifferentsciencedisciplines.Eachteamiscalleda“node.”WithinthePDS,therearenodesfocusingonthescientificdisciplinesofAtmospheres,Geosciences,CartographyandImagingSciences,PlanetaryPlasmaInteractions,Ring-MoonSystems,andSmallBodies.Additionally,therearetwosupportnodesofthePDS:theEngineeringNodeandtheNavigationandAncillaryInformationFacility.Foracurrentlistofcontactsforeachnodesee
https://pds.nasa.gov/contact/contact.shtml
3 A Typical PDS Archive APDSarchivetypicallyincludesdata,labelscontaininginformationaboutthecontentandformatofthedata,anddocumentationaboutthedataandmission.Togetherthelabelsandthedocumentationmustbesufficienttoenableindividualstofind,readandusethedata.Thedocumentationshouldincludedescriptionsofwhichinstrumentwasusedtomaketheobservation,whatplatformwasthehostoftheinstrumentandwhichobjectswereobserved.Collectivelytheseprovidethecontextoftheobservation.Additionaldocumentationmayincludepapersorotherdocumentsthatdescribetheinstrument,calibrationstepsorprocessingthatwasperformed.Forthedata,thestructureandformatmustbedescribedinsufficientdetailtoenableotherstoreadthedata.BoththedatalabelsandthecontextdocumentationarespecifiedwithPDS-definedmetadataincompliancewithPDSstandards.Inparticular,thestandardsrequirethatdataproductsconformtothestructuresandformatsthatcanbe
1ThereisaseparateguideforR&AprojectscalledtheIndividualProposer'sArchiveGuide(I-PAG)2ADMPmaybeknownbyothernamessuchasDataManagementandArchivePlan(DMAP).
PDS4MissionProposer'sArchivingGuide
2
describedbyPDS-definedmetadata.Dataproductsthatcanbereadonlybyexternalsoftware(publicorproprietary)arenotcompliant.TomeetarchivingstandardsdatamustbereadableusingonlytherequiredmetadatainthePDSlabel.TheonlyexceptiontothisruleareSPICEkernels,asdefinedbyNASA’sNavigationandAncillaryInformationFacility(NAIF)node.Thecontextdocumentation,otherdocumentation,labelsanddataarelogicallygroupedintoanarchive,whichisplacedinthePDS,madeavailabletousers,andmaintainedindefinitely.EveryarchivesubmittedtothePDSmustpassapeerreviewpriortoitspublicrelease.
4 PDS4 Details and Definitions of Terms PDS4specifiesthestandardsandservicesusedbyPDS.PDS4isanintegratedsystemdesignedtoimprovediscoverabilityandaccesstodataacrossmultiplestoragelocations.EachitemstoredinaPDSarchive–whetherdata,documentation,orothermaterial–isconsideredaproduct.Aproductconsistsofthearchiveditemandthelabelcontainingitsmetadata.Everyproductisassignedauniqueidentifiersoitcanbereferencedandmanaged.Aproductisusuallyasinglefile,butitispossibleforaproducttoconsistofmultiplefilesdescribedbyasinglelabel.
ProductsareorganizedintoCollectionsandCollectionsareorganizedintoBundles.WhiledesigningaPDS4compliantarchiveitisimportanttokeepinmindthefollowinggeneralprinciples.
Everythingisaproduct.
Aproductisanyiteminthearchivealongwithitslabel.EachproductisassignedanidentifierthatisuniquethroughoutallofPDS.Productsmaybedata,documents,contextfiles,XMLschemaorotherdigitalobjects.
Collectionsaregroupsofsimilarproducts.
Acollectionconsistsofproductsthatshareoneormoreattributes.Theseattributescanbethetypeofproduct,atimerange,acquisitionmethod(i.e.,instrument),processingleveloranyotherlogicalattribute.Everyarchivedproductmustbelongtoacollection,soeveryarchivesubmissiontoPDSwillhaveatleastonecollection.Aproductmaybelongtomorethanonecollection,inwhichcaseitiscalledasecondarymemberoftheadditionalcollections.
Someexamplesofcollectionsare:
• DocumentCollection–Containsdocumentationnecessaryforunderstandingandusingthedata
• DataCollection–Containsobserved,derivedorgenerateddata,logicallygroupedbysharedattributes
• CalibrationCollection–Containscalibrationdataseparatedfromthedatacollection(s)and/ormoredetailedinformationaboutcomplexcalibrationefforts.
Bundlesconsistofrelatedcollections.
Abundlecontainscollectionsthatarerelatedbyahighlevelconceptsuchasproject,acquisitionmethod,processinglevel,orutility.Thecollectionsinabundlearecomplementarytoeachother.EveryarchivesubmissiontoPDSwillhaveatleastonebundle.
PDS4MissionProposer'sArchivingGuide
3
Forexample,abundlemayinclude:
• allcollections(data,document,calibration)foraparticularinstrument,or
• datacollectionsfromasinglelaborlabproject,or
• allcollectionsfromasinglefieldcampaign,or
• allcollectionsfromaresearchoranalysisproject.
Therelationshipamongproducts,collectionsandbundlesisshowninFigure1.InaPDS4archiveabundlecontainsPDS4metadatastoredasXMLdocumentswhichdescribethecollectionsthatarepartofthebundle.EachcollectioncontainsXMLdocumentsandrelatedfileswhichdescribetheproductsthatareincludedinthecollection.EachproductconsistsofanXMLdocumentandrelatedfiles.
Figure1Relationshipofproduct,collectionandbundle.
5 PDS Archiving Process ThePDSarchivingprocessconsistsofmultiplesteps,beginningwithidentifyingthedataproducts,designingthecollectionsandbundles,andcontinuingwiththecreationofcontextproducts,labelingofproducts,deliveryoftheproductstoPDS,conductingapeerreviewandresolutionofanyissuesdiscoveredduringpeerreview.IfanarchiveisincrementallydeliveredtothePDStheremayoneormoredeltareviewstoensuretheentirearchivecollectionmeetsPDSstandardsandrequirements.
PDS4MissionProposer'sArchivingGuide
4
Duringorpriortothedesignphase,missionandinstrumentpersonnelshoulddefinethedataproductstheyintendtoarchive,estimatetheirvolumeandgenerationrate,andnegotiateapreliminarydeliveryprocedurewiththePDS.Adequatedocumentationforbothunderstandingandusingthedataiscriticaltoeacharchive;missionplannersshouldbemindfulofthearchivedocumentationrequirementastheydevelopexplanatorymaterialsforotherpurposes.Asuitablearchiveincludescompletedescriptionsoftheoperationofeachinstrumentandofthecalibrationproceduresthataresuitableforgeneralrelease(ITAR/EARcleared).Itwillincluderawandprocesseddataalongwithallfilesneededtocarryoutthecalibration.Themissionproposalcalland/orNASAmanagersmayrequirespecificspecialorhigherlevelproducts.Thesemightincludederivedproductssuchasmosaics,maps,dataresampledtoacommoninterval,fitstomodelresults,orinversions.Theseproductswillalsoneedtobeincludedinthearchive.Additionally,amissionmaydeterminethatthereareotherproducts(combinationsofdatafrommultiplesources,theresultsofanalysesnotoriginallyplanned,etc.)thatareworthyofarchiving.ThePDSencouragesinclusionofthesespecialproductsinthearchive.
Forproductsthatrelyoncartographiccoordinatesystem-forexamplemaps,mosaicsandothergeospatialproducts-thecoordinatesystemmustfollowstandardsandpracticesoftheWorkingGrouponCartographicCoordinatesandRotationalElements(WGCCRE)oftheInternationalAstronomicalUnion(IAU).Thesestandardsandpracticesarespelledoutinonlinestatements(https://pds.nasa.gov/documents/sr/Chapter02.pdf;andhttp://sbn.pds.nasa.gov/data_sb/resources/coordinate_systems.shtml).Ingeneral,inorderforacartographiccoordinatesystemtobeusedinaproductthecoordinatesystemmustbedescribedindetailinpubliclyreleasedandperpetuallyavailabledocuments.Forexample,asawhitepaperarchivedinthePDSorasapaperinascientificpublication.SuchacoordinatesystemmustbeconsistentwiththatofdataalreadyinthePDSforthetargetbody(orbodies),musthaveaprimemeridianwhichisdefinedbyusingaclearlyidentifiablephysicalfeature,andmustbeconsistentwithanyestablishedIAUcoordinatesystemforthesamebody.
Inadditiontoacquireddata,themissionisexpectedtoarchivecompletegeometricdetailsfromlaunchthroughendofmission.Thesetypicallyincludethefullephemerisofthespacecraftandorientationofthespacecraftandallinstruments,therelationshipofthesetoeachotherandtocoordinatesystemsonthetargetandahistoryofallsignificantspacecraftevents.Additionally,housekeepingdata(suchastemperaturesandpowerlevels)thatmightbeusefulinunderstandingthebehaviorofinstrumentsmaybearchived.Themissionshouldalsoarchiveancillarydatathatareimportanttoeithermissionplanningorinterpretationofthedatafromthemission.Thesemightincludecontemporaneous,Earth-basedobservationsorkeymodels,suchasshapemodels,usedininterpretingthedata.Furthermore,inthecaseofradioscienceexperiments,radiometrictrackingdataarealsoarchived.
6 PDS Involvement in Mission Planning and Operations ThePDSrecognizesthatittakessomeefforttolearnhowtoproduceanarchivethatconformstoPDS4standards,andwewillhelpyouwiththis.ThetaskofcreatinganarchiveissharedbetweenthemissionandthePDS.ThroughallphasesofamissionPDSisaresourceyoucanrelyonforadviceandguidance.Thisincludesallthestepsinarchivingthedatafrompreparingaproposal,tocreatingaDataManagementPlan(DMP),totheoperationofthemissionandmakingdeliveriestothearchive.Ateverystep,frompreparingaproposaltomissionoperations,toarchivepreparationfeelfreetocommunicatewithPDSasoftenasneededtoensurethatyouapproacharchivinginanefficientmanner.Wecanassist
PDS4MissionProposer'sArchivingGuide
5
youinidentifyingthecomponentsforyourplannedarchive,assistindevelopingtemplatesforlabels,andhelpyouorganizethecollectionandbundlestructure.WhilewritingaproposalfeelfreetocontactthePDSNodemostcloselyalignedwiththeprimarygoalsoftheproject.Afterselection,thePDSManagementCouncilwillassignadisciplinenodeastheleadnode.Inmanycasesthiswillbethesamenodeyouinteractedwithduringthepreparationoftheproposal.
InthefollowingsectionswedescribewhatPDSwillprovideateachmilestone[1][2]overthecourseofaproject.Whiletheterminologyusedinthisdocumentmayvarysomewhatfromoneprogramtoanother,missionstypicallyhaveperiodsofadvancestudies,formulationandimplementation.Figure2showsthevariousphasesforamissionandthePDS-relatedmilestones.Someprojectsmayhaveadditionalmilestonesordocumentswhichareproducedandmayproducemultipledocumentstomeetamilestone.Insomecases,milestonesinvolvePDSsigningadocument,suchasthearchiveplansectionsinaproject'sDMP,orcertificationbyPDS,suchasinapeerreview.
6.1 Pre-proposal Briefing PriortoproposaldeadlinesforNRAsandAOs,NASAoftenorganizesapre-proposalbriefingtoprovideguidelinesandanswerquestions.Aspartofthisbriefing,PDSwillnormallymakeapresentationonhowPDSworksandwhatanarchiverequires.TheMissionProposer'sArchivingGuide(thisdocument)willbeprovidedatthebriefing.
AdvancedStudies
Formulation
Implementation
Step-1 Proposals (pre-Phase A)
Step 2/Study (Phase A)
Definition (Phase B)
Design and Development (Phase C/D)
Operations (Phase E)
Phases
KeyEvents
Reviews
PDSMilestones
ConceptSelection
IPR
Pre-proposal Briefing
Selection
TMCO PDR CDR TRR FRR SRR SDR
NOI
NOI–NoticeofIntentIPR–InitialProposalReviewTMCO-technicalmanagement,cost,andotherSRR-SystemRequirementsReviewSDR-SystemDesignReviewDMP–DataManagementPlanMOU–MemorandumofUnderstanding
PDR–PreliminaryDesignReviewCDR–CriticalDesignReviewTRR–TestReadinessReviewFRR–FlightReadinessReviewCERR–CriticalEventReadinessReviewAD–ArchiveDeliveryPAD–PDSArchiveDelivery
Advise MOU DMP Signed DMP
Archive Plan
Approval to Build
Approval to Launch
CERR
AD Peer Review
Figure2:Missionlifecycle,keyeventsandPDSmilestones.
Missionlifecycle,keyeventsandPDSmilestones
May occur multiple times
PDS4MissionProposer'sArchivingGuide
6
6.2 Proposal Data Management Plan (DMP) AmissionproposalisusuallyrequiredtoincludeaDataManagementPlan(DMP).WhilethespecificinstructionsfortheDMPmayvaryforeachmissionAnnouncementofOpportunity(AO),typicallyaDMPpreparedforaproposaldescribeshowthedatawillbeproduced,howandbywhomitwillbemanagedandhowitwillbearchived.AfteramissionisselectedamoredetailedDMPwillbecreatedwhichwillbemutuallyagreedtobytheprojectandthePDSwithfinalapprovalbyNASA(ProjectManagementofficeandtheProgramScientist).
BesuretocheckforanyrequirementsspecifictotheprogramtowhichyouareproposingbecausesomeprogramsmayhaveadditionalormorespecificrequirementsforthecontentsoftheDMP.
ThePDSrecommendsthefollowingtopicsforyourDMP:
• IdentifythePDSnodethatwillleadthePDSsideofthedataarchivingandanyotherPDSnodesthatwillinterfacewithinstrumentorcomponentteams.Includealetterofsupportfromeachofthenode(s)statingthatyouhavediscussedyourproposeddataproductsandthatthenode(s)willworkwithyoutoarchivethem.
• Discusstherolesandresponsibilitiesofteammembersinaccomplishingthearchivinggoals.
• Describeaschedulefordesign,productgeneration,validationanddeliveryofyourproducts.Besuretoincludetimerequiredforparticipatinginallstepsofthearchiveprocess(seeSection7).
• Includeageneralscheduleforsubmittingthemissionarchivesforreviewandreleasetothesciencecommunity.Amissionoflongdurationshouldplantoreleasearchivesatregularintervalsoverthecourseofthemission.UnlesstheAOspecifiesotherwise,thereleasescheduleshouldallowfortheaccumulationovernomorethanthreemonthsofeachbatchofdatatobereleased,andthereleaseshouldoccur,atthelatest,bythetimethenewestdatainthebatcharenomorethansixmonthsold.
• Outlinethedesignofyourarchive,includingthebundle(s)andcollection(s)aswellasanyderivativesofthedeliveredproducts(i.e.,browseimages),observationalgeometryinformationorsupplementalproducts
• Summarizetheproductsyouintendtoarchive,includingthedataproducts,documentation,geometryandancillaryinformation(e.g.,informationonhowthedatawereobtained,processed,calibrated---includeanythingthatauserwouldneedtoknowtouseyourdataasascientificproduct).Eachtypeofproductshouldbenamedanddescribedintermsofprocessinglevel,format,unitsofmeasure,andestimatedvolume.Table1showsthePDSprocessinglevelnamesanddefinitions.Itisnotnecessarytosubmitproductsateveryprocessinglevel,buttherawdataandatleastonelevelofcalibrateddataareexpected.Necessarydocumentationisinadditiontothedataproducts.
• Discusshowgeometryinformationwillbegenerated.Forexample,whetherSPICEwillbeusedorbysomeothermethod.
• Provideestimateddatavolume.Theestimateshouldincludeaccumulationsrates(bytesbyyear)andbesub-dividedbyinstrument.
PDS4MissionProposer'sArchivingGuide
7
Processinglevel DescriptionTelemetry Anencodedbytestreamusedtotransferdatafromoneormoreinstruments
totemporarystoragewheretherawinstrumentdatawillbeextracted.PDSdoesnotarchivetelemetry.
Raw Originaldatafromaninstrument.Ifcompression,reformatting,packetization,orothertranslationhasbeenappliedtofacilitatedatatransmissionorstorage,thoseprocessesareremovedsothatthedatavaluescanbereadilyused.TheseareoftencalledExperimentalDataRecords(EDRs).
PartiallyProcessed Datathathavebeenprocessedbeyondtherawstagebutthathavenotyetreachedcalibratedstatus.TheseandmorehighlyprocessedproductsareoftencalledReducedDataRecords(RDRs).
Calibrated Dataconvertedtophysicalunits,whichmakesvaluesindependentoftheinstrument.
Derived Resultsthathavebeendistilledfromoneormorecalibrateddataproducts(forexample,maps,gravityormagneticfields,orringparticlesizedistributions).Supplementarydata,suchascalibrationtablesortablesofviewinggeometry,usedtointerpretobservationaldatashouldalsobeclassifiedas‘derived’dataifnoteasilymatchedtooneoftheotherthreecategories.
Table1.DataProcessingLevels
6.3 Advise and Assist Earlyinthemissionlifecycle,PDSwillscheduleanorientationformissionrepresentativestodefinerolesandresponsibilitiesandtoestablishthesepointsofcontact:
• Missioncontacts• Instrument/ScienceTeamcontacts• PDSDisciplineNodecontacts
AnewmissionisusuallyassignedtoasinglePDSdisciplinenode,whichservesastheleadnodefortheremainderofthemission.Leadnodes,inturn,arrangeforsupportofindividualinstrumentteamsthroughotherdisciplinenodesasappropriate.Thisincludessupportforpotentialdatacontributorswithoutspecificinstruments,suchasInterdisciplinaryScientists.Theleadnodeworkswiththemissiontoensurethatarchiveplansaredeveloped,thearchivedesignsmeetstandardsandfacilitatecross-instrumentandcross-missioncomparisons,andarchiveproductionandvalidationrunsmoothly.ManyoftheseelementswillbeinthedetailedDMP.TypicallydevelopmentofthedetailedplansisdoneviaaDataArchiveWorkingGroup(DAWG)ledjointlybythePDSleadnodeandthemissionarchivinglead.DAWGmembershipincludesarchiverepresentativesfromeachinstrumentteamandeachPDSnodethatwillreceivedatafromthemission.
6.4 Memorandum of Understanding (MOU) EarlyinPhaseB,themissionandPDSwilldraftaMemorandumofUnderstanding(MOU)thatdefinesanddelineatestherolesandmutualresponsibilitiesregardingarchivinganddistributionofmissiondata.ForsmallmissionsNASAmanagementmaywaivetheneedforanMOU.IntheMOUthePDSManagementCouncilwillassignadisciplinenodeastheleadnode.
PDS4MissionProposer'sArchivingGuide
8
6.5 Data Management Plan (DMP) and Software Interface Specifications (SIS) OnceamissionentersthedevelopmentphaseitwillberequiredtogenerateadetailedDataManagementPlan(sometimescalledanArchivePlanorsimilartitle)asamissiondeliverable.AdraftofthisplanisusuallyrequiredforthemissionPreliminaryDesignReview.Theproposal'sDataManagementPlanwillbeausefulstartingpointforthemissionDataManagementPlan,butitsspecificcontentswilldependonmissionrequirements.
TheleadnodewillworkwiththemissiontocompletetheportionoftheDMPrelatedtoPDSarchives.TheDMPmustcontainsufficientdetailaboutthedataflow,archivalproducts,andproceduresforgeneratingthearchives;mustclearlyidentifytheindividualresponsibilities;andmustlayoutthescheduleforarchivedeliveriesandreleasetothesciencecommunity.Additionally,theDMPmustprovidesufficientdetailtoenableboththemissionandthePDStodevelopreliableestimatesofthepersonnelandothercostsfortheirrespectiveactivities.
EachinstrumentteamonthemissionwillberequiredtodocumentthedataproductstobegeneratedbytheirinstrumentinoneormoreSoftwareInterfaceSpecification(SIS).Thesedocumentsincludeenoughdetailaboutthedataprocessing,productstructure,format,andcontentstoenablesoftwaretobedevelopedtoreadandunderstandthedata.TheSISdocumentshelpsatisfythePDSrequirementfordocumentationandthereforeareincludedinthearchive.EachteamwillworkwithitsdesignatedPDSnodetowriteoneormoreSISdocumentstodescribeitsdataproducts.
Observationgeometrydataareessentialforproperlyinterpretingmissiondataandmustbeincludedinthearchive.AprogramAOmayormaynotspecifythemeansforgeneratinggeometrydata,butifyouarefreetochoose,bothPDSandtheInternationalPlanetaryDataAlliance(IPDA)recommendthatamissionuseNASA’sSPICEsystemtoproduceobservationgeometryparameterssuppliedwithsciencedataproducts.IfamissiondoesproduceSPICEdata,acomprehensivesetofmissionSPICEkernelsmustbearchivedattheNAIFnodeofthePDS.Ifamissionproducessomeotherformofgeometrydata,thatgeometrydataalongwithadequatedocumentationmustbeincludedinthesciencedataarchive.
Note:SomeprojectsmaycombinetheSISinformationintotheDMPandtherebyhaveasingledocument.However,theDMPisasignaturecontrolleddocument,whiletheSISisnot,soinallbutthesimplestcasesthetwodocumentsshouldnotbecombined.
6.6 Archive Delivery Nearlyallmissionscollectdataoverlongperiodsoftime.However,NASApolicyconsidersallscientificdatareturnedfromNASAmissionstobeimmediatelyinthepublicdomain.NASAalsorecognizesthatinordertoproducescientificallyusefuldataproductsthereneedstobeaperiodofexclusiveaccessbythemissionteams.Barringexceptionalcircumstances,theexclusiveaccessperiodmaynotexceedsixmonthsafterreceiptonthegroundofalldatawithinabatchofdata.Ablockofdatamaycontainuptothreemonthsofdatafromthetimeofdownlinkoftheearliestdataintheblock.Thismeansthatthenominalschedulefordeliveringdatatoanarchiveiseverythreemonths(quarterly),witheachdeliverycontainingthreemonthsofdata,anddeliveredsixmonthsafterthemostrecentlyacquireddataintheblock.EachdeliverymustoccurlongenoughbeforethereleasedatetoallowPDStovalidatethedelivery,typicallytwoorthreeweeks.TheschedulefordeliverieswillbedetailedintheDMP.Thedeliveriesmaybemadethroughascienceoperationscenter(SOC)ortheindividualinstrumentteams.
PDS4MissionProposer'sArchivingGuide
9
EachdeliverywillcontainproductsandotherinformationdetailedintheDMPandinconformancewiththeSIS.UponreceiptPDSwillacknowledgethedeliveryandcheckthedataforcompliance.
6.7 Peer Review PDSrequiresthatalldatasubmissionsfromdataproviderspassapeerreviewbeforebeingarchived.ThePDScoordinatesallpeerreviews.Duringapeerreview,reviewerswillevaluatetheusabilityofthedatabyutilizingthemetadata(inlabels)toreadandperformascientificassessmentofthedata.Inaddition,thecompletenessandaccuracyofotherinformationinthearchivesubmissionwillbeassessed.Anyissuesdiscoveredduringareviewareexpressedformallyasa“lien”againsttheproducts.Majorliensarethosesevereenoughtorenderaproducttobeunsuitableforscientificresearch.Minorliensarethosewhichmayaffecteaseofuse,completenessofdocumentation,qualityofinformation(i.e.,typosindocumentationormetadata)orothersimilarissues.Allliensmustbeaddressedbeforedataproductscanbearchived.Adataproviderisrequiredtoseetheprocessthroughtohavingtheproductsarchived,includingallottingenoughtimeforiterativeworkonthepreparationofproducts,supportingapeerreviewandcompletinganylienresolution.Afterallliensareresolvedtherewillbeadeltareviewtoconfirmthatthelienswereaddressed.ThePDSwillthenshowthedataas"certified"toindicatethatthedatawaspeerreviewedanddeemedtomeetPDSarchivingstandards.
Forshortlivedmissionswheredataisdeliveryoneortwotimes,thepeerreviewwilloccuraftereachdatadelivery.Formissionsthatoperateoveralongperiodoftimeand(typically)producelargeamountsofdatathataredeliveredincrementallyoverthecourseofthemissiontothePDSitispreferabletohavethedataprocessingpipeline"certified"byPDS.ForPDStobeabletocertifythepipelinetheremustbeawell-definedsetofprocessingstepswithversioncontrolonsoftwarecomponentsusedinthedataproduction,anddelivereddatamustindicatewhichversionofthepipelinewasusedtoproducethedata.TocertifyapipelinePDSwillreviewtheproductdesigndocumentationandsampleproductsbeforeanydeliveriesareplannedtobedone.Astheproject'sdataprocessingpipelinematures,andpriortofirstarchivedelivery,thePDSwillreviewtheproductsthatcomeoutofthepipeline.Theproductsarecomparedtothepeer-review-approvedproductdesigndocumentationtoensurethateverythingisasexpected.Inaddition,therecipientPDSnodewillvalidatethedeliveryforPDScompliance.Ifitisdemonstratedthatthepipelinereliablyproducescompliantproductsthenafullpeerreviewisnotconductedwitheverydelivery.Thisgreatlyimprovestheefficiencyofthearchivingprocess.Ifchangesaremadetopipeline,whetherbychangesinsoftwareorconfiguration,thepipelinewillneedtobere-certifiedbeforedatacanberoutinelyarchived.
7 Estimating Effort and Cost of Creating a PDS Archive ThetaskofcreatinganarchiveissharedbetweenthemissionandthePDS.
Tocoordinateamissionarchive,amissionwilltypicallydesignateanindividualtoserveastheMissionArchiveScientist.Thisindividualoverseesthearchivingactivitiesoftheentiremission.TheMissionArchiveScientististheprimarycontactbetweenthemissionandthePDSleadnode.
PotentialtasksandresponsibilitiesfortheMissionArchiveScientistinclude:
• PreparethearchiveportionsoftheDataManagementPlan.• Preparethedescriptivetextaboutthemission,instrumenthost(e.g.,spacecraft),and
referencestothecontextproductsforthePDSregistry.
PDS4MissionProposer'sArchivingGuide
10
• Ensurethetimelycompilationbymissionteammembersofcontextproductsspecifictoindividualinstruments(e.g.,instrument,spacecraft,andpersonnelfiles).
• EnsurethetimelycompilationbymissionteammembersofotherArchiveDescriptionDocumentationcomponents,asneeded.
• Ensurethatanycopyrightissueshavebeenaddressedifpreviouslypublishedmaterialistobeincludedinthearchive.
• Coordinatereviewofdocuments,calibrationinformation,andotherpartsofthearchivewhichmaybesensitiveforITAR(InternationalTrafficsinArmsRegulations)compliance.
• EnsurethatallfilesdeliveredtothearchiveareITARcleared.• Ensurecompatibilityofformatsanddefinitionsfromoneinstrumenttoanother.• Coordinatedeliveryschedulesforthearchivalproductsfromdifferentinstruments,
negotiatinganddocumentingschedulechangesasneeded.• Ensurethatalldatapreparersaremeetingtheirobligations/milestones.• Coordinatethemissionteamreviewsofthearchivingplansanddetailstoensurethatall
relevantinformationiscapturedinthearchive.• CoordinateappropriatemissionteamparticipationinthePDSorganizedpeerreviews.• Organizethemissionresponsestoanyliensidentifiedbythereviewprocesses.• Arrangeanydesiredtechnicalworkshopsforthemission.
Additionally,themissionwillidentifyoneormoreindividualswhowillpreparearchivedeliveriesforeachinstrument.ForsomeprojectsthisactivityiscoordinatedbytheMissionArchiveScientist.Thepreparationofarchivalproductsrequiresamixofscientificexpertiseandexpertisewithdataformatsandstandards.Sometimesasingleindividualcanfillbothroles.ArchivepreparerswillhaveearlyandcontinuedinteractionwithPDSpersonnelbecausearchivedeliverieswilloccurthroughoutthelifespanofthemission.
Duringoperations,thegeneraldivisionofeffortisasfollows:
Themissionperformsthefollowingtasks(usingmissionfunds):
• ProducesdataproductsinacceptablePDSformat.• ProducesPDSlabels.• Writessupportingdocumentation.• Organizesdata,labels,documentation,etc.intocollectionsandbundles.• ValidateslabelsusingPDSprovidedtools.• Participatesinpeerreview(maybedoneeitherface-to-faceorviaweb,emailandphone).• Makesupdatestotheproducts,asnecessary,basedonpeerreviewrecommendations.• Participatesindeltareview(ifneeded).• DeliversarchivepackagestoPDSonapre-determinedschedule.
ThePDSNodeperformsthefollowingtasks(usingPDSfunds):
• ProvidesadviceonPDSstandardsandrequirements.• AssistsindesigningPDSlabels,ifneeded.• Helpscreatecontextproducts.• ProvidesavailablePDStoolsandguidanceonuse.
PDS4MissionProposer'sArchivingGuide
11
• AcceptsthepackagesandtracksdeliveriestoPDS.• Setsupandconductsapeerreview.• Integratesthedataintoitsarchives,includingmakingitavailableontheNodewebsite.
Wehavefoundthatthisdivisionoftaskshelpstohaveanefficientarchivingprocess;however,theremaybesituationswherethisdivisionoftasksisnotpracticalorfullyachievablewithinthescopeoftheproject.PDSisheretohelp,socontacttheappropriatenodeanddiscusshowtheymightassistyou.
Ourexperienceindicatesthatpreparationofasimplearchive,consistingofonebundlewithafewcollectionswithalimitednumberofproductsandmodestdatavolume,maytakeonepersonuptoamonthofeffortspreadoverthefulldurationoftheproject.Foramissioneachinstrumentwillhaveoneormorebundlesandeachbundlewillhaveoneormorecollections.Additionally,atypicalmissiondeliversdatatothearchiveoveranextendedperiodoftime.Eacharchivedeliverytakestimetoassemble,deliverandreview.Itcantakeseveral(2-3)weekstoprepareandcompleteadeliverytoPDS.Tocalculatetheamountoftimeneededtocreatethearchiveoneneedstoconsiderhowmanyuniquecollectionswillbecreated.Ifcreatingmultiplesimilarcollectionsitwilltakesomeamountoftimeforthefirstcollectionandafractionofthattimeforeachnewcollection(incrementallymoretimepercollectionthanthefirstcollection),whereascreatingcollectionsthatareeachuniquewilltakeaboutthesameamountoftimetocreateeachcollection(proportionallymoretime).
DuringthecourseofamissionthetimespentoncreatingaPDSarchiveisspreadacrossthedesign,productgeneration,validation,productdelivery,peerreview,lienresolutionanddeltareview.Ingeneral,moretimeisspentonproductgenerationandvalidationthantheotherphases.Lienresolutioncanbetimeconsumingiftheproductgenerationgoesastray,butPDS4isdesignedtominimizethislikelihoodandthePDSNodeswillgiveyouguidanceonhowtoavoidanysurprises.PDSalsoprovidestoolstoaidinthedesign,generationandvalidationofproducts(seehttps://pds.nasa.gov/pds4/software/index.shtml).
PDSisyourpartnerinpreparinganarchive.Whilepreparinganarchiveyoushould:
• ExpecttocommunicateoftenandtoiteratewithaPDSNodeonarchivedesignandproductformats,labels,etc.
• ExpecttovalidateyourdatasubmissionusingPDS-suppliedsoftware.• Expecttoparticipateinproductdesignreviewsandsampledataproductreviews.• Bepreparedtoparticipateinapeerreviewofyourdatasubmission,withthesupportofPDS
Nodepersonnel.• Bepreparedtoresolveanyliens.• Bepreparedtoparticipateinadeltareviewofyourdatasubmission.
Toillustratehowtoestimatethearchivingeffortsconsiderthisexample.Amissionhasfiveinstrumentswitheachinstrumentdeliveringtwobundles(rawandcalibrated).Eachbundlewillcontainonecollectionthataccumulatesoverthecourseofthemission.Themissionwilltakethreeyearstocompleteresultingin12quarterlydeliveriestoPDS.Theminimumamountoftimeamissionshouldallocatefordesigninganarchiveandpreparingforthefirstdeliveryis10months(1monthforeachcollectionfor5instruments).Anadditionaltwomonths(2weeksperquarter)willbeneededeachyearofthemissiontopackage,deliveryandreviewthequarterlydeliveriestothePDS.Forthisexample,atotalof16months,distributedoverthedurationofthemission,willbeneededtoarchivethedata.This
PDS4MissionProposer'sArchivingGuide
12
wasasimpleexampleandmanymissionarchivesaremorecomplicated,requiringmoretimetobeallocatedforarchiving.
8 Additional Information WeunderstandthatnotalldataprovidershaveextensivebackgroundsinPDSstandardsandprocesses.WhilethisguidereflectstheinformationfoundinavarietyofPDSdocumentsandspecifications,youshouldrefertotheseadditionalresourcesformoredetailsandsuggestions:
• PDS4Concepts(https://pds.nasa.gov/pds4/doc/concepts)• PDS4StandardsReference(https://pds.nasa.gov/pds4/doc/sr/current)• PDS4InformationModelSpecification(https://pds.nasa.gov/pds4/doc/im/current)• SmallBodiesNodePDS4Wiki(http://sbndev.astro.umd.edu/wiki/SBN_PDS4_Wiki)
PDS4MissionProposer'sArchivingGuide
13
9 Appendix A: Glossary archive:Aplaceinwhichpublicrecordsorhistoricaldocumentsarepreserved;alsothematerial
preserved—oftenusedinplural.SometimescapitalizedwhenreferringtoallofPDSholdings—thePDSArchive.
bundle:Asetofcollections.Forexample,abundlecouldincludeacollectionofrawdataobtainedbyaninstrumentduringitsmissionlifetime,acollectionofthecalibrationproductsassociatedwiththeinstrument,andacollectionofalldocumentationrelevanttothefirsttwocollections.
collection:Asetofproducts,allofwhicharecloselyrelatedinsomeway.
dataobject:Aphysical,conceptual,ordigitalobject.
dataprovider:ApersonororganizationthatassemblesarchivaldatafordeliverytoPDS.
identifier:Auniquecharacterstringbywhichaproduct,object,orotherentitymaybeidentifiedandlocated.Identifierscanbeglobal,inwhichcasetheyareuniqueacrossallofPDS(anditsfederationpartners).Alocalidentifiermustbeuniquewithinalabel.
informationmodel:Arepresentationofconcepts,relationships,constraints,rules,andoperationstospecifydatasemanticsforachosendomainofdiscourse.
label:TheaggregationofoneormoredescriptionobjectssuchthattheaggregationdescribesasinglePDSproduct.InthePDS4implementation,labelsareconstructedusingXML.
labeltemplate:Atextfilewhichservesasapatternforconstructinglabels.
leadnode:OneofseveralconsultingnodesdesignatedasthePDScoordinatorandprimarycontactwithaproject.
lien:Aformallyexpressedissuewithoneormoreproductsinacollection.Minorliensarethoseintendedtoimprovethedataset,butwhicharenotconsideredcriticaltotheunderstandinganduseofthedata.Majorliensarethosesevereenoughtorenderthedataset(orincrement,inthecaseofdynamicdatasets)tobeunsuitableforscientificresearch.
logicalidentifier(LID):Anidentifierwhichidentifiesthesetofallversionsofanobject.
metadata:Dataaboutdata—forexample,a‘descriptionobject’containsinformation(metadata)aboutan‘object.’
product:Oneormoretaggedobjects(digital,non-digital,orboth)groupedtogetherandhavingasinglePDS-uniqueidentifier.InthePDS4implementation,thedescriptionsarecombinedintoasingleXMLlabel.ProductsarethesmallestaddressablegranularunitinthePDSholdings.
10 References [1]JPL:BasicsofSpaceFlight,Chapter7,https://solarsystem.nasa.gov/basics/bsf7-1.php
[2]NASA,2014DiscoveryProposalEvaluationPlan.http://discovery.larc.nasa.gov/discovery/pdf_files/Discovery_2014_AO_Eval_Plan_20150817_public_version.pdf