1

 Establishing a West African Science Ser‐vice Center on Climate Change and Adapted Land Use (WASCAL)  

Data Management Plan 

This Project Communication and Data Management Plan has been produced by theWASCALDataManagementExecutiveGroupat theoutsetof theWASCALproject,andhasbeenapprovedbytheWASCALInternationalAdvisoryBoard.ThePlanisintendedtohelpresearchteamstothinkabouttheirproject’sorganization,activitiesandrespon‐sibilities, in particular communication and dissemination activities, engagement withstakeholders,anddatamanagementneedsandresponsibilities.

TheplanaimstodescribetheapproachesnecessarytoimplementaWASCALdataman‐agement infrastructure. It concerns themanagement of data and data products to becreatedbytheCoreResearchProgram,theGraduateProgramandtheresearchteamsintheCompetenceCenter.ThedatawillbehostedandmanagedattheCompetenceCenter.Theplanactsasanagreementbetweendatausersanddataproviders/creators in theframeworkofWASCAL,onhowtouse,store,disseminateandpublishdatageneratedbytheproject.

The target audience for this plan is all projectmembers, in particular scientists fromGermanandAfricanresearchinstitutionsaswellaspartnerorganizationsprovidingandusingdataanddataproducts.

ThePlanalsoprovidesabasisfortheoverallplanninganddevelopmentofthecentralWASCALdatamanagementby:

providing informationthatcanbeusedtoco‐ordinatecommunicationactivitiesandstakeholderrelationsacrossWASCAL

highlightingdatamanagementandcustodyissuesatanearlystagesothatdataismanagedinawaythatmeetstherequirementsoftheWASCALprojectmanage‐ment,andenablestheProjecttorespondtocommondataneeds

providingabasisforqualityassurancewithintheproject providingabasisfromwhichWASCALprojectpartnersandtheprojectmanage‐

mentcanreportandmonitorprojectandoverallWASCALprojectprogress.

2

Authors:

Dr.RalfKunkel,ResearchCentreJülich,52425Jülich,Germany,E‐Mail:r.kunkel@fz‐juelich.de

AntonioRogmann,ZentrumfürEntwicklungsforschung,53113Bonn,Germany,E‐Mail:arogmann@uni‐bonn.de

JürgenSorg,FZJ,ResearchCentreJülich,52425Jülich,Germany,E‐Mail:j.sorg@fz‐juelich.de

ContentScheme:

DataManagementPlanningTool“DMPonline”(https://dmponline.dcc.ac.uk/)bytheDigitalCurationCentre(http://www.dcc.ac.uk/)

Version: 06

Date: 2013‐01‐06

Documentversion

0.2

Documenthistory:

2012‐06‐30 Firstdraft0.1(AntonioRogmann,RalfKunkel)

2012‐11‐30 Reviewingandextension(RalfKunkel,JürgenSorg)

2012‐12‐06 Reviewing(AntonioRogmann)

2013‐01‐06 Reviewing(RalfKunkel)

2013‐01‐15 Reviewing(AntonioRogmann)

2013‐01‐18 Reviewing(RalfKunkel,AntonioRogmann)

2013‐01‐27 Reviewing(AntonioRogmann,RalfKunkel,JoeHill)

2013‐01‐31 Seconddraft0.2,submittedtoProjectManagement

 

3

Content

1 BasicProjectInformation.................................................................................................................5

2 CaptureMethodsandManagementofResearchData..........................................................5

2.1 OverviewoftheWASCALDataInfrastructureSetup............................................................5

2.2 ExistingData...........................................................................................................................................8

2.3 NewData..................................................................................................................................................9

2.4 DataIntegrationandStandardization......................................................................................10

2.5 DataFormats.......................................................................................................................................10

2.6 NamingConvention..........................................................................................................................12

2.7 QualityManagement........................................................................................................................13

2.8 IntermediateandPersistentData..............................................................................................14

2.9 Versioning.............................................................................................................................................15

2.10 DataDocumentationandMetadata...........................................................................................15

2.10.1 MetadataStandards...........................................................................................................16

2.10.2 MetadataProfiles................................................................................................................16

2.10.3 MetadataCreationandManagement.........................................................................16

2.11 Georeferencing...................................................................................................................................18

3 DataRightsManagement:PrivacyandIntellectualProperty........................................18

3.1 EthicalandPrivacyIssues.............................................................................................................18

3.2 IntellectualProperty........................................................................................................................19

3.3 Licenses..................................................................................................................................................20

4 DataSharing.........................................................................................................................................20

4.1 AccesstoData.....................................................................................................................................20

4.2 ProvisionofData................................................................................................................................21

4.3 ReuseofDataoutsideofWASCAL..............................................................................................22

4.4 Citationrules.......................................................................................................................................23

4.4.1 CitationandAcknowledgmentofDataSourcesinPublications....................23

4.4.2 CitationandAcknowledgmentinPublications......................................................23

5 Short‐TermStorageandDataManagement..........................................................................24

5.1 StorageMediaandDataTransfer...............................................................................................24

5.2 Backup....................................................................................................................................................24

5.3 Security..................................................................................................................................................25

6 DepositandLong‐TermPreservation......................................................................................25

6.1 Long‐TermSpecifics.........................................................................................................................25

4

6.2 MetadataandDocumentationforLong‐TermPreservation..........................................25

6.3 Longer‐TermStewardship............................................................................................................26

7 Resourcing............................................................................................................................................26

7.1 OrganizationalRolesandResponsibilitiesforDataManagement...............................26

7.2 DataManagementActivitiesFunding.......................................................................................27

8 AdherenceandReview....................................................................................................................27

9 StatementofAgreement.................................................................................................................28

Annex1 Contactdetailsofnominateddatamanagers/namedindividuals...................29

A1.1 DataManagementExecutiveGroup..........................................................................................29

A1.2 DataManagementCouncil.............................................................................................................30

A1.3 ResearchWorkingGroup...............................................................................................................30

A1.4 InstitutionalDataManager...........................................................................................................30

Annex2 ListofcontributingorganizationstoWASCAL...........................................................31

Annex3 Glossary.......................................................................................................................................32

Annex4 Datamatrix.................................................................................................................................34

 

5

1 BasicProjectInformation

WASCAL (West African Science Service Center on Climate Change and Adapted LandUse)isanintegratedresearch‐focusedprogramdesignedtohelptacklethechallengeoffuture climate and landuse changes to enhance the resilienceof humanand environ‐mentalsystems.ItdoessobystrengtheningtheresearchinfrastructureandcapacityinWestAfricarelatedtoclimatechangeandbypoolingtheexpertiseoftenWestAfricancountriesandGermany.Scientificcompetencesallocated to theScienceServiceCenter(calledCompetenceCenterhereafter)willplayanimportantroleinregionallandman‐agementplanningandpolicyadvice.Theprojectconsistsofthreesubprojects:

The Competence Center (CC) develops local research capacity, and is a servicecenter forthepartnercountries,buildingonthenationalresearchcommunitiesof theWestAfricancountriesparticipating inWASCAL.Thecenterconnectsre‐gional partners in data‐collection networks (observation networks), and offersthe infrastructure and expertise necessary for analyzing the impacts of climatechangeandfordevelopingstrategiesandpoliciestocopewiththem.

TheCoreResearchProgram(CRP) isa joint researchprogramonadapted landuseandmanagementunderchangingclimaticconditions,whichbringstogetheraGermanandanequivalentWest‐Africanresearchconsortium.

TheGraduateResearchProgram(GRP)supportsandfacilitatesacademiceduca‐tionamongstWestAfricanuniversities inassociationwithGermancounterpartinstitutions.Theactivitiesfocusonthetrainingofdoctoralstudents.

The project is funded by the German Federal Ministry for Education and Research(BMBF)withinthetimeperiod2012‐10‐01to2016‐02‐29.Thecoordinatingorganiza‐tion is theCenter forDevelopmentResearch (ZEF)at theUniversityofBonn.A listofcontributingorganizationsisgiveninAnnex2.

DuetothepoliticalconditionsrelevantfortheestablishmentoftheCompetenceCenter,policies with regard to the protection of ethical standards and intellectual propertyrightsarestilltobedefinedandnegotiatedbytheWASCALSteeringCommitteetogetherwith the parties concerned. A preliminary draft is included in this DataManagementPlan. 

2 CaptureMethodsandManagementofResearchData

2.1 OverviewoftheWASCALDataInfrastructureSetup

TheWASCALDataInfrastructure(WADI)withintheCompetenceCenterwillserveasadatabasenodeprovidingscientistsanddecisionmakersinWestAfricawithreliableandwellaccessibledataanddataproductsrelatedtoclimatechangeandadaptedlanduse.

Furthermore,theWASCALDataInfrastructurewillplayasubstantialroleasanewandinnovative node in theWest‐African networkwhere research programs, projects andinstitutionsworkingonclimatechangeandrelatedtopicssharedataandknowledge.

6

ByfollowingtheconceptsofaSpatialDataInfrastructure(SDI),wherespatial(andnon‐spatial) data, metadata, users and tools are interactively connected1, a decentralizeddata infrastructurewillbeestablishedwithin the frameworkofWASCAL.This typeofdatainfrastructuresisalreadyusedsuccessfullyinseveralotherprojects,e.g.theinter‐disciplinary and long‐term research program TERENO, which involves six HelmholtzAssociationCenters(seehttp://www.tereno.net).

Thisdecentralizedsetupaimsatinterconnectingregionaldataandmetadatainfrastruc‐turesasfarastheyarealreadyestablishedatpartnerinstitutions,andunderthe“um‐brella”ofWASCAL.Acentraldataportalapplicationandacentralmetadatacalatogue(CMC)inWADIwillactasa“one‐stop”entry‐pointtothedatasharingnetwork,where,inadditiontoalldatabeinghostedbyWASCAL,dataandmetadataheldbyotherWest‐Africanandalsointernationalpartnerinstitutionscouldbelocalized,analyzedand‐de‐pendingonthedataowners‐retrieved.

DatapublicationandexchangewillbefacilitatedpredominantlythroughwebservicesasstandardizedbytheInternationalStandardizationOrganisation(ISO)andtheOpenGeo‐spatialConsortium(OGC)2,operatedfromtheCompetenceCenterorfromthedatapro‐viders.WADIcontainsthebasicfeatures:

a) AWASCAL portal application,which allows one to query, find and access datafromWASCALdatabases or external data infrastructures according to the datapolicy.

b) DefinedinterfacesfordataexchangebetweenWADIandregionaldatainfrastruc‐turesprovidedbystandardized,OGC‐conformalweb‐servicesoperatedinWADIand, as far as existent, in regional data infrastructuresmaintainedbypartners.Thefollowingweb‐servicespecificationswillbeinuse:

i. OGCSensorWebEnablement(SWE)standardsandinterfaceswillbeusedtoprovidebio‐physicaltimeseriesdatafromtheWASCALobservationnetworkstogetherwithcontextualdetailssuchas instrumentsused, intendedapplica‐tion, valid time, contact details to responsible persons, security level, geo‐graphiclocation.

ii. OGC compliantWebMap Services (WMS),WebFeature Services (WFS) andWebCoverageServices(WCS)willbeimplementedbyusingaweb‐mapserv‐er(Geoserver)toprovidemaplayersgeneratedfromvectordataorrasterda‐tatotheusers.Non‐OGCcompliantwebservicesmaybeimplementedtopro‐videadditionalfunctionalitiesnotcoveredbytheOGCstandardsandinterfac‐es specifications. Common data file download services (based on http, FTP,etc.)willbeconnectedtotheaforementionedserviceswhereappropriate.

iii. MetadatawillbepublishedbyOGCcompliantWebCatalogueServices(CSW)basedontheISO19115/19139metadatastandard.AsacentralentrypointtoWASCALmetadataaCentralMetadataCatalogue (CMC)willbecreated.TheCataloguewillusetheGeoNetworkOpensource3framework,whichisaCSWapplicationdevelopedbyFAO,WFPandUNEP,willbeusedtoquery,find,ac‐

1http://en.wikipedia.org/wiki/Spatial_data_infrastructure(accessed12.03.2013)2http://www.opengeospatial.org/(accessed12.15.2012)3http://geonetwork‐opensource.org/(accessed01.27.1013)

7

cessandeditmetadataanddataintheWADIandtoconnectexternaldatain‐frastructures. It supports multiple metadata standards (ISO19115, FGDC,DublinCore), contains an integrated map‐server and map‐viewer to accessdistributedmap‐services, isopensource, freeof costs, and supportedbyanactivedeveloperandusercommunity.Theonlinemetadataeditoroffersdif‐ferentdatasharingandsecuritylevels.

c) AcentraldatabasetomanageWASCALdatacreated,usedanddisseminatedwith‐intheCoreResearchProgram,GraduateProgramandtheCompetenceCenter.

Figure1showsthemainfunctionsandcomponentsrequiredforthecentraldatabasetobeimplementedattheCompetenceCenter.Basically,fourdifferentkindsofdatawillbemanaged:

a) FilebaseddatawillbemanagedbyaContentManagementSystembasedonthecontent management software Plone4, which combines traditional file storagewithmetadatasupportthroughWeb‐andCatalogue‐services,andtheaforemen‐tionedGeoNetworkmetadata‐catalogue(seesection4.2).BothinterfacesrelyonthesameservicestoaccessthedatabasesexecutedbyWADIandprovidethere‐foremerely different views on the databases by itsmetadata.Workflows, userroles,versioningandextensivedatasearchcapabilitieswillbeprovidedbythissystem.Accesstodataispossiblebydifferentinternetprotocols,e.g.HTTP,FTPand Web‐DAV. An internal WASCAL communication platform based on Plone,

4http://plone.org/(accessed01.27.13)

Figure1:ComponentsandfunctionsoftheWASCALdatainfrastructureWADI.

8

hosted at Research Centre Juelich, is already online since 2009(http://www.wascal.org).

b) TimeseriesdatafromtheobservationnetworkswillbestoredinarelationaldatabasesupportedbyaTimeSeriesManagementSystemdevelopedatFZJ,whichal‐lowsautomateddata input, standardizeddataanalysis anddataqualityassess‐mentroutinesneededtobecreatedaccordingtotheparticularrequirements.

c) Geospatial data will be stored either file based or in a spatial database (Post‐greSQLwithPostGISextension)andwillbeaccessedbygenericdatabase inter‐faces (e.g.pgadmin,phppgadmin,…), themetadata‐catalogueorby commercialGIS‐Serverapplications(e.g.ArcGISServerbyEsri).Thesedataareinternallyac‐cessiblebyvariousGIS‐clients,e.g.byArcGISorotheropensourceGISsoftware.DataexchangebetweenthedifferentWASCALpartners,authoritiesandotherus‐ersisrealizedbyweb‐servicesfollowingtheOGC‐specifications.

d) Remote sensing data may be stored either file based or in spatial databases.However,processingandcreationofnewproducts require special tools,whichareprovidedbyspecialistsystemsforremotesensingapplications.Dependingonthe amount of remote sensing data being collected at the Competence Center,suchasystemcanbeeitherincorporatedintotheWADI(seefigure1)orattachedtothesystemasanadditionallocaldatabaseconnectedtoWADIbytheOGCin‐terfaces.Theproposaloftheremotesensinggroupcontainsmoredetails.

Presently,therearenoout‐of‐the‐boxsystemsavailablewhichcanbeuseddirectlyforthesetupofWADI.Therefore,adaptationsofexistingsystems,e.g.theTERENODMI,toWASCAL’srequirementswillbemade.Theseadaptationsaremainlyattributedtodata‐basemodeldesignandtointerfacetoolsdevelopmentsbetweentheindividualsystemscomponents,whichhave to be developed according to the requirements identified bytheWASCAL users and/or researchers. A preliminary data sharing infrastructure hasalreadybeenimplementedatResearchCentreJuelichpriortotheWASCALmainphasestartinautumn2012.

2.2 ExistingData

Existing input data sets of different types (observations/raw data, derived data, etc.),requiredfortheworkpackagesoftheCoreResearchProgram(CRP)andthestudiestobe carried outwithin the Graduate Programwill be provided by external sources. Ofmain importance as data sources in this respect are collected or produced data fromprevious researchprojects, suchas the IMPETUSWest‐AfricaProject5and theGLOWAVoltaProject6.Otherexistingdatasetswillbeacquiredfromgovernmentalinstitutions,non‐governmentalorganizationsandprogramsaswellasbyinternationalprogramsintheregion,e.g.theAMMA7program,theFAO8,andothers.

AccesstothedataofinteresttoWASCALstoredinthedatarepositoriesmaintainedbytheprogramsandinstitutions,asmentionedabove,willbeorganizedbyestablishingadistributed,web‐servicebasedinfrastructure(seeprevioussection).Initialapproaches5http://geonetwork.impetus.uni‐koeln.de/srv/en/main.home(accessed01.27.2013)6http://131.220.109.2/geonetwork/srv/en/main.home(accessed01.27.2013)7http://database.amma‐international.org/(accessed01.16.2013)8http://www.fao.org/geonetwork/srv/en/main.home(accessed01.27.2013)

9

oncooperationwithpossiblepartnersinthisrespecthavealreadybeenestablisheddur‐ingthepreparationphase,aswithVBA(owneroftheGLOWAVoltadatabase),IMPETUS,AMMA,GEOSS,etc.

PreliminaryinformationontheexistingdatastockusedinWASCAL,andonthenewda‐taup‐comingintheproject’s lifetime,aresummarizedinadatamatrix(seesection1).The information on this data stockwas gainedby surveyswhereCRP scientistswereaskedtocontributeto.AssoonasthedataisavailableandrequiredbyseveralusersinWASCAL,itwillbestoredinWADItogetherwithaccompaniedmetadata.

2.3 NewData

Theresearchregionischaracterizedbydatascarcityandexistentdataoftentimesisnotsuitable for the research purposes due to various reasons such as unknown quality,missingmetadataorinaccessibility.Therefore,thegenerationofnewdataisofutmostimportance to fill gaps inknowledgeon regionalphenomena, and to feedavarietyofmodelsand tools for scenariodevelopmentwhichwill serveas the scientificbasis forpolicyadvicetonational/regional/localstakeholders.WithinWASCALnewdatawillbecapturedorcreatedby

biophysicalandsocio‐economicobservationnetworks

datacollectionbyindividualresearchersfromexternalsourcesandowninvesti‐gations

data creation by individual researchers by processing raw data from externalsourcesorowncollections

observationsprovidedbyWASCALObservationNetworksandremotesensing:

o Landcover/usedataandessentialclimatevariables(ECVs)capturedbyavariety of remote sensing instruments in different spatial (West‐AfricanSudan Savannah belt to focal watersheds) and temporal resolutions(minutes,hours,daystodecades,dependingonparameters)

o Hydrologicaldatagatheredbyaregionalobservationnetwork,distributedoverMali,BurkinaFaso,Togo,Coted'Ivoire,BeninandGhana

o Meteorologicaldatagatheredbyaregionalobservationnetwork,distrib‐utedoverMali,BurkinaFaso,Togo,Coted'Ivoire,BeninandGhana

o Biodiversitydatacollectedfromanobservationnetworkwithinandnear‐bythefocalwatershedsandfromBIOTAWestobservationsites

Socio‐economicdatageneratedbyhouseholdsurveys.

AspreparatoryworkforthemanagementofdatatobecollectedorcreatedbytheCoreResearchProgram,datasurveyshavealreadystartedtobecarriedoutduringtheprepa‐rationphaseofWASCAL.Ananalysisoftheresearchproposalswithregardtodataandapplications(models,software‐tools,etc.)tobecreatedandusedduringtheproject(re‐sults,seesection1)wascarriedoutatthebeginningoftherequirementsanalysis.Basedonaquestionnairedeliveredto thescientistsof theCRP,detailed informationondataarebeinggatheredandcompiled intodatamatrices.Thematricesprovidedetailed in‐formation on dataset and parameter characteristics, and are structured in input‐ andoutput‐dataperwork‐package.Animportantdetailistheexpectedtimeofavailabilityofthedata,becauseintimedataflowsamongtheCRPmembersandtheCCresearchteamsrelyona clear scheduling. From the results adatabase isbeing created,whichallows

10

queriesandreportsbythedatamanagementexecutivegroupforitsdatamanagementplanningregardingdatasupplyanddemand.

Noteverywork‐packagewasabletospecify itsdataprovisionsoverthecompletelife‐timeoftheproject,attheprojectoutset,thereforetheabove‐mentionedsurveywillberepeatedfromtimetotime.InadditionthequestionnaireaskswhichsoftwareistobeusedbyscientistsintheframeworkofWASCAL(firstresults,seeAnnex4).This infor‐mationwillbeused toplansoftwareprocurementand installation in theCompetenceCenter.DemandsondatasupplyintheCompetenceCenterarenotspecifiedindetailasyet,butlistingswiththematic,datatypeandapplicationrelatedgroupingsofdatatobeusedandproducedintheCCduringtheproject’slifetimewillbepreparedasfarasnec‐essary.

2.4 DataIntegrationandStandardization

Inordertoensurecompatibilityindataintegrationbyseveralapplications/models,de‐tailed standards and regulations for particular data groupswhich are not covered bycommonstandardizationrules,willbespecifiedincooperationwiththerespectivesci‐entificexpertsintheirfields.Integrationbetweenthedatabeinggatheredintheprojectandpre‐existingdatasourceswillbemadeonseverallevels,asfarasappropriate:

Observablepropertylevel:whereneeded,transformationofunitsandrecalcula‐tionsofvalues

Formatlevel:reformattingtostandardizedformats(seenextsection)

Geographic reference system level: transformation to standardized coordinatesystems

Documentationlevel:useofstandardizedmetadataprofiles

Temporalandspatialscales(bymetadata).

TheDataManagement ExecutiveGroupwill provide reference tableswithmandatorystandardvocabulariestobeusedinWADItotheWASCALcommunity.

2.5 DataFormats

Datastorageanddata formatshighlydependonthe typesofdatawithinadatastock,whichcanbeveryheterogeneous.Basically,dataofinterestinWASCALcanbeclassifiedasfollows:

Structured(quantitative)data:

o Time series data provided by online in‐situ or remote sensors, to bestoredinrelationaldatabases

o Tabular (statistical)dataderived frommeasurements, surveysorgener‐atedbysimulations,tobestoredinfilesorrelationaldatabases

Unstructured(qualitative)datasuchasdescriptivedocuments,audio‐andvideodata,pictures,storedinfiles

Georeferenceddatastoredinfilesorrelationalgeodatabases

o Vector‐basedandattributedgeodata

o Rasterbasedgeodata

11

Exceptforunstructuredinformation,alldataisbeinginterpretedbycomputerprogramstomakeitunderstandableandis‐byitsverynature‐softwaredependent.Dataarethusendangeredby theobsolescenceof thehardwareandsoftwareenvironmentonwhichaccesstodatadepends.Thebestoptiontowarrantinteroperabilityofdatabetweenva‐rietiesofapplicationsandoverthelongtermistoconvertdatainnon‐proprietaryandstandardizedopen‐formats.Nevertheless,archivingofdatainproprietaryformats9canbe required in cases wheremeaningful content would get lost when storing in openformats, e.g. formulas and diagrams in MS Excel tables when exporting in comma‐separatedvalues(ASCII/CSV)files.Inordertosavestoragespaceonthehard‐drivesoftheserver,uploadeddatamaybestoredascompresseddatafilepackages(e.g..zip,.7z,.rar).

ThefollowingfileformatsfordatawillbesupportedbyWADI:

Typeofdata Preferableformatsforexchangeandreuse

Acceptableformats

Qualitativedatatextual

Richtextformat(rtf),OpenDocumentText(.odt),PlainText(.txt),eXtensibleMark‐upLanguage(XML)textaccordingtoanappropriateDocumentTypeDefinition(DTD)orschema(.xml)PortableDocumentFormat(.pdf),

Hypertextmarkuplanguage(.htm),Widelyusedofficeformats(e.g.MSWord) 

Quantitativetabu‐lardata(withorwithoutcolumnla‐beling,variablesnamesandmetada‐ta)

CommaSeparatedValues(.csv),Tab‐delimitedFile(.tab),OpenDocumentSpreadsheets(.ods),ExtensibleMarkupLanguage(.xml),SPSSportableformat(.por)NetCDF(.netcdf),HierarchicalDataFormat(.hdf)

MicrosoftExcel(.xls,.xlsx),dBase(.dbf),SPSS(*.sav)MSAccess(.mdb,.accdb)

Digitalimagedata Bitmap(.bmp)JointPhotograficExpertsGroup(.jpg,.jpeg)PortableNetworkGrafics(.png)

TaggedImageFile(.tif,.tiff)Georeferencedvec‐tordata

ESRIshapefile(essential‐.shp,.shx,.dbf,optional‐.prj,.sbx,.sbn)GeographicMarkupLanguage(.gml)CADdata(.dwg)

ScalableVectorGraphics(.svg)KeyholeMark‐upLanguage(KML)CADdata(.dxf)MapInfoInterchangeFormat(.mif)

Georeferencedras‐ GeoTIFF(TaggedImageFileFormat/.tif,.tiff),

9E.g.MicrosoftFormats:Excel,Word,etc.(http://en.wikipedia.org/wiki/Proprietary_format)(accessed01.28.2013))

12

terdata NetCDF(.netcdf)EsriASCIIorbinaryGrid(.asc,.flt)HierarchicalDataFormat(.hdf)

Digitalaudiodata FreeLosslessAudioCodec(FLAC)(.flac)

#MPEG‐1AudioLayer3(.mp3)WaveformAudioFormat(WAV)(.wav)

Digitalvideodata MPEG‐4(.mp4),motionJPEG2000(.mj2)

 

Duetotheextensivedatavolumesandforreasonsofaccessibility,timeseriesdatafromin‐situandremote sensorswillnotbe stored in simple filebased formatsbut in rela‐tionaldatabasesystems.Fordatastorageinthedatabaseandregistrationofthesensormetadata,anunderlyingdatamodelfortimeseriesdatawillbeused,whichstoresenvi‐ronmental observations along with sufficient metadata to provide traceable heritagefromrawmeasurementstousableinformation.

2.6 NamingConvention

Data file names should reflect file content as best as possible. Therefore all filenamesmanagedbyWADIwilluseaconsistentnamingschemedefinedasfollows:

<Project>_<ScientificDiscipline/MainTopic>_<ThematicContent/Parameter>_<SpatialCoverage>_<TimeFrame(‐TimeStep)>_

(<SpatialGeometryType>)_<VersionNo>.<extension>

Withinone<element>severalitemsaretobeseparatedbyahyphen(‐),while<ele‐ments>aretobeseparatedbyanunderline(_).Therefore,thedatafilesmayhavethefollowingnames:

WSC_hyd_soil‐moisture_bf‐dano‐watershed_20000101‐20061231‐h_v1.csv

WSC_soc_household‐income_burkina‐dano‐watershed‐diebougou_2013.xls

Thecontentofthetagsare:

<Project>: denotestheprojectthedataisattributedto(e.g.WASCAL=“WSC”)

<ScientificDiscipline/MainTopic>: abbreviatesthedisciplineand/ormaintopicthedataisattributedto.Codingexamplesmaybe:adm=Administrativehyd=Hydrologyclim=Climatology

<ThematicContent/Parameter> denoteseitherthethematiccontentortheparame‐ter,whichisdescribedbythedata(e.g.reservoirs,temperature,regional‐capitals,food‐security)

13

<SpatialCoverage> denotesthespatialextentofthedata(e.g.=ghana,ghana‐tamale,burkina‐dano‐watershed)

<TimeFrame(‐TimeStep)> denotesthetemporalextentofthedata(e.g.2010,20000101‐20061231‐h)

<SpatialGeometryType> specifiesthetypeofspatialgeometryincaseofgeodata.Codingexamplesmaybe:pol=Polygonpnt=Pointlin=Lineras=Raster

<VersionNo> specifiestheversionofthedataset(e.g.v1)

<extension> fileextensionaccordingtothetypeofdata(e.g.csv,xls,seesection2.5)

WhenuploadingdatatoWADI,datafilesmayautomaticallyberenamedaccordingtothecommon file names scheme using common metadata entries provided by the us‐er/uploaderofthedata.Thepossiblecontentoftheindividualtagsusedforfilerenam‐ing are provided by common vocabularies specified in reference tables,which can beaccessedanddownloadedfromtheWASCALdataportal.

2.7 QualityManagement

Thelevelofdataquality,followingthecommondefinitionofdataqualityi.e."Thestateofcompleteness,validity,consistency, timelinessandaccuracy thatmakesdataappro‐priateforaspecificuse"10,ishighlydependentontherealworldphenomenarepresent‐ed by the data and data products. To carry out data quality assessments specialistknowledgeonthefieldofdatagenerationisdemanded.Therefore,the 

a) responsibilityfordataqualityassessmentsandassurancemeasuresisbythesci‐entistsgeneratingorworkingonthedata.

b) datacreatorswillberequestedbythedatamanagementresponsibletodescribethedataqualityassurancemeasuresandtogiveanevaluationonthetrustwor‐thinessofthedatawithintheCentralMetadataCatalogue.

AllWASCALdatamustbeattributedbytheresponsiblescientistswithrespecttoitsdataqualityanddataprocessinglevels.Thisistobedonebyacombinationofadataqualifierandaprocessingstatusflagassignedtoeachdataset.Thesequalityinformationareei‐therstoredinthemetadataforentiredatasets(geodataorotherfilebaseddata)oronthelevelofindividualobservationsfortimesseriesdata.

The data qualifier provides qualifying information that can note validity informationaboutthedata(like“visuallychecked”)oranythingunusualorproblematicaboutindi‐vidualobservations(suchas, forexample, "holding time foranalysisexceeded"or"in‐completeorinexactdailytotal").AlistofdataqualifierswillbeelaboratedbytheDataManagementExecutiveGroupincollaborationwiththeresponsiblescientistsinthefirstphases ofWASCAL, published as a reference table byWADI, andwill continuously berevisedondemand.

10http://en.wikipedia.org/wiki/Data_quality(accessed01.05.2013)

14

2.8 IntermediateandPersistentData

Alldatacreated,collectedandusedbytheWASCALprojectandbeingregardedasvalu‐ableforverifyingscientificfindings,reuseinfurtherresearchandintegrationinpolicyadvice statements,will stored inWADI or in connected data infrastructures as far asauthorizedbyWASCAL.However, inorder toavoidoverflows in thedata repositoriesand the accumulation of unnecessary and unneeded data versions, scientists shouldcarefullyevaluateifadatasetshouldbesharedbyintegrationintothedatabasesornot.

Inthedataprocessingchainadatasetmighthaveanintermediatecharacter.

Theprocessingstatuscharacterizesthegeneralprocessingstepsthatthedatahavebeensubjected to.Dependingon theparametersbeingcontrolled, severalprocessingstatuslevelsaredefined:

Processinglevel“L‐1”:RawDataRawdataisdefinedasunprocessedorpreliminarypre‐processeddataanddataproductsthathavenotundergonequalitycontrol.Dependingonthedatatypeanddatatransmissionsystem,rawdatamaybeavailablewithinsecondsorminutesafterreal‐time.

Processinglevel“L‐2”:QualityControlledDataQualitycontrolleddatahavepassedqualityassuranceproceduressuchasroutineestimationoftimingandsensorcalibrationorstatistical/visualinspectionandremovalofobviouserrors.

Processinglevel“L‐3”:DerivedProductsDerivedproductsrequirescientificandtechnicalin‐terpretationandincludemultiple‐sensordata.

Processinglevel“L‐4”:InterpretedProductsTheseproductsrequireresearcher(PI)drivenanaly‐sisandinterpretation,model‐basedinterpretationusingotherdataand/orstrongpriorassumptions.

Processinglevel“L‐5”:KnowledgeProductsTheseproductsrequireresearcher(PI)drivenscien‐tificinterpretationandmultidisciplinarydatainte‐grationandincludemodel‐basedinterpretationusingotherdataand/orstrongpriorassumptions.

Withtheintentiontodescribephasesincreatingscientificandpublishablefindings,thestateofdataprocessingcanberelatedtospecificresearchdomains.ResearchDomainsdefinethegroupofuserswithwhomdatawillbeshared11.Thelistingbelowservesasanorientationguideforthedecisionastowhetherdatashouldbeup‐loadedintoWADIornot.Ifindoubt,theWASCALDataManagementExecutiveGrouportheprojectcoor‐dinatorsshouldbeconsulted.

11Treloar & Harboe-Ree, 2008 (http://www.valaconf.org.au/vala2008/papers2008/111_Treloar_Final.pdf accessed 10.24.2012)

Rawdata

Intermediateresults

Finalresearchresults

15

a) PrivateResearchDomain:Involvesmembersofacoreresearchteam,e.g.awork‐packageintheCoreResearchProgram.Datausedinthisdomainusuallyrepre‐sent raw, preliminary or intermediate rather than final research findings. Datamanagementandsharingoccurswithintheteam,andispre‐definedasmembersonly.

Therefore,datadonothaveto,butmaybeintegratedinWADIorinanexter‐nal Data Management Infrastructure connected to WADI. In case data isstored in the researchdatabasesaccessiblebyWADI, itbecomesaccessiblewith restrictions, such as for instance forwork‐packages or Core ResearchProgram teammembersonly (mappedas a specific „user group in the sys‐tem)

b) Shared Research Domain: Involves researchers collaborating with a core re‐searchteam,oftenacrossinstitutions.Datasharedmostlyrepresentintermediateresearchresults,whicharenotthesubjectofascientificpublicationasyet.

Therefore,datahave tobe integrated inWADIor inanexternalDataMan‐agementInfrastructureconnectedtoWADI,butthedataaccessisrestrictedto members of a research cluster, the research groups in the CompetenceCenterortoWASCALstaffasawhole(mappedas“usergroups” inthesys‐tem).

c) PublicDomain: Involves thepublic sphere.Datamayhaveallprocessing statesandmaybeusedinorreferencedbypublications.

Therefore,datahave tobe integrated inWADIor inanexternalDataMan‐agementInfrastructureconnectedtoWADI,andwillbeaccessiblebythesci‐entific community, decision makers, politicians and the interested, non‐commercialpublic.

2.9 Versioning

Withinadataprocessingchainseveralversionsofadatasetmaybecreated.Aversioncanrepresentastatusintheprocessingchain,orasmallmodificationmadetothedataduetootherreasons.Versioningmightalsooccurinscenariosbeingresultsofmodeling.

Versionscanbemarkedsimplybyaddingaversionnumbertothefile‐,database‐name,database‐record or to a data‐identifier, e.g. <file/database/database‐record‐name><version‐number>, respectively, by adding a time stamp. In addition, par‐ent/childrelationshipsmaybeincludedintheCentralMetadataCataloguetodocumentseveralstatesintheprocessingchainasversions.

Where required server‐clientbasedversioncontrol softwarewill beused, e.g.ApacheSubversion(SVN).Subversionmanagementsoftwareiscommonlyusedinsoftwarede‐velopmentenvironments,whereseveraldevelopersworkonthesoftwarecodelocally,and code extensions ormodifications aremerged to a software code repository on aserver.SVNclientsareconnectedtotheserverbycommondatatransferinternetproto‐colsaslikeFTP,SFTPorSCP.

Thepossibleusefulnessoftheabove,andimplementationforotherapplicationse.g.cli‐matemodeling,intheframeworkofWASCALwillbediscussedwiththerespectivespe‐cialistsintheDataManagementCouncil(see7.1b)attheprojectoutset.

2.10 DataDocumentationandMetadata

16

Datadocumentation throughmetadata is anessential requirement for theassessmentandevaluationofdatawithinadata infrastructure.Moreover, thetaskofadata infra‐structuretodisseminateandtopromotetheusageofthedatausuallyfailsifthedataarenotproperlydescribedand,asaconsequence,usersarenotableto judgewhetherthedatacontentisrelevantandthedataqualityissufficienttotheirspecificneeds.

InWASCAL, metadata will be managed and published and, in case of file‐based datamanuallyprovidedtotheWADIbyscientists,becreatedbyusingthetoolsprovidedbyaCentralMetadata Catalogue (CMC) application integrated in theWASCAL data portal.Thesetoolsprovidetheuserwithfacilitiestouploadresearchdatawithitsmetadatainoneworkingstep.Ametadatasetconsistsofseveralelementstodescribethedata,e.g.author, abstract, lineage, data quality, etc. In order to exchangemetadata with othermetadatacataloguesorcomparableapplications,internationalapprovedstandardsandprotocolswillbeused(seesection2.10.1).

2.10.1 MetadataStandards

Theprincipalmetadatastandard for filebaseddataandgeodata tobeused is the ISO19115 "Geographic Information ‐ Metadata" standard, in xml‐encoding following ISO19139. These standards are widely established within distributed spatial data infra‐structures,wheregeoreferenceddatarepresentalargeproportionofthedatastock.ThesetofmetadataelementsintheISOstandardsiscapabletocovermostdata‐types,data‐topicsanddata–processes,evenfordatawithoutcoordinate‐basedspatialreference.Ifnecessary,theISOstandard19110todescribefeaturetypes(e.g.intabulardataonat‐tribute level) will be used. For digital documents (qualitative) and any other type ofqualitativedigitalweb‐content,DublinCorewillbeusedasthemetadatastandard.

Hydrologicalandmeteorologicaltimeseriesdatagainedfromtheobservationnetworkwill be distributed by web‐services, which provides the data together with basicmetadata. The metadata scheme provided by these services corresponds to the Sen‐sorMLspecificationbasedontheSensorWebEnablement(2.0)initiativeoftheOGC.

Metadataisretrievedfromtherelationaldatabaseinwhichthedataisstored,andwillbeintegratedand/orconvertedintotheserviceconfigurationbytheDataManagementExecutiveGroupincooperationwiththescientistsresponsiblefortheObservationNet‐workintheCompetenceCenter.

2.10.2 MetadataProfiles

Everyusergroupwillbeprovidedwitharangeofmetadataprofiles/templatestailoredto therequirementsofspecificdatagroups(e.g. remotesensingdata,sociologicalsur‐veys,statisticaldata)undertheircustody.TheprofilesaresubsetsofthebasicstandardISO19115,whichconsistsofaround400metadataelements,andwhichhelptheusertoworkmoreeconomicallywiththemetadataeditorsintheCMC.AlreadyestablishedISO19115profileswill be evaluated against the needs ofWASCAL (e.g.WMO‐Core). Ownprofiles,willbedevelopedbytheDataManagementExecutiveGroup,togetherwithre‐sponsiblepersonsfromtheWASCALresearchgroups,andimplementedintheCMCasfarasissuitable.

2.10.3 MetadataCreationandManagement

Creationandcapturingofmetadatadependsonthetypeandoriginoftheresearchdata.Someapplications (e.g.ESRIArcGIS)arecapable tocreateandexportmetadata intoa

17

standard,whichiscomplianttotheWASCALmetadatastandards.Standalonemetadataeditorsbasedon theWASCALstandardsarealsoavailable (e.g. the INSPIREMetadataeditor12or CATMDEdit13) and can be used alternatively. As soon as it is connected toWADI themetadata canbe imported togetherwith thedata into theCMC. In general,however,metadataforfile‐baseddatawillbecreatedonlinethrougheditingtoolswithintheWASCALDataPortalapplication.Thelifecycleofmetadata,fromcreationandcon‐tentcontrollingofametadataset,toitspublicationintheweb,ismanagedbydedicateduserprofilesinthesystem.ThemembersoftheDataManagementExecutiveGroupwilltrain the users to use the metadata‐editing tool. The process of establishing thesemetadatacreatinganddatasharingworkflowswillbe leadandsupportedbytheDataManagementExecutiveGroupaswell.Inthecreationandmanagementofmetadatathefollowingrulesapply:

a) Every data set stored or archived in WADI must be described by meaningfulmetadata,complianttothedefinedmetadatastandardsandprofiles.

b) It is the responsibilityof thescientists respectively theWASCALstaffmembersup‐loadingdatatoWADItoprovidepropermetadatawiththedata.She/hewillbe granted the “editor” role in the user accountmanagement system ofWADI,which enables him/her to create, edit and delete his/her ownmetadata in theCMC.

c) Foreveryworkinggroupatleastoneresponsiblepersonwillbenominated(seesectionAnnex1),whowillbeinchargetocontroltheuploadandthedistributionofdatathecontentandthecompliancetothestandardsofthemetadatacontrib‐utedbycolleaguesinthegroup.ThispersonshouldbememberoftheResearchand Institutional Data Manager Working Group (RIDMG) (see section 7.1 c)).She/hewillbegrantedthe“ContentReviewer”orthe“Useradministrator”roleinthesystembywhichmetadatacontentanddatadistributioncanbecontrolledonworkinggroupbasis.

d) ThemetadatamustcontaineitheraURLtotheonlineresourceforaccessingthedatadirectlyoratleastthecontactdetailswherethedatacanberetrievedwhenstoredlocally.

e) Metadata is allowed to bemodified on any occasion by the owner, but itmustcontainabasicsetofmetadataelements–mostlypartofbyadedicatedmetadataprofile(seeprevioussection)‐tobeclassifiedas“completed”.

f) Datamayberejectedfrombeing importedintothe infrastructure ifproperandcompletedmetadataarenotdeliveredwithinacertaintimeperiodafterupload‐ingthedata.

In addition, controlled vocabularies such as keyword‐thesauri, reference tables, fixedcategoriesetc.willbeimplementedincoordinationwiththeusers,tosupporttheeasyfindingofdataby filteringthemetadata.TheGeneralMultilingualEnvironmentalThe‐saurus(GEMET)isthefirstchoiceforthematicthesaurusimplementation,togetherwitha thesaurus for spatial locations. Furthermore, for example,more scientific disciplineorientedthesauri,maybeincludedinthecatalogueifrequiredbytheusers.

12http://inspire‐geoportal.ec.europa.eu/editor/(accessed01.15.2013)13http://catmdedit.sourceforge.net/(accessed01.15.2013)

18

2.11 Georeferencing

Inordertocreatemapsbyoverlayinggeospatial layersgeneratedfromgeodataofdif‐ferentsourcesitisimportantthatthelayerssharethesamegeographiccoordinatesys‐tems(GCS)andprojections.Specificrequirementsontheaccuracyofspatiallocalizationmaydemandtheuseofregionalorlocalcoordinatesystemsandprojections.However,when submitting geospatial layers toWADI the geodata should be referenced by theWorldGeodeticSystem1984(WGS1984).Thereforeitmightberequiredtotransformthegeodata, e.g. fromUTM intoWGS1984,beforeuploading intoWADIorpublishingthegeodataasWebMapServicelayers.ThelayersbasedontheoriginalGCScanbeadd‐edtotheuploadasitdeemsnecessary.

3 DataRightsManagement:PrivacyandIntellectualProperty

Datasharingandre‐use issubject to legalregulations.Therefore, thedatarightsman‐agementisofcrucialimportanceinthedatamanagementframework,andofhighpriori‐tyineachandeverydatamanagementplan.Thissectioninthedatamanagementplanwillbedevelopedby theWASCALDataManagementExecutiveGroup, incoordinationwiththeresponsiblebodiesintheWASCALprojectconsortium,andwiththehelpofle‐galexperts.AssoonasitislegallyapprovedandadoptedbyallrelevantpartiesinWAS‐CAL,itwillbepublishedofficiallyandcomplementthedatamanagementplan.

Inthefollowingapreliminarydraftforadatarightsmanagementstatement,andrespec‐tively a data policy, is provided. Asmentioned, it might be adapted to the legal con‐straintsresultingfromthepoliticalandthereforejuristicconditionsinwhichWASCAL,andrespectivelytheCompetenceCenter,isembedded.

3.1 EthicalandPrivacyIssues

Ingeneral,personaldata,whichisdatacharacterizinganindividualhumanbeing,issub‐jecttoparticularprotection.Inresearch,personaldatacontainingprivacy‐sensitivein‐formation(e.g.householddatawithprivate/personalmaterialor familydetails,whichleadbacktotheindividuals)canbeusedandprocessedonlywiththeconsentofthein‐dividualssupplying thedataor information.Correspondingly, inpublicationspersonaldatacanbeusedonlywiththewrittenconsentofthepersonsconcernedinthedata.InWASCALthefollowingprivacyruleswillbeapplied:

a) DatawithprivacycontentwillbestoredinWADIonlywithadocumentcontain‐ingthetermsofusebeingsignedbytheindividualsconcerned.

b) Providedthattheresearchpurposeisnotaffected,thedatawillbeanonymizedassoonaspossibleby,e.g.

i. removingdirectidentifiers,e.g.names,addressesorspatiallocalizations

ii. generalizationofvalues,e.g.rangesofhouseholdincomes

iii. storingthedatabyseparatingcharacteristicsofpersonalormaterialcir‐cumstanceswhichcouldbeattributedtoanidentifiedoridentifiableper‐son. This can be done, for example, by storing the data in separatedfiles/tables connectedby identifiers (primary/foreignkeys).Approachesin thisrespectwillbedevelopedwith thosescientistswhoproducedataforwhichprivacy,e.g. fromlocalstakeholderswithinhouseholdsurveys,needstobemaintained.

19

c) Dataprivacyprotection statementshave tobe included in themetadataby thecreatorofdatacontainingprivacy‐sensitiveinformation.

d) Thecreatorofdatacontainingprivacy‐sensitiveinformationisresponsibletore‐stricttheaccesstothisdatabyusingthemeans,whichareprovidedbytheWAS‐CALCentralMetadataCatalogue(CMC).

e) Ifaresearcherdependsonusingdatawithsensitivepersonalinformationinhisstudies,privacyprotectionstatements,basedonthetermsofuse(seeundera)inthissection)integratedinthedataretrievalprocesswouldhavetobesignedbythedatauserbeforeaccessingthedatasets.

3.2 IntellectualProperty

Intellectualpropertydoesnotprotectbarefacts/data,butratherprotectsonlytheforminwhich facts and/or data are presented.With regard to scientific outcomes literaryworks,suchaswrittenworks,speechesandcomputerprograms,illustrationsofascien‐tific or technical nature such as drawings, plans, maps, sketches, tables and three‐dimensionalrepresentationsareprotected,onlyinasfarasthattheymeetthetwore‐quirements:originality(anintellectualcreation)andindividuality(i.e.havingapersonalfeature).

Asaconsequence,noteverytypeofdataisregardedastheintellectualpropertyoftheconcernedscientist,neitheriseverytypeofdataprotectedbycopyrightlaw.Anexampleisrawdatafrombiophysicalmeasurementscollectedbyinstrumentsorbystandardizedscientificmethodologies.Datanotsubject to copyright canbesubject toownershiporuserighthowever,forexamplebytheownerofthemeasuringinstrumentorthedonorofadatacollectionactivity.

Althoughintellectualpropertyrightsarenon‐transferableingeneral,arightholdercanoriscommittedtogivethelicensetootherpartiestousethedata.Alicensecancontainallsortsofregulations(seesection3.3).InWASCALthefollowingintellectualpropertyruleswillapply:

a) Data created by WASCAL staff members that are not considered intellectualproperty,areownedbytheWASCALproject.

b) Bysigningadatasharingagreement(reflectingtherulesasstatedinsection4.1)everyregularlyemployedWASCALstaffmember,whoistheholderofdatacon‐sideredtobeintellectualproperty,grantsadatauselicense(seesection3.3)totheWASCALproject.

c) Withthedatauselicense,WASCALisauthorizedtomakethedataaccessiblebymeansofWADI, and in turn to grantuse licenses to stakeholders for scientific,policy‐adviceanddecisionmakingpurposesrespectively,byputtingthedata inthepublicdomain.

d) DatauselicensestobegrantedfordatainthecustodyofWASCALcanbelimitedtoindividualusersorgroupofusers,ortemporarilyberejectedifrestrictionsasdefinedinsection4comeintoeffect.

e) DataundertheownershipofpartnerinstitutionsbutalsoincustodyofWASCALduetoitsstorageinWADIwillbeprotectedagainstunauthorizedaccessonthebasisofagreementsbetweenWASCALandtherespectivepartnerinstitutions.

20

3.3 Licenses

Copyright law provides the intellectual property rights holder with the possibility togranta license to thedatauser.A license isauseragreement, signedbybothparties,whichstatesthescopeforusingthedata.Ininformationsystems,however,whereusa‐ble items under intellectual property can be downloaded, a license is included in themetadata and/or oftentimes in the order process, so that by downloading it the useracceptsthelicense,forinstancebyclickingaspecialcheck‐box.InWASCALthefollowinglicensingruleswillapply:

a) WASCALstaffmemberswillsignadatasharingagreementwithWASCAL(basedontheregulationsstatedinsection4.2)atthebeginningoftheirworkinWAS‐CAL.Thisagreement includesadatause license tobeprovidedto theWASCALproject,andrespectivelytheCompetenceCenter.Thisuseright licenseincludestherighttodisseminatethedatatootherpartiesasdeemednecessarybyWAS‐CAL,butonlyinconsiderationoftherulesasstatedinsection4.2.

b) WASCALgrantsdatause licensestodatausersbasedonthe license frameworkprovided by the non‐profit organization Creative Commons14(e.g. by a licensetype <Attribution‐NonCommercial‐ShareAlike 3.0 Unported – CC BY‐NC‐SA3.0)15>.

c) The licenseswill citedasabstractswithin themetadataof thedata. InadditiontheURLtothedetailedlicensedefinitionatCreativeCommonswillbeincluded.

d) Inthemetadata‐cataloguethelicensewillbeincludedintheorderprocessforda‐taunderintellectualproperty,sothatbydownloadingit,theuseracceptstheli‐cense by entering his/her name and email‐address, and by clicking a specialcheck‐box.

e) DatainthepublicdomainwillbemarkedwithaPublicDomainMark.Itmightberestrictedtonon‐commercialpurposes.

4 DataSharing

4.1 AccesstoData

ProjectdatahostedbyWADIwillbeaccessibletoprojectpartners,andrespectivelythepublic,assoonasthisisdemandedbytheresearchteamsand/ortheprojectcoordina‐torsandtheExecutiveDirector.

InWADIlegalrequirementswillbemappedtoafine‐graineduserandusergroupstruc‐ture.Thisstructurewillregulatethedisseminationofdataanddataproductsbyreflect‐ingtherightmanagementdemandsasdelineatedinsection3.Thereforethefollowingrulesapply:

a) Fordatanot subject to intellectualproperty rights:MostlyL‐1 toL‐2data (seesection2.8)andownedbyWASCAL.Willbeaccessiblebyeveryoneintheinter‐net forscientificpurposes.An identification/registrationof theuser inWADI is

14http://creativecommons.org/ (accessed 12.17.2012)15http://creativecommons.org/licenses/by‐nc‐sa/3.0/legalcode (accessed 12.17.2012)

21

notrequired.Apublicdomainmark(seesection3.3e)willbeattachedtotheda‐ta.

b) Fordatafallingunderintellectualpropertyrights:MostlyL‐3toL‐5datawithadatauselicenseatWASCAL:

i. Canbeaccessibleforeveryoneintheinternetforscientificpurposeswith‐outanyidentificationofthedatarequestinguser.Thedatauselicensewillbeattachedtothedata,andneedstobeacceptedbytheuserwhendown‐loading(bysubmittinghis/hernameandemail‐address).

ii. Access can be restricted toWASCALmembers or specific groups in andoutside ofWASCAL forwhatever reasons (e.g. due to publication inten‐tions).Theserestrictionshavetobecommunicatedtotheprojectcoordi‐nators,andthedatamanagersneedtobeinformed.Theuseridentifiedasamemberofsuchacloseddatasharingnetwork,andrespectivelyasau‐thorizedbythedataprovider,needsanaccountinWADItoaccesstheda‐ta.Adatauselicense(seesection3.3b)willbeattachedtothedata,andneeds to be accepted by the user when downloading (by submittinghis/hernameandemail‐address).

c) Fordataownedbyexternalprojectpartners(e.g.Met‐orHydro‐Services):accessrestrictions and data use licenseswill applied as statedwithin bilateral agree‐ments.

d) Foruseraccountsandgroupmemberships,whichgrantaccess todatasets:willbeadministeredbytheWASCALDataManagementExecutiveGroup,andrespec‐tively the data managers in the Competence Center, in collaboration with themembersoftheDataManagementCouncil.Informationonhowtogetpermissiontodownloadrestricteddata(“orderinginstructions”)isincludedinthemetadataoftherequesteddata.

e) DatadownloadswillberegisteredbynotificationsintheformofanemailsenttoaresponsiblememberoftheDataManagementCouncil inWASCAL(section7.1b))orResearchandInstitutionalDataManagerWorkingGroup(section7.1c).

ThemainentrypointtoWADIwillbeprovidedthroughtheWASCALhomepage,whichconnectseithertotheCentralMetadataCatalogueapplicationortootherdataqueryanddataaccesstools.

4.2 ProvisionofData

InordertoguaranteecontinuitytotheresearchactivitieswithinWASCAL,itisessentialthatdataproducedbyoneresearchgroupismadeavailableassoonaspossibletotheotherresearchgroupsorindividuals,andrespectivelytoexternalpartnersormembersoftheworldwidescientificcommunity.

In producingdatasets to be exchanged, site operatorsneed to refer to this dataman‐agementplan,inparticulartosections2.4to2.10.

Inconsiderationoftherequirementsandproceduresasfixedinsection3,thefollowingrulesfordataprovisionapply:

a) The project coordinators are the authorities to decide on data sharing and ex‐change.Theywillsettleconflictsinafriendly,mutuallyunderstandingmannertothe benefit of all stakeholders. Theywillmake sure that a scholar is contacted

22

whenhis/herdataaretobeusedbyothers.IncaseofconflictthedecisionrestswiththeWASCALExecutiveDirector.

b) InternaldocumentsorprojectrelatedannouncementshavetobepublishedandexchangedbyusingtheWASCALhomepage.Alotherdata,dataproducts,docu‐ments,models,softwarecode,etc.whichisofinterestfor in‐andoutsideoftheprojectwillbepublishedandexchangedbyusingtheCentralMetadata‐CatalogueintegratedinthedataportalofWADI.

c) SeniorscientistsandregularstaffmembersofWASCALhavetoprovidethedatatoWADIassoonasitispreparedforexchange,andbyfollowingthestandardsasexplained in sections2.7‐2.10and the recommendations in section2.8, butnotlater than2months after its acquisition.Access restrictions to thedatawill beregulatedasmentionedinsection4.1.

d) PhDstudents(“scholars”),whoarefundedbyWASCALhave

i. priorityrightstopublishhis/herdatafirst,e.g.aspartofhis/herPh.D.orpublication,asfarasthedata(L‐3toL‐4,section2.8)issubjecttointellec‐tual property rights. If this priority right is not used, then after an ade‐quate timespan (24months), this right ispassedover to theproject. Inpracticethismeansthatonwardsfromthetimetherightispassedtotheproject, the coordinators in consultationwith the executive director de‐cidehowthedatawillbeused.Ifpossible,theywillconsultandinformthescholarabouttheirdecisions

ii. theobligationtouploaddatawhichisnotsubjecttointellectualpropertyrights (mostly L‐1 and L‐2 data, section 2.8) together with adequatemetadataintoWADIbyusingtheCMCapplication.

e) IfthestudyisaPh.D.studyconductedatapartneruniversity,e.g.theUniversityofBonn, then the rulesof theUniversityapply.Atpresent, such rules stipulatethatadataCDshouldbehandedovertothecoordinatorofthePh.D.programatZEForuploadedintotheZEFDataPortal(onlinespring2013)attheendofthestudy.ThisCDisstoredatZEFfor10years.However,ifthestudyisatanyotherpartnerinstitution,thentheirruleapplies.

f) Monitoringdatafromtheobservationnetworksaretobemadeavailableonlinewithinthreemonthsafterinstallation.

g) Projectdataaretobemadeavailablebydatabaseaccesswithinthreemonthsaf‐ter theWASCALprojectends,oraccording tootherallocatedsubmissiondead‐lines. It will be the Institutional Data Manager’s responsibility to ensure thatsubmissiondeadlinesareobservedandtochasepossiblydelayedormissingda‐ta.

h) For data provided by external parties, individual agreementswill bemade be‐tweenWASCALandresponsiblepersonsfromthedataprovidingandusingpart‐nerinstitutions.

4.3 ReuseofDataoutsideofWASCAL

WASCAL is an interdisciplinarymulti‐partner project, with the aim to provide policymakersandstakeholdersintheareaof ‘landuseadaptationtoclimatechangeinWestAfrica’withuseful informationbasedon the researchwork tobemadeby seniorand

23

juniorscientists intheWASCALCoreResearchProgram,thegraduateschools,andtheresearchteamsintheCompetenceCenter.

Other organizations and programsworking on comparable scientific agendas, such astheAMMAprojectandtheGEOSSprogram,nationalpoliticalbodiesandNGOs,willbeinterestedinthedatatobemadeavailablebyWASCAL.

TheCompetenceCenteristobeestablishedasapermanentinstitution.Datamanagerswillhavetofurtherdevelopdatamanagementstrategiesfittingup‐comingrequirementsinresearchanddecisionmaking,andconsideringnewconceptualandtechnologicalde‐velopmentsrelevantforthemanagementofdata(asfarasthisfallswithintheresponsi‐bilityofthedatamanagers).

4.4 Citationrules

4.4.1 CitationandAcknowledgmentofDataSourcesinPublications

WhendatastoredinWADIandobtainedfromtheDataPortalisusedwithinapublica‐tion, the source of the data is to be cited by including a persistent URL (<server‐address><UUID of themetadataset>),which addresses themetadata in the CMC. Thelinkcaneitherbeincludedasafootnoteorinthereferences/bibliography.Ifdataisob‐tained from other colleagues within WASCAL, these other colleagues must be citedproperlyaccordingtothepossiblecases:

a) If the data have been produced in actual fieldwork by one personwithin theWASCALproject, thesepersonsshouldbeacknowledged, citedorevenbecomeco‐authors.

b) IfthedataisavailablefromtheWASCALDataPortal,acitationoftheURLtothemetadataset intheCMCissufficient,becausethemetadatacontainsthedetailsfromthedatacreatorandcontributors.

c) Ifaninstitutionhasprovidedthedataset(generallythecasewithsecondaryda‐ta),theinstitutionmustbecited.

d) Ifconsiderableeffortsoftwoormorepersonsgointoonedataset,jointpublish‐ing (i.e. thenamingofbothasdata sources/authors inapublication) is recom‐mendedandappropriate.

e) Whengatheringorpreprocessingofprimarydatawassubstantiallysupportedbyothers(e.g.studentassistants),theyshouldalsobeacknowledged.

4.4.2 CitationandAcknowledgmentinPublications

WhenaWASCALstaffintendstopublishdata,researchresultsandinformationespecial‐lyinaninternationalcontext(journal,book,conference,andsoon),severalregulationsshouldbefollowed.Ineachpublicationareferencetothedonorsandtheexecutingin‐stitutes must be made: this is mandatory. For example, the acknowledgement in thepublicationmaystateoneof:

a) This research was conducted in the framework of the WASCAL project (PN:01LG1202G) funded by German Federal Ministry for Education and Research(BMBF)”

b) This research projectwas carried out under the auspices of the agreement onscientific‐technologicalcooperationsignedbythegovernmentsofGermanyand‐

24

‐‐.TheGermanpartnerwasfundedbytheGermanFederalMinistryforEducationandResearch(BMBF).TheWASCALPartnerwassponsoredbyMinistryof….TheexecutingpartnersweretheCenterforDevelopmentResearch(ZEF)oftheUni‐versityofBonn,Germanyandthe……….

c) Priortosubmittingthedocumentforpublication,permissionshouldberequest‐edfromtheeditorialcommitteeofWASCALwhichconsistsof…..persons:Thedi‐rectorofZEF‐,……………..,…………,……….. .Onlyafterapprovalthedocumentcanbesubmitted.

d) Oralpresentationsandposterpresentationsofthescientificworkinanykindofmeetingmustbeprecededby adry runwithin a groupof project participants.Thiswillservenotonlyasaformoftrainingandasameanstocommunicatethepresentation’s intentions,butalsoasanoccasiontoobtainpossiblecorrectionsforanymisinterpretationsofdata.

5 Short‐TermStorageandDataManagement

5.1 StorageMediaandDataTransfer

DatatobeexchangedandpublishedinsideaswellasoutsideofWASCALwillbestoredonstoragedevicesonserversattheCompetenceCenter.Primarystoragewillbeaccom‐plishedusingRAIDharddrivedisksonastorageareanetwork(SAN).InadditiondataarestoredinrelationaldatabasesystemsandWeb‐basedcontentmanagementsystems,enablingdataaccessviaHypertextTransferProtocol(Secure)(HTTP(s)),(Secure)FileTransfer Protocol ((s)FTP), Secure Shell (SSH), Server Message Block Protocol(SMB/CIFS)andWeb‐basedDistributedAuthoringandVersioningProtocol(Web‐DAV).FordatatransferfromandtotheCompetenceCenterit isespecially for largedataob‐jectsnecessary toprovidea software tool that enables resumea transfer after an ab‐normalconnectionlosttoavoidresubmittingalreadysubmitteddata.Thisisparticular‐lynecessarybecauseofacomparativelypoorcommunicationinfrastructurewithinAfri‐ca.

Datafrompartnersmightbestoredintheirowndatainfrastructuresandlinkedtothecentraldatainfrastructurebystandardizedwebservices(seesection2.1).Independent‐lyoftheactualdatastoragedevicesintheWASCALdatainfrastructure,aregistrationofdatasetinthemetadatabasetogetherwithdistributioninformationgivinginstructionswheretoaskfordatahastobemadeatleast.

5.2 Backup

DatabackupinWADIisaccomplishedusingregulardataandsystem(virtualmachines)backupsonharddiskdrivesandregulardataarchivingusing tapedrives.Backup fre‐quencieswilldependonthedatamodificationratebutwillbeatleastoneperday.Ar‐chiveofdatatotapedrivedriveswillbeperformedifnecessary.TheresponsibilityfordatabackupandarchiveiswiththeWASCALdatainfrastructureadministratorsrepre‐sentedby theWASCALDataManagementExecutiveGroup,andrespectively, after im‐plementationofWADIattheCompetenceCenterbyitsdatamanagers.

Institutionaldatamanagers(section7.1c))areresponsiblefortheimplementationandsupervisionofproperdatabackupandarchivestrategiesintheirinstitution.

25

5.3 Security

During the project's lifetime access restrictions and data security is ensuredby usingcommonITcomponentssuchasfirewalls,virus‐scanners,secureconnections(ssl,tls,…).Accesstodataprovidedbyinternalandexternalwebservicesmayberestrictedtotakeplace via WADI based on Lightweight Directory Access Protocol (LDAP) technology.Basedondatapolicyagreements,usersneedtoberegisteredinthedatainfrastructure.Everyuserwhoaccessesrestricteddataoughttosignanagreementinwhichthelicenseconditionshavetobeconfirmed(see3.3).

Accesscontrolwillbe implementedonaperdatasetbasis in theCMCor throughnet‐workaccesscontrol,e.g.whenaccessingtheserverviaFTP,sshorotherweb‐protocols.

Based on user profiles and user groups,WADIwill give dedicated access and activitypermissionsonthesystemtoauser.AccesstodatawillbemanagedbytheDataMan‐agementExecutiveGroupincooperationwiththosehavingdatamanagementresponsi‐bilitiesintheresearchteams(mightbemembersoftheDataManagementCouncil),theprojectcoordinatorsandtheExecutiveDirector.Auserandgroupconceptwillbeelabo‐ratedandwillconsiderthefollowingaspects:

Roleoftheuserwithrespecttodataacquisition:Dataprovider/producer/con‐sumer/anddatamanagementrelatedroleintheresearchteam.

Typeofindividualrelationshiptotheproject:memberofprojectstaff,memberofpartnerinstitution,employmentconditions(funding,position).

Scientificdisciplineandteam‐membershipinworkinggroups.

6 DepositandLong‐TermPreservation

Along‐termstrategyformaintaining,administeringandarchivingthedataistobeen‐suredbythelong‐termstorageofdataattheCompetenceCenter.

6.1 Long‐TermSpecifics

DataaretobekeptbeyondthelifetimeoftheprojectforaslongasneededbytheusersintheCompetenceCenter.HowdatawillbemanagedbeyondtheCCestablishingproject(WASCAL)willdependuponhowthecenterwillcontinue thereafter.Assumingacon‐tinuationasaScienceServiceCenter,dataanddataproductswillplayacrucialrolefur‐theron.Lifecyclesofdatawillbehandledbyfollowingthedemandsexpressedbyscien‐tists and stakeholders at the end ofWASCAL. Plans for archiving and of preservationstrategies (by seeingarchiveddataasnot immediatelyaccessibledata),willbedevel‐opedbytheDataManagementGroupattheCompetenceCenterintime.

Managingdatasets including sensitivedataover the longer termwillbeaccomplishedtakingintoconsiderationnationallaws.SensitivedatawilleitherbeanonymizedortheprotectionofdataprivacywillbeassuredbytheCompetenceCenterdatamanagersbycontracts.

Datatransformationbyreformattingtoopenformatsorbytransformationtoanappro‐priategeographicreferencesystemmaybeperformed,asandifnecessary.

6.2 MetadataandDocumentationforLong‐TermPreservation

26

DatasetswillbelinkedbyinternalentrieswiththeUIDsinthemetadatabase.Inaddi‐tion,xmlfiles(ISO19139standard)aretobedownloadedautomaticallytogetherwiththedatafileswhenauseraccessesthedatainWADI.Thiswillbedonebythedatapro‐viders/creatorsbyeditingmetadataonlineontheWASCALdataportal,orbyusingap‐propriatetoolsextractingmetainformationfromdatastoredonlocaldrivesinaformat(19139xmlschema),whichcanbeuploadedtothecentralmetadatacatalogue.

Publishedmaterialsand/oroutcomes,preferentiallylinkedtotheuseddata,willbein‐cluded in thedata infrastructures.ThiswillbedonebypersistentURLs (composedofserverhostnameandmetadataUID)totherelatedentry in links inthemetadatacata‐logue,respectivelybyDigitalObjectIdentifiers(e.g.fromtheDOI‐System16)asfarasisintroducedinWASCAL.

6.3 Longer‐TermStewardship

Responsibilityovertimefordecisionsabout thedataoncetheoriginalpersonnelhavegone iswith theDataManagementExecutiveGroup togetherwith theheadquarter oftheCompetenceCenter,andbasedupondatapolicystatementsagreedwiththerespec‐tiveinstitutionalbodiesofWASCALandtheCompetenceCenter.

7 Resourcing

7.1 OrganizationalRolesandResponsibilitiesforDataManagement

During theWASCALproject funding timeperiod, coordinationofdatamanagement atdifferentlevelsofresponsibilitywillbeestablishedinthefollowingmanner:

a) DataManagementExecutiveGroup(DMG):TheDMGconsistsofthedatamanag‐ers responsible for conceptualization and implementation of the datamanage‐mentinfrastructureinWASCAL.Thisgroupisresponsiblefortheoverallcoordi‐nation,tobuildupandoperatetheWASCALdatamanagementinfrastructureandtoorganizeandcarryoutusertrainings.MembersofthegrouparelistedinAn‐nexA1.1.

b) DataManagementCouncil(DMC):TheDMCconsistsoftheexecutivedirectorre‐spectivelyhisdeputy,onerepresentativeperResearchCluster,oneleadingrep‐resentative of the Competence Center, representatives of the DMG and repre‐sentativesoftheWASCALpartnercountries.IntheDMCgeneralstrategicissueswithregardtodatamanagementwillbediscussedandpendingdecisionsofma‐jorrelevancewillbetaken,forexamplewithregardtodatarightsmanagement.Thegroupwillmeetorcommunicateondemand.MemberofthegrouparelistedinAnnexA1.2.

c) ResearchWorkingGroup(RWG):TheRWGwillworktogetherwiththeDMGandconsists of one representative per each Work Package, research group in theCompetence Center andGraduate Research Program and/or representatives ofthe main partner institutions contributing data to WASCAL. Within thegroups/institutions they represent they have to organize the controlling, pro‐

16http://www.doi.org/(accessed12.09.2013)

27

cessing, preparation for sharing (e.g. by transformations), qualitymanagement,andprovidingofdataandmetadatatoWADIasfarasdemandedbytheWASCALdata management policies. This could be done e.g. by the designation of datamanagement responsibles (datamanagers) in the respective institution orWP.TheDMGwillworkcloselytogetherwiththesedatamanagersbysupportingandtrainingthemindatamanagementtaskswithintheirresponsibilitye.g.thesub‐missionofmetadataanddatatothecentraldatabases,andwillorganizefurtherprocessingasfarasitfallsundertheirresponsibility.Furtherprocessing,asideofdatasharing,couldbethecreationofportrayalandothervisualizationservices.The groupwillmeet and communicate on demand.Members of the group arelistedinAnnexA1.2.

Figure2:OrganizationalstructureintheWASCALDataManagement

7.2 DataManagementActivitiesFunding

Fundingofdatamanagementwithintheprojectlifetimeispartoftheproposedprojectbudget.Longertermfundingaftertheproject’sendisnotyetspecified.

8 AdherenceandReview

This data management plan will be signed by theWASCAL project management andeventuallybythestaffmembersof theWASCALcompetencecenter.Thedegreeofad‐herencetotheplanwillbeobservedinthedailyworkoftheDataManagersandcheckedbytheDataManagementExecutiveGroup.

Currently,therearenodetailedplansforreviewingthisdatamanagementplan.

28

9 StatementofAgreement

29

Annex1 Contactdetailsofnominateddatamanagers/namedin‐dividuals

A1.1 DataManagementExecutiveGroup

Dr.RalfKunkel(headofgroup)SeniorresearcheranddatamanagementcoordinatoratResearchCenterJülich52425Jülich,GermanyPhone: ++49‐2461‐613262E‐Mail: r.kunkel@fz‐juelich.de

AntonioRogmannSeniorresearcheranddatamanageratCenterforDevelopmentResearch,Uni‐versityofBonnWalter‐Flex‐Str.3,53113Bonn,GermanyPhone: ++49‐228‐734904E‐Mail: arogmann@uni‐bonn.de

Dr.ChristineFürstSeniorresearcheratCenterforDevelopmentResearch,UniversityofBonnWalter‐Flex‐Str.3,53113Bonn,GermanyPhone: ++49‐228‐734922E‐Mail: cfuerst@uni‐bonn.de

JürgenSorgDatamanagerandcomputerscientistatResearchCenterJülich52425Jülich,GermanyPhone: ++49‐2461‐615535E‐Mail: j.sorg@fz‐juelich.de

HuapingWangDatamanagerandcomputerscientistatResearchCenterJülich52425Jülich,GermanyPhone: ++49‐2461‐618055E‐Mail: h.wang@fz‐juelich.de

N.N.,DataManageratWASCALCompetenceCenterAddress: ?Phone: ?E‐Mail: ?

N.N.,SystemAdministratorattheCompetenceCenterAddress: ?Phone: ?E‐Mail: ?

30

A1.2 DataManagementCouncil

A1.3 ResearchWorkingGroup

A1.4 InstitutionalDataManager

31

Annex2 ListofcontributingorganizationstoWASCAL

32

Annex3 Glossary

CC WASCAL Competence Center: Service center for the WASCALpartnercountries,buildingonthenationalresearchcommunitiesoftheWestAfricancountriesparticipatinginWASCAL.Thecenterconnectsregionalpartners indata‐collectionnetworks (observa‐tionnetworks),andofferstheinfrastructureandexpertiseneces‐saryforanalyzingtheimpactsofclimatechangeandfordevelop‐ingstrategiesandpoliciestocopewiththem.

CMC CentralMetadata Catalogue, which stores allmetadatamanagedbyWADI.

CMS ContentManagementSystem:Computerprogramthatallowspub‐lishing, editing and modifying content as well as maintenancefrom a central interface. Such systems of content managementprovideprocedures tomanageworkflow ina collaborativeenvi‐ronment.

CRP WASCAL Core Research Program: Joint research program onadaptedlanduseandmanagementunderchangingclimaticcondi‐tions, which brings together a German and an equivalentWest‐Africanresearchconsortium.

CSW CatalogServicefortheWeb(sometimesseenasCatalogService‐Web):StandardforexposingacatalogueofgeospatialrecordsontheInternet(overHTTP).CSWisonepart(or"profile")oftheOGCCatalog Service, which defines common interfaces to discover,browse, and querymetadata about data, services, and other po‐tentialresources.

DMI DataManagementInfrastructure

DMP DataManagementPlan:Formaldocument thatoutlineshowyouwillhandleprojectdataduringresearchtimeandaftertheprojectiscompleted.Thegoalofadatamanagementplan is toconsiderthemanyaspectsofdatamanagement,metadatageneration,datapreservation, and analysis before theproject begins; this ensurethat data are well‐managed in the present, and prepared forpreservationinthefuture.

GIS Geographic Information System: System designed to capture,store,manipulate,analyze,manage,andpresentall typesofgeo‐graphicaldata.Inthesimplestterms,GISisthemergingofcartog‐raphy,statisticalanalysis,anddatabasetechnology.

GRP WASCAL Graduate Research Program: Program to support andfacilitateacademiceducationamongstWestAfricanuniversitiesinassociation with German counterpart institutions. The activitiesfocusonthetrainingofdoctoralstudents.

OGC The Open Geospatial Consortium (OGC), an international volun‐taryconsensusstandardsorganization,originatedin1994.IntheOGC,morethan400commercial,governmental,nonprofitandre‐

33

search organizationsworldwide collaborate in a consensus pro‐cess encouraging development and implementation of openstandardsforgeospatialcontentandservices,GISdataprocessinganddatasharing.

SDI Spatial Data Infrastructure: Data infrastructure implementing aframeworkofgeographicdata,metadata,usersandtoolsthatareinteractivelyconnectedinordertousespatialdatainanefficientandflexibleway.

SWE OGC'sSensorWebEnablementframeworkdefinesasuiteofwebserviceinterfacesandcommunicationprotocolsabstractingfromtheheterogeneityofsensor(network)communication.

UID UniqueIdentifier:anyidentifierwhichisguaranteedtobeuniqueamongallidentifiersusedforthoseobjectsandforaspecificpur‐pose.

WADI WASCALData Infrastructure: Spatial data infrastructure createdtomanagethedatafromtheWASCALproject

WASCAL West African Science Service Center on Climate Change andAdaptedLandUse

WCS TheOpenGeospatialConsortiumWebCoverageServiceInterfaceStandarddefinesWeb‐basedretrievalofcoverage

WFS Web Feature Service: Interface standard of the Open GeospatialConsortium,whichprovidesaninterfaceallowingrequestsforge‐ographical features across the web using platform‐independentcalls.

WMS Web Map Service: Standard protocol for serving georeferencedmapimagesovertheInternetthataregeneratedbyamapserverusingdata fromaGISdatabase.ThespecificationwasdevelopedandfirstpublishedbytheOpenGeospatialConsortiumin1999.

34

Annex4 Datamatrix

ExcelFile:WASCAL_CRP‐OUT‐IN‐Data‐Matrix.xlsx