CESSDA Strengthening and Widening · D2.2 – v. 1.0 Page 4 of 30 EXECUTIVE SUMMARY Over the years,...

Project funded by the EU Horizon 2020 Research and Innovation Programme under the agreement No.674939

ResearchandInnovationAction

CESSDAStrengtheningandWideningProjectNumber:674939 StartDateofProject:01/08/2015 Duration:24months

Deliverable2.2

Knowledge-SharingPlatformContentand

ManagementPolicy

DisseminationLevel PU

DueDateofDeliverable 31/10/16

ActualSubmissionDate 31/10/16

WorkPackage WP2DisseminationandCommunication

Task 2.1

Type Report

ApprovalStatusbyEC 31 January 2017

Version V1.1

NumberofPages p. 1–p.30

Abstract: Building on the results of the Virtual Stakeholder’s Forum (D2.1), this report details how thecontent and functionality of the CESSDA Knowledge-Sharing Platformwill be developed, and describeshowitwillberun,managedandmaintainedpost-project.

Theinformationinthisdocumentreflectsonlytheauthor’sviewsandtheEuropeanCommunityisnotliableforanyusethatmaybemadeoftheinformationcontainedtherein.Theinformationinthisdocumentisprovided“asis”withoutguaranteeorwarrantyofanykind,expressorimplied,includingbutnotlimitedtothefitnessoftheinformationforaparticularpurpose.Theuserthereofusestheinformationathis/hersoleriskandliability.

D2.2 – v. 1.0

Page2of30

History

Version Date Reason Revisedby

0.0 08/08/2016Document created, table of contents, first textinput

JonasRecker

0.1 Until11/10/2016Furthertextinput,commentsonanddiscussionofcontent

JonasReckerBirgerJerlehagIrisAlfredssonIrenaVipavcBrvarSonjaBezjak

1.0 20/10/2016 Finalizetext JonasRecker

1.1 27/10/2016Incorporate feedback from Project Manager andCESSDATechnicalOfficer

JonasRecker

1.1 28/10/2016Deliverable revised by Delivery Committee ChairandProjectCoordinator

Jindrich Krejci, IvanaIlijasicVersic

AuthorList

Organisation Name ContactInformation

ADP SonjaBezjak [email protected]

ADP IrenaVipavcBrvar [email protected]

CESSDAMO Jean-BaptisteMilon [email protected]

GESIS JonasRecker [email protected]

SND IrisAlfredsson [email protected]

SND BirgerJerlehag [email protected]

D2.2 – v. 1.0

Page3of30

TimeSchedulebeforeDelivery

NextAction Deadline Careof

Determineelements and scopeofplatformcontentandmanagementpolicy

31/06/2016 ADP,GESIS,SND

Analyze and describe functional requirements,describeoutcomeofsoftwareselectionprocess

15/09/2016 GESIS

Developanddescribelicensingschema 15/09/2016 SND

Developanddescribecollectionandoperationpolicy 15/09/2016 ADP

Developanddescribemetadataschema 15/09/2016 ADP

Develop and describe future content developmentandmanagementofplatform

15/09/2016 GESIS

Finalizereport 15/10/2016 ADP,GESIS,SND

D2.2 – v. 1.0

Page4of30

EXECUTIVESUMMARYOver theyears,CESSDApartnershavecreateda significantbodyofknowledgeonabroad rangeof topics.Muchof this knowledge is captured in digital resources such as papers, presentations, reports, guidelines,and training materials. However, these resources are scattered across the different service providers,sometimesavailablefromthewebpage,butinothercasesmerelystoredoninternalservers.Whatismore,no systematic and structured description of these resources exists. Task 2.1 of the CESSDA SaWproject isdedicated to remedying this situation by creating a virtual knowledge-sharing platform (KSP) as a centralpointofaccessforthebodyofknowledgecreatedbyCESSDApartners.

D2.2deliversthePlatformContentandManagementPolicy,detailinghowcontentandfunctionalitywillbedevelopedduringtheprojectandspecifyinghowtheKnowledge-SharingPlatform(KSP)willberun,managedandmaintainedpost-project.ItbuildsonD2.1“Knowledge-SharingPlatformForumReport”,whichcontainstheresultsofasurveyamongprospectiveusersoftheplatformandgivessomeinsightintotheirexpectationsrelatingtothecontentandfunctionalityoftheplatform.

Developmentofplatformfunctionality

Thefunctionalityoftheplatformwillbeshapedbythesoftware,aswellasbytheimplementedpoliciesandstandards for thedescriptionandorganizationthecontent.Toensure theusabilityanduser friendlinessoftheplatform,thesoftwareonwhichtheplatformwillbebuilt (DSpace)wasselectedbasedonafunctionalrequirements analysis taking into account the different stakeholder groups who will be working with theplatform(users,depositors,administrators).Furthermore,theOSSWatchcriteria1fortheselectionofopensourcessoftwarewereemployed.

Thediscoverabilityofcontentandoveralluser-friendlinessoftheplatformforthoselookingforresourcesarealso determined by how content is organized and described with (structured and un- or semi-structured)metadata.Tosupportdiscoverability,thefollowingwasdeveloped:ametadataschemadrawingonrelevantstandardsforopenaccessrepositories(e.g.DublinCoreLibraryApplicationProfile,DataCite);amodelfortheorganizationofcontentintheplatformmakinguseofthe“community”and“collection”structureofDSpace.

Developmentofplatformcontent

Tosupportboththedepositorsandthefutureeditorsoftheplatform,aCollectionandPlatformOperationPolicywasdeveloped.Itdescribesthescopeoftheplatform,i.e.whichcontentwillbecollected,anddefinesselectioncriteriatosupportthereviewandpublicationprocess.

AnimportantaspecttoconsiderwhenfillingtheplatformwithcontentareIntellectualPropertyRights.Thus,whenacceptingresourcesforpublication,CESSDAhastoassurethatthedepositorshavetherighttopublishtheresourceandthatnorightsofthirdpartiesareinfringed.Forthispurpose,adepositcontractwascreatedthat depositors have to accept when submitting resources. This at the same time allows depositors todetermineunderwhichlicensetheywanttosharetheirresources.

Maintainingtheplatformpost-project

OneoftheexpressobjectivesofestablishingtheKnowledge-SharingPlatformisthesystematicarchivingofCESSDA resources. Thus, the platform must become a long-term effort of CESSDA AS. Accordingly, itscontinued existence and development must be guaranteed, both on a technical and a content level. Toachieve this, the report addresses the following aspects: possibilities for platform hosting, organization ofplatformadministration,submissionmanagement,andcollectiondevelopmentwiththehelpofaneditorialcommittee.

1Seehttp://oss-watch.ac.uk/apps/openness/.

D2.2 – v. 1.0

Page5of30

AbbreviationsandAcronyms

ADP SlovenianSocialScienceDataArchives

BSD BerkeleySoftwareDistribution

CC CreativeCommons

CCBY CreativeCommonsAttribution

CCBYNC CreativeCommonsAttribution-Noncommercial

CCBYNCND CreativeCommonsAttribution-NoDerivatives

CCBYNCSA CreativeCommonsAttribution-Noncommercial-ShareAlike

CESSDAAS ConsortiumofEuropeanSocialScienceDataArchives

CESSDAMO CESSDAMainOffice

CESSDASaW CESSDAStrengtheningandWidening

da|ra Registrationagencyforsocialandeconomicdata

DOI DigitalObjectIdentifier

GESIS GESIS-LeibnizInstitutefortheSocialSciences

KSP Knowledge-SharingPlatform

OAI-ORE OpenArchivesInitiativeObjectReuseandExchange

OAI-PMH OpenArchivesInitiativeProtocolforMetadataHarvesting

OpenDOAR DirectoryofOpenAccessRepositories

OPUS OnlinePublikationsverbundderUniversitätStuttgart

PM PersonMonth

RSP RegisteredDSpaceServiceProviders

SND SwedishNationalDataService

SP ServiceProvider

SSOAR SocialScienceOpenAccessRepository

D2.2 – v. 1.0

Page6of30

TableofContents

ExecutiveSummary

Introduction

DevelopmentofPlatformFunctionality

Requirements

Software

DSpaceDataModelandContentOrganization

DSpacePublicationWorkflowandRoles

MetadataSchema

DOIRegistration

Implementationprocess(TechnicalTasks)

DevelopmentofPlatformContent

Requirements

CollectionPolicyandselectioncriteria

ContentDevelopment

LicensingandDepositAgreement

MaintainingthePlatformPost-Project

PlatformHosting

PlatformAdministration

SubmissionManagementandCollectionDevelopment

Appendix1:UserStoriesandFunctionalRequirements

Appendix2:FunctionalrequirementsandCorrespondingDSpace5.xfunctions

Appendix3:CollectionandOperationPolicy(DRAFT)

Appendix 4: Deposit and licensing agreement for resources uploaded to the CESSDA Knowledge-SharingPlatform(DRAFT)

D2.2 – v. 1.0

Page7of30

1. INTRODUCTIOND2.2deliversthePlatformContentandManagementPolicy,detailinghowcontentandfunctionalitywillbedevelopedduringtheprojectandspecifyinghowtheKnowledge-SharingPlatform(KSP)willberun,managedandmaintainedpost-project.ItbuildsonD2.1“Knowledge-SharingPlatformForumReport”,whichcontainstheresultsofasurveyamongprospectiveusersoftheplatformandgivessomeinsightintotheirexpectationsrelatingtothecontentandfunctionalityoftheplatform.

2. DEVELOPMENTOFPLATFORMFUNCTIONALITYThefunctionality-andusability-ofthecompletedplatformwillmainlybedependentontwofactors:firstly,thesoftwareand,secondly,theimplementedpoliciesandstandardsforthedescriptionandorganizationofthe content. Thus the software defines the general framework for the functionality of the platform.Importantaspectstoconsideraresupportofstandards;outoftheboxfunctionsfordeposit,management,and discovery; openness; and customizability. However, the discoverability of content and overall user-friendliness of the platform for those looking for resources are impacted by the way in which content isorganized and described with (structured and un- or semi-structured) metadata. Thus from a userperspective,whethertheplatformisperceivedaswell-functioningandeasy-to-usedoesnotmerelydependontechnologicalfeaturesofthesoftwarebutverystronglyontheintellectualorganizationofcontent.

2.1 REQUIREMENTSTo ensure that the Knowledge-Sharing Platform is designed to be as user-friendly as possible, it wasimportanttolearnmoreabouttheneedsanddemandsoffutureplatformusers.ForD2.1wedeterminedthestakeholdergroupsandroleslistedinTable1.

Table1:Stakeholdergroups

Group Stakeholders Envisioneduse

I · CESSDAMainOffice· KSPEditorialCommittee· CESSDAServiceProviders· CESSDAObserversandaspiringService

Providers

Extensive/heavyuseoftheplatformindifferentroles

II · Other(socialscience)dataarchives LighterandmoreselectiveuseoftheplatformthanGroupI

III · Socialscienceeducators· Socialscienceresearchers· Academicsupportstaff(administration,

librarystaff,etc.)· CESSDAMembers(i.e.ministries)· PolicymakersonnationalandEuropean

level

Lightuseofonlyselectedareas/materialsonspecifictopics

Thesestakeholderswillusetheplatformindifferentroles.Wedistinguish:

D2.2 – v. 1.0

Page8of30

● Depositors:submitresourcestotheplatform.● Users:searchforanddownloadcontentfromtheplatform.● Editors:managethecontent-sideoftheplatform.● Administrators:managethetechnology-sideoftheplatform.

The most common role across all stakeholders will be that of user. A considerably smaller group ofstakeholderswillalsodeposittotheplatform,andtheroleofmanagingcontentandthetechnologicalsideoftheplatformwillbeperformedbyayetsmallernumberofindividuals.Todeterminetherequirementsofthe“Users”,theD2.1onlinesurveywascarriedout(seeD2.1Report).Tomake it easier to translate these results into actual functional requirements for D2.2, user stories werecreated.Userstoriesareatoolfromagilesoftwaredevelopment,consistingof“short,simpledescriptionsofafeaturetoldfromtheperspectiveofthepersonwhodesiresthenewcapability,usuallyauserorcustomerof the system” (https://www.mountaingoatsoftware.com/agile/user-stories). The stories were created tobetter capture and illustrate the desired functionality and to facilitate the communication with theprogrammers.To identify needs and demands of the other stakeholder groups, further user stories were created andreviewed by the current Editorial Committee, whosemembers will use the KSP in the roles of depositor,editor, and administrator during the project. User stories were then matched with softwarefeatures/functionsrequiredtomeetthedemandsexpressedinthem(seeAppendix1).

2.2 SOFTWAREThedecisionwasmadetoimplementtheKSPusingDSpace,anopensourcerepositorysoftwarethatiswidelyused for institutional repositories (http://www.dspace.org). Other open source software solutions on themarket are, for example, EPrints (http://www.eprints.org/uk/), Fedora (http://fedorarepository.org), Hydra(https://projecthydra.org), or OPUS (https://en.wikipedia.org/wiki/OPUS_(software)). The decision forDSpacewasmadebasedonfunctional/technologicalandorganizationalfactors(seebelow).

TheDSpacesoftwarewasdevelopedbytheMITLibrariesandHewlettPackard,withtheinitialreleasedatingfrom 2002. Today it is stewarded by DuraSpace, a not-for-profit organization formed in 2009 in amergerbetween theDSpace FoundationandFedoraCommons (seehttp://www.duraspace.org/history). The latestversion of the software is 5.5, released in March 2016.2 According to the Directory of Open AccessRepositories (OpenDOAR, http://www.opendoar.org) DSpace is currently the most widely used repositorysoftwarewithover1,400currentinstallations(seeOpenDOARinformationchart).

DSpacemeets the functional requirements thatwere identified inD2.1andexpandedwith thehelpof theuser stories developed for stakeholder groups not covered in the online survey. Among the features ofDSpacethatleadtoourdecisiontouseitfortheimplementationoftheKSParethecustomizablemetadatafields, flexible licensemanagement, freeworkflowdefinition, user-friendly implementation ofmulti-lingualuser interfaces, full-text and faceted search/browsing (see Appendix 2 for detailed matching betweenrequirementsandsoftwarefeatures)

Inadditiontolookingatfunctionalrequirements,OSSWatchsuggestsemployingthefollowingcriteriaintheprocessofselectinganopensourcesoftware(seeTable2).

Table2:OpenSourceSoftwareselectioncriteria

2 Full software documentation for DSpace 5.x releases is available underhttps://wiki.duraspace.org/display/DSDOC5x/DSpace+5.x+Documentation

D2.2 – v. 1.0

Page9of30

Criterion3 (How)doesDSpacemeetthecriterion?

Reputation:Doesthesoftwarehaveagoodreputationforperformanceandreliability?

GESIS’sexperiencefromimplementingandmaintainingSSOAR,datorium,andLeibnizOpenisthatDSpaceisbothreliableandhasexcellentperformance.ThisisspecificallyduetoitsuseofhighlyperformantframeworkssuchasSOLRandCocoon.Inaddition,DSpaceischaracterizedbyaveryhighflexibility,e.g.regardingtheuserinterface.

Ongoingeffort:Isthereclearevidenceofongoingefforttodeveloptheopensourcesoftwareyouareconsidering?Hastherebeenrecentworktofixbugsandmeetuserneeds?

Thesoftwarehascontinuallybeendevelopedfurthersinceitsinitialreleasein2002.Ithasbigandactiveuser/developercommunitywithwell-definedcommunicationchannelsallowingforthesubmissionofbugs,thecontributionofcode,ortherequestoffeatures.4

Standardsandinteroperability:Choosesoftwarewhichimplementsopenstandards.

DSpacesupportsrelevantstandards,includingOAI-PMH,OAI-ORE,SWORD,WebDAV,OpenSearch,OpenURL,RSS,ATOM(http://www.dspace.org/why-use).

Support(Community):Doestheprojecthaveanactivesupportcommunityreadytoansweryourquestionsconcerningdeployment?

DSpacehasanefficientcommunitysupportinfrastructure,includinganumberofveryactivemailinglists(http://www.dspace.org/community).

Support(Commercial):Thirdpartycommercialsupportisavailablefromadiversityofcompanies

DSpaceworkswith“RegisteredDSpaceServiceProviders(RSP)”.Thesearecompanieswho“havemadeaninvestmentintheDSpacetechnologyandacommitmenttoworkcooperativelywithDuraSpaceorganizationtobestservethecommunityofusers”(http://www.dspace.org/service-providers).

Version:Whenwasthelaststableversionofthesoftwarereleased?

Version6.0,releasedinOctober2016

Documentation:[...]Youshouldbeabletotraceaclearhistoryofbugfixes,featurechanges,etc.

ComprehensivedocumentationisavailableontheDuraSpraceWiki:https://wiki.duraspace.org/display/DSDOC6x/DSpace+6.x+Documentation.JIRAisusedforbugtracking:https://jira.duraspace.org/projects/DS/issues/DS-2325?filter=allopenissues

Skillset:Considertheskillsetofyourselfandyourcolleagues.Doyouhavetheappropriateskillstodeployandmaintainthissoftware?

ThetechnicalimplementationoftheKSPwillbecarriedoutbytheGESISdepartment“KnowledgeTechnologiesfortheSocialSciences”whichhasconsiderableexperiencewithDSpacerepositories.Currently,threeDSpacerepositoriesaremanagedatGESIS:SSOAR(http://www.ssoar.info),datorium(https://datorium.gesis.org/xmlui/),andLeibnizOpen(http://www.leibnizopen.de/1/home/).

Licence DSpaceisdistributedunderaBSDlicense(http://www.dspace.org/license).

Another factor influencing the decision for DSpace is the fact that GESIS, responsible for the technicalimplementation of the platform, has long-standing expertise in implementing and maintaining DSpaceplatforms,bothfortextualresourcesandforresearchdata.Thisalsomeansthatroutinesandsolutionsfor

3Allcriteriaandexplanationsquotedfromhttp://oss-watch.ac.uk/resources/tips.4Seehttps://wiki.duraspace.org/display/DSPACE/How+to+Contribute+to+DSpace.

D2.2 – v. 1.0

Page10of30

required workflows and functions already exist (e.g. automatic DOI registration with da|ra, suggestedcitation) and can therefore be re-used for the CESSDA Knowledge-Sharing Platform. This makes theimplementationprocessmoreefficient.

2.3 DSPACEDATAMODELANDCONTENTORGANIZATIONTheDSpacedatamodeldistinguishesthefollowingtypesofelements,organizedinahierarchicalfashion(seeFigure1).Onthehighest level, therearecommunities,whichcontainoneorseveralcollections.Collectionsarecomposedofitems,whichcanappearinmorethanonecollection.Eachitemiscomposedofbitstreamswhichmaybegrouped intobundles if theyareclosely related (e.g.allbitstreamsthatmakeupawebpagewithtextandimageswouldbeconsideredabundle).Eachbitstreamisassociatedwithabitstreamformat.

Figure1DSpacedatamodel

(Source: DSpace Documentation 5.x,https://wiki.duraspace.org/display/DSDOC5x/Functional+Overview#FunctionalOverview-DataModel)

D2.2 – v. 1.0

Page11of30

Whilethewaythatcontentorganizedintocommunitiesandcollectionsdoesnothaveagreatimpactonthediscoveryofcontent(whichisveryflexiblyhandledbytheDSpacediscoverysystembasedonthemetadata),ithassomerepercussionsforadministeringtheplatformandforusescenariosfromtheorganizationalratherthanindividualuserperspective.Thusthefollowingpointsneedtobeconsidered:

1) If the repository ingests different resource types that need to be described with different metadata,collectionsshouldreflectresourcetypes.Eachresourcetypecollectioncanhavea“tailored”setofmetadatafieldsassociatedwithit.Amongotherthingsthiscanmakeiteasierfordepositorstofilloutthesubmissionform(e.g.becausetheydonothavetoscrollthroughlonglistsofirrelevantmetadatafields),anditcanhelpto increase metadata quality (e.g. because there is more flexibility in designating metadata fields asmandatoryoroptionalbasedonresourcetype).AsweexpectdifferenttypesofresourcestobesubmittedtotheKSP-rangingfromreportsandpresentationstoaudiovisualandwebresources-resourcetypesshouldbereflectedonthecollectionlevel.

2)AsecondimportantquestionthatneedstobeconsideredistherepresentationofServiceProvidersinthestructure of the KSP. The organization of data in DSpace was originally designed to reflect the typicalstructure of universities divided into colleges, departments, chairs, etc. This can be used to represent thestructureofCESSDA in thecontentorganizationhierarchyaswell.Thus,eachServiceProviderandCESSDAMainOfficecanberepresentedasacommunity.Thisapproachhastwoadvantagesandonedrawback:

● AllpublicationsofoneSPcanbeaccessedthroughasinglepage,whichcanforexamplebeequippedwithalogoandcouldbeusedbytheSPtoshowcaseitspublications.

● Intheunlikelyeventthatforwhateverreasonaneedarisestoremove(publicationsby)oneSPfromtheportalentirely,thecommunitystructureallowsforthiswithoutmajoreffort.5

● A drawback of this approach is the additional effort that needs to be made in setting up thecommunities and collections. However, as the creation of collections and communities is notcomplicatedinDSpace,andseeingasitismostlyaone-timeeffortduringtheimplementationphase,thisisnotasignificantproblem.6

InadditiontoServiceProvidercommunitypagesitissuggestedtocreateacommunityforcuratedcollectionson different topics, which include lists of “hand-picked” resources on a certain subject, as well as acommunity forprojects,whichcancontaincollectionsofoutputsofbiggercollaborativeprojects (e.g.SaWitself).Takingthisintoaccount,thecommunity-collectionstructurewouldlookasshowninfigure2.

5ItshouldbenotedthatbyassigningaDOItotheresourcesintheKSP,weguaranteethatatleastthelandingpageoftheresourcewillremainaccessible.6 In the event that access to communities and collections needs to be controlled in amore differentiatedfashion,thiswillmakeitnecessarytocreateanaccesscontrolmodel(e.g.RBAC).ThiscanbehandledwithDSpacewithoutproblems,however.

D2.2 – v. 1.0

Page12of30

Figure2:CESSDAKSPcontentorganization

2.4 DSPACEPUBLICATIONWORKFLOWANDROLESTheDSpacepublicationworkflowcanhaveuptothreestepsbeforeitemsarepublishedinacollection(seeFigure3).Differentstepscanbeassignedtodifferentgroupsofpersons.FortheCESSDAKSPweproposeaprocedureconsistingoftwosteps:

1)Afteradepositorsubmitsanitem,it isreviewedbyaneditor,whocanacceptorrejectanitemandwhocanalsoeditmetadataifrequired.2)Whenthisreviewiscompleted,theitemisreviewedandthenpublishedbyanadministrator.

D2.2 – v. 1.0

Page13of30

Figure3:SubmissionworkflowinDSpace

Source:https://wiki.duraspace.org/display/DSDOC5x/Functional+Overview#FunctionalOverview-WorkflowSteps

In addition,DSpaceallows theassignmentofdifferent roles to thoseusing the system. ThedistributionofrolesandresponsibilitiesfortheCESSDAKSPisdetailedinTable3.

Table3:Rolesandassociatedrights

Group Rights

Anonymous ● Readallresourcesand(bibliographic)metadata

Registeredusers7 ● Readallresourcesand(bibliographic)metadata

Depositors ● Readallresourcesand(bibliographic)metadata● Submitresourcestocollections

Editors ● Readallresourcesand(bibliographic)metadata● Submitresourcestocollections● Edititems(metadata)incollections(incl.DOIassignment)● Withdrawitemsfromcollections● Mapitemsintoacollection

Administrators ● Readallresourcesand(bibliographic)metadata● Submitresourcestocollections● Edititems(metadata)incollections(incl.DOIassignment)● Withdrawitemsfromcollections● Mapitemsintoacollection● Assignregisteredpersonstogroups● Assignrightstogroups● Createcommunities● Createcollections● Publishresources

7Registereduserscancreateemailalertsforcollections,butneednothavethesamerightsasdepositors.

D2.2 – v. 1.0

Page14of30

2.5 METADATASCHEMAThemetadatausedtodescribetheresourcescollected in theKnowledge-sharingPlatform(KSP)arecrucialfortheadministration,discovery,andcitabilityofresources.Themoredetailedinformationisrecordedaboutresourcespublishedthroughtheplatform, theeasier these tasksbecome.However,abalanceneeds tobestruckbetweenthedesiredamountofmetadataandthetimethatdepositorsarerequiredtospendonthesubmissionofresources.Thisbalancecanbeachievedbymakingonlythosemetadatafieldsarequirementthatareabsolutelynecessarytofulfillthepurposesmentionedabove,butgivingdepositorstheopportunitytocontributefurthermetadataifdesired.

TodevelopthemetadataschemafortheCESSDAKSP,anumberofotherschemaswasconsultedandotherrepositorieswereconsulted.Theschemasandrepositoriesconsultedincluded

● da|raMetadataSchemaversion3.1(http://www.da-ra.de/en/technical-information/doi-registration/)

● DataCiteMetadataSchemaversion4.0(http://schema.datacite.org/)● DublinCoreLibraryApplicationProfile(http://dublincore.org/documents/library-application-

profile/)● OpenAire(https://guidelines.openaire.eu/en/latest/literature/application_profile.html)● OpenScienceportalSlovenia(http://www.openscience.si/default.aspx)● NordicHealthData(https://github.com/NordicHealthData)● LeibnizOpen(http://www.leibnizopen.de/1/home/)● SocialScienceOpenAccessRepository(SSOAR)(http://www.ssoar.info)● EconStor(https://www.econstor.eu/dspace/)

Inaddition,therequirementsofthelinkedCESSDA-SaWTask5.2weretakenintoaccount.

Onthisbasis,ametadataschemawasdevelopedwhichiscurrentlyintheprocessofbeingfinalized.

2.6 DOIREGISTRATIONThe SaWdescriptionofwork explicitly requires that resources published through theKSP receive aDigitalObject Identifier (DOI), registered through da|ra (http://www.da-ra.de). DOIs enable the unambiguousidentificationandeasycitationofresources.Theycanbeassignedunderthecondition“thatDigitalobjectsreferencedviaan identifiermustbepermanentlyandconstantlyavailable,without interruption,under theregistered address” (da|ra Policy 5.4.18). Before the CESSDA KSP can begin registering DOIswith da|ra, aServiceLevelAgreement9hastobesigned.

8http://www.da-ra.de/en/about-us/da-ra-policy/policy/9http://www.da-ra.de/en/about-us/da-ra-policy/service-level-agreement/

D2.2 – v. 1.0

Page15of30

2.7 IMPLEMENTATIONPROCESS(TECHNICALTASKS)Table4:PlatformImplementationProcess

From To Description Partner(s)

M11 M15 ● Descriptionoffunctionalrequirements● Definitionofdatamodel● Definitionofmetadataschema● Definitionoflicensingscheme● Setupda|racooperationforDOIregistration

ADP,SND,GESIS,CESSDAAS

M16 M18 ● Programming/implementationofplatform GESIS

M19 M21 ● Beta-testing All

M21 M21 ● LaunchofplatformontheCESSDAwebpage GESIS,CESSDAAS

3. DEVELOPMENTOFPLATFORMCONTENT

3.1 REQUIREMENTSAs detailed in D2.1 (see chapter 3.3), the survey carried out among future users and depositors of theKnowledge-sharing Platform suggests an interest in a broad range of resources types and topics. A stronginterest exists in resources that can be used for training, “Guidelines and manuals” in particular. Otherdesiredresources includedcasestudiesandbestpractices, technicalspecifications (e.g., foruseofDDIandothermetadataframeworks),andencyclopediatyperesources.Similarly,thesurveyshowedaninterestinabroad range of topics across the curation life-cycle, with a somewhat lower interest only for resourcescoveringthepre-ingestandingestphases,aswellasforresourcesonPersistentIdentifiers.Inconsequence,thecollectionpolicydefinesabroadscopeoftopicsandresourcetypes(seebelow).

3.2 COLLECTIONPOLICYANDSELECTIONCRITERIAThecollectionpolicyisadocumentthatdescribeswhichtypesofresourcesonwhichtopicsarecollectedbytheCESSDAKnowledge-sharingPlatform(KSP).Thisfulfillsatwofoldobjective:Firstly, ithelpstogivethoseusingtheplatformtoaccessordepositresourcesabetterideaofthekindofcontenttheycanexpectintheplatform. Secondly, it supports the editors, who decide whether a submitted resource is accepted, indeterminingwhethertheresourcefitsthescopeofthecollection.Tofurthersupportthisdecisionprocess,selectioncriteriaarederivedfromthedefinitionofthescopeofthecollection.

ThecollectionpolicyandselectioncriteriafortheKSPareembeddedinabroaderpolicydocumentdetailingthewaytheplatformwillbeoperated.SeeAppendix3forthedraftversionofthisCollectionandOperationPolicy.

3.3 CONTENTDEVELOPMENTThemainfocusofTask2.1istheconceptualizationandimplementationoftheplatform.However,aspartofthe implementation it will be necessary to test all aspects of the platform - organizational and technicalworkflowsinparticular.Thisisonlypossiblewith“real”content,sothattheprocessofcontentdevelopmentwillbeginaswebegintoimplementtheplatform.

D2.2 – v. 1.0

Page16of30

InpreparationfortestingtheplatformacallforthepreparationofcontentwillbesentouttoCESSDAServiceProvidersandotherpotentialdepositorspartofSaW(e.g.CESSDAobserversorarchivesthatwerepartoftheCESSDAnetworkbeforeitbecameCESSDAAS).Thecallwillincludeinformationonthecollectionpolicyandselection criteria of the KSP aswell as on legal aspects to keep inmind (specifically, Intellectual PropertyRights).Whenthetestingphasebegins,allpartnersinTask2.1- inparticularthosewithonly0.5PMinthetaskwilldepositthepreparedcontent.

Inthisphase,anadditionalfocuswillbeputontwoothersourcesforcontenttobedeposited:

● Firstly, output fromother SaWwork packageswill be identified and prepared for inclusion in theplatform. In particular, this will concern the training resources created in Task 4.1 as well as theoutputsofTask5.2,whichhascloselinkswithTask2.1.

● Secondly, we will use resources created as part of the CESSDA Expert Seminars to gain a betterunderstandingof the issues thatneed tobedealtwithwhenacquiring resources for theKSP thatwerecreatedinthepastbyauthorswhomayornotstillbeemployedataCESSDASP.CESSDAExpertSeminars have taken place annually since 1987 (see http://cessda.net/CESSDA-Services/Resources/Events/Expert-Seminars).ResourcesassociatedwiththeExpertSeminarsincludepresentationsbutalsowebsiteswithschedules.AmongtheissuesthatweexpecttoencounteraredifficultieswithclarifyingthesituationregardingIntellectualPropertyRightsandobtainingtherightsfromtherespectiverightsholdertopublishthematerialsviatheplatform.

3.4 LICENSINGANDDEPOSITAGREEMENTToavoidfuturedisagreementabouttheusageandownershipoftheresourcespresentedintheKnowledge-sharingPlatform (KSP), there is aneed for commonunderstandingabout the legal rightsof the respectivepartnersinvolved.ThereisalsoaneedfortheusersoftheKSPtoknowhowtheycanusetheresources.Thisis resolved by using commonly used licensing systems. In this context, two relationships need to beconsidered:1)thatbetweendepositorandtheKSP,and2)thatbetweentheKSPandthosewhoaccessanddownloadresourcesfromit.

Thus,theKSPhastoobtainthedepositor’spermissiontostoreanddisseminateagivenresource.Atthesametime, depositors have to confirm that they have all rights required to grant the KSP the respective usagerights and that no rights of third parties are being infringed. In turn, users who access and downloadresourcesviatheKSPhavetocommittousingresourcesonlyinthewaypermittedbytherightsholder.

Whilerelationship1)willbegovernedbya“Depositandlicensingagreement”(seeAppendix4),relationship2)willbegovernedbythelicenseassignedtoeachresourcebythedepositor.

ThestakeholdersurveycarriedoutforD2.1showedveryclearlythatthereisastrongdemandforresourcestobeasopenlyaccessibleaspossible.Therefore,intheKSPguidelinesfordepositors(yettobedeveloped),itwillbecrucialtohighlightthebenefitsandtheimportanceofpublishingresourcesunderopenlicensesifatallpossible.ThisisalsoreflectedintheCollectionandOperationPolicy(Appendix3).

At the same time the survey hinted thatmany respondents did not have detailed knowledge of copyrightregulations and open licences. Therefore it seems necessary to provide general guidance on this topic forbothusersanddepositorstomakesurethattheyunderstandtheimplicationsoftherespectivelicensesforuse.

D2.2 – v. 1.0

Page17of30

4. MAINTAININGTHEPLATFORMPOST-PROJECTOneof theexpressobjectivesofestablishingtheKnowledge-sharingPlatform is thesystematicarchivingofCESSDA resources. Thus, the platform must become a long-term effort of CESSDA AS. Accordingly, itscontinuedexistenceanddevelopmentmustbeguaranteed,bothonatechnicalandacontentlevel.

4.1 PLATFORMHOSTINGHosting the DSpace platform will require running a server (LINUX) and about 1 PM/per year foradministrative/maintenance tasks. Currently, twooptions for hosting are beingdiscussedwith theCESSDATechnicalWorking Group: 1) The KSP will be hosted by CESSDA as part of its future cloud infrastructureplatform(2017).2)GESISwillhosttheserver-duringapilotphase,orindefinitely.

4.2 PLATFORMADMINISTRATIONAdministrators have responsibilities in three areas: 1) user/rightsmanagement, 2) collectionmanagement,and3)publicationofresources(seetable5).

Table5:Administrativetasks

User/rightsmanagement ● Registernewusers● Assignuserstousergroupsassociatedwithcertainrights(e.g.read,add,

write;seetable3above)● Removeusers

Collectionmanagement ● Createnewcommunities● Createnewcollections

Resourcepublication ● Publishresourcesthatwerepositivelyreviewedbyeditors

TheadministrativeworkwillbesharedbetweenCESSDATrainingandCESSDAMO.Itisexpectedthatinitiallytheworkloadwillbealittlehigher,asagreaternumberofnewuserswilllikelyregister,resourcespublishedor created in the past will be continued to be added to the platform, and SaW project results will bepublishedthroughtheplatformaswell.However,afterthisinitialphasepost-project,theexpectedworkloadperyeardoesnotexceed1PM(tobesharedbetweenCESSDATrainingandCESSDAMO).

4.3 SUBMISSIONMANAGEMENTANDCOLLECTIONDEVELOPMENTInorder to represent the interestsofCESSDASPsbut also to supportCESSDAMOandCESSDATraining inmaintaining the platform an Editorial Committeewill be formed, consisting of KSP administrators, editors,andliaisons.

Asdescribedintable3above,editorsfulfilltasksinsubmissionmanagement.They

● rejectoracceptsubmissionsbasedonthecollectionpolicyandselectioncriteria;● reviewandeditmetadataifnecessary;● assignDOIs.

Theexpectedoverallworkload(tobesharedbetweenalleditors)is1-1.25PMperyear.

Tosupporteditors,especiallyinregardtocollectionbuilding,eachSPshouldassignaliasion.Liasionsmonitorthe CESSDA-related public output created by staff of the SP, and either encourage creators to submit theresourcesorgetthepermissiontodepositresourcesforthem.TheworkloadsomewhatdependsonthesizeoftheSPanditspublicationoutput,butshouldoverallbeverysmall,rangingfrom0.1toamaximumof0.25PMperSPperyear.

D2.2 – v. 1.0

Page18of30

Together, all members of the Editorial Committee should actively support and promote collectionbuilding/development. This canbedone,on theonehand,byencouraging colleagues to submit resourcesafterCESSDAExpertSeminarsorother(training)events.Ontheotherhand,membersoftheEditorialBoardcanberesponsibleforcertaintopics(“curatedcollections”)andenhancethesebyaddingmetadatarecordsforrelevantresourcesfromoutsideCESSDAtotheKnowledge-SharingPlatform.

Table6CompositionoftheEditorialCommittee

Group Numberofpersons

Selectionprocess Durationofcommitment

Liasions 1perSP Self-selection/assignedbySP. Suggestion:2years.Individualagreementscanbemade.

Editors 4 SPsshouldbeaskedwhethertheyarewillingtocontributehumanresourcesforthistask,andwhichamount.ThiswillbedifferentforsmallerandbiggerSPs.

Suggestion:2years.Individualagreementscanbemade.RotatingamongSPsifdesired;whilerotationisdesirable,itshouldbekeptinmindthatitwillmaketrainingofneweditorsnecessarywheneverachangeoccurs.Solonger-termcommitmentsareencouraged

Admins. 2 AssignedbyCESSDAMO Indefinitely/notfixed

D2.2 – v. 1.0

Page19of30

APPENDIX1:USERSTORIESANDFUNCTIONALREQUIREMENTS1. Deposit

As a depositor... Corresponding features/functions

Technical solution?

Priority according to D2.1

...I want easily accessible information on which types of resources are accepted by the KSP so that I don’t submit something out of scope.

● Collection policy ● Selection criteria

No n/a

...I want to upload resources to the KSP in a simple procedure so that I don’t have to spend too much time on this.

● Easy registration procedure

● Simple upload procedure

● Only necessary amount of mandatory metadata fields

Partly Moderate

...I want the registration process to be simple because I don’t want to spend much time on “formalities”.

● Registration with an email address associated with a CESSDA SP

Partly n/a

...I want to freely choose the license under which a resource is shared because I want to have control over how a resources is distributed.

● Default licenses to choose from

● Custom license text

Partly n/a

...I want to understand what a license means even if I am no copyright expert.

● Licensing FAQ/Guideline

No n/a

...I want to be able to get support with uploading resources in case I have questions so I don’t have to spend more time than necessary getting familiar with the system

● User manual ● Short explanatory texts ● Helpdesk

Partly n/a

...I want my shared resources to receive a PID so that they are easily citable.

● (Semi-)automated procedure for DOI registration and assignment

Yes High

...I want to be notified when a resource I uploaded is published so I don’t have to go to the platform and check again and again myself.

● Email notifications when status of deposited resource changes

Yes n/a

...I am interested in knowing how often a resource I uploaded was accessed.

● Usage statistics Yes Moderate

D2.2 – v. 1.0

Page20of30

2. Access

As a user... Corresponding features/functions

Technical solution?


...I want to have a clear idea of the kind of resources and information that I can find on the platform.

● Collection policy No n/a

...I want to discover openly accessible resources on the KSP and elsewhere on the web so I don’t have to search in two or more places.

● Simple search ● Advanced search ● Browsing

Yes High

...I want to search the KSP without having to think about metadata fields or controlled vocabularies because I want the search process to be as easy and comprehensive as possible.

● Simple search ● Full text search

Yes Moderate

...I want to easily download interesting resources to use them in my work.

● Access to metadata and resources without registration/log-in or other barriers

● Limit search to resources where full text is available

Yes High

...I want to browse topics to discover interesting resources.

● Browse by topic ● Facets to drill down

search results

Yes High

...I want to specify search criteria so that I can find exactly what I am looking for.

● Advanced search ● Simple search + drill

down via facets

Yes High

...I want to browse curated collections on topics to discover interesting resources.

● Curated collections on topics

Yes High

...I want to download bibliographic metadata to import it into my reference management software for easy referencing and citing resources..

● Export function for metadata in BibTex format

Yes High

...I want guidance on how to cite a resource so I can easily reference works in my writing.

● “Suggested citation” automatically generated from the metadata

Yes High

...I want to be alerted to new resources on a certain topic by email, so I can keep up to date.

● Alert functions for registered users

Yes Moderate

...I want easy access to the KSP from the CESSDA Homepage so that I don’t have to visit too many different pages when looking for information.

● Link to KSP prominently from the CESSDA homepage

● Search KSP directly from CESSDA homepage

Yes High

D2.2 – v. 1.0

Page21of30

...I want the KSP and its resources to be as openly accessible as possible so that I don’t have to waste my time with complicated access procedures and so that I can use the resources from the platform easily in my work.


● ● Guidance concerning

the meaning of a specific license

Yes High

...I want to be able to search for resources in a specific language to make sure that the search results are relevant to me.

● Limit search by language (metadata)

Partly n/a

3. Management of content

As an editor... Corresponding features/functions

Technical solution?


...I want to be notified when new resources are submitted to the KSP so I can review them.

● Alert function as part of review workflow

Yes n/a

...I want a set of criteria that helps me decide whether a resource falls within the scope of the KSP or not, so I can make the decision to reject or publish a resource easily and dependably.

● Selection criteria (collection policy)

● Guidelines for editors

No n/a

...I want to be able to review and edit the metadata of a submitted resource before publication to ensure good quality of the resource description.

● Platform publication workflow: edit submission

Yes n/a

...I want to be able to assign a DOI to a submitted resource accepted for publication in a simple process.

● Platform publication workflow: register DOI

Yes n/a

4. Management of platform (incl. user management)

As an editor... Corresponding features/functions

Technical solution?


...I want to be able to get in touch with depositors to let them know that their resource needs further editing.

● Publication workflow: Accept/reject submission

Yes n/a

As an administrator... Corresponding features/functions

Technical solution?


...I want to have easy access to all information necessary to decide if a

● List of organizations and email domain

No n/a

D2.2 – v. 1.0

Page22of30

newly registered depositor falls within the scope of the KSP’s intended community of depositors.

names

...I want to accept or reject depositors who have registered with the platform to give me control over who can publish things in the KSP.

● Registration workflow Yes n/a

...I want to be able to assign editors to take care of the publication workflow for certain communities and collections

● User management routine

Yes n/a

...I want to be able to customize the design of the KSP to adapt it to the CESSDA corporate design.

● Customizable style sheets

Yes n/a

...I want to generate statistics about the size of the collection and its use to better understand the interests and needs of the user community.

● Statistics for ○ Items (by

topic, by institution) on the platform

○ Number of users

○ Use by topic

Yes n/a

5. Other

User story Corresponding features/functions

Technical solution?


As a user, I want to have the possibility of suggesting resources to the editorial committee for inclusion in the platform without too much effort.

● Form on the webpage that allows suggestion of resources

Yes n/a

D2.2 – v. 1.0

Page23of30

APPENDIX2:FUNCTIONALREQUIREMENTSANDCORRESPONDINGDSPACE5.XFUNCTIONS1. Deposit

Required features/functions DSpace 5.x support Priority according to D2.1

● Easy registration procedure Different registration and authentication processes supported - self registration by web form and subsequent log in with user name and password, or authentication via LDAP or Shibboleth.

Moderate

● Simple upload procedure The following features can be used to make the deposit procedure as easy/efficient as possible:Fully customizable metadataChoice management and authority control to help users entering controlled metadata valuesCustomizable licenses, including support for Creative Commons;

Moderate

● Designation of mandatory/optional metadata fields

Supported. Fully customizable. Moderate

● Flexible licensing of content DSpace offers support for Creative Commons; license texts are fully customizable by both admins (to define options to choose from) or by users who want to enter a specific license text.

n/a

● Explanatory/help texts in context Short info texts can be shown when hovering the cursor over a given word/icon on the page.

n/a

● (Semi-)automated procedure for DOI registration and assignment

By default, DSpace uses the CNRI Handle System to assign globally unique identifiers to communities, collections and items. The GESIS WTS department has developed a routine that allows to assign a DOI to items in the repository using the da|ra service. This functionality will be re-used for the CESSDA KSP.

High

● Email notifications when status of deposited resource changes

Supported. n/a

● Usage statistics for individual resources

Supported. Moderate

2. Access

Required features/functions DSpace 5.x support Priority according to

D2.2 – v. 1.0

Page24of30

D2.1

● Simple search ● Advanced search

DSpace uses the search engine Lucene. The search function is fully customizable: keyword search in all or limited to specific metadata fields is supported.

High

● Full text search Supported for text based contents Moderate

● Facets to drill down search results

Faceted browsing is supported for any metadata field.

High

● Browsing Users can browse the following indices: title, author, issue date, subject terms. It is possible to limit browsing to specific parts of an index, e.g. to only browse items in a particular collection or community.

High


Anonymous discovery and retrieval are supported.

High

● Collections on topics DSpace supports the creation of so-called “Communities” and “Collections”. These can be used to organize the items stored in the repository, e.g. by topic. A community contains collections, defined as “groupings of related content”. It is possible for a collection to appear in different communities.

High

● Export function for metadata in BibTex format

Not supported out of the box. Implementation effort: 0.25 PM

High

● “Suggested citation” automatically generated from the metadata

Not supported out of the box. Implementation effort: 0.25 PM

High

● Alert functions for registered users

Registered users can subscribe to collections in DSpace and are notified by e-mail about new items in these collections.

Moderate

3. Management of content


● Alert function as part of review workflow when new items are submitted

Supported n/a

● Platform publication workflow: edit metadata of submission

Supported n/a

● Platform publication workflow: register DOI

The GESIS WTS department has developed a routine that allows to assign a DOI to items in the repository using the da|ra service. This functionality will be re-used for the CESSDA KSP.

n/a

D2.2 – v. 1.0

Page25of30

4. Management of platform (incl. user management)


● Publication workflow: Accept/reject submission

Supports a customizable submission workflow which allows for the rejection or acceptance of submissions.

n/a

● Registration workflow: accept/reject depositors

Supported. “Deposit” rights have to be actively assigned to newly registered users.

n/a

● Assigning roles and associated rights to users

DSpace supports an authorization system based on so-called “Resource Policies”. These policies are used to determine which actions can be performed for a given object and which group of users has permission to do so. Users are given a set of permissions by assigning them to a certain group.

n/a

● Customizable style sheets DSpace supports two user interfaces, one is based on JavaServer Pages (JSP), the other one on the Apache Cocoon framework (XMLUI). These can be customized to match the CESSDA corporate design.

n/a

● Statistics for ○ Items (by topic, by

institution) on the platform

○ Number of users ○ Use by topic

Usage metrics are provided based on SOLR. Statistics are available on item, collection, and community levels.They include page visits and downloads. In addition, system statistics allow to generate reports on the content and use of the repository drawing on DSpace’s log files. This includes user logins and popular searches among other things.

n/a

5. Other


● Integration with CESSDA Webpage

Depending on the preferred solution, this will require an implementation effort of 0.5 PM

n/a

D2.2 – v. 1.0

Page26of30

APPENDIX3:COLLECTIONANDOPERATIONPOLICY(DRAFT) 1.IntroductionTheCESSDAKnowledge-sharingplatform(KSP)isacentralpointofaccessforthebodyofknowledgecreatedbyCESSDApartners.Thispolicyisintendedtoserveasaguidetothedevelopment,managementandcareofthecollectiontoachievetheoverallmissionoftheKSP.Itdefinesmission,purpose,scope,selectioncriteriaandstakeholders’roles.2.MissionOvertheyears,CESSDApartnershavecreatedasignificantbodyofknowledgeonabroadrangeoftopics.TheKSPisintendedtosupportthesystematicandstructureddescriptionoftheseresources(1).IttherebyaimstopromoteabroadexchangeofknowledgeamongCESSDAServiceProviders(SPs)andthecommunitiestheyserve(2).Tofosterknowledgeexchangeinthebestpossibleway,resourcesshouldbefreelyaccessibletoeveryonetouseandrepublishastheywish,withaslittlerestrictionsfromcopyrightorothermechanismsofcontrolaspossible.TheKSPshouldbeasopenandbarrierfreeaspossible(3).TheKSPaimstobecomeaspecialcollection:inaspecificallydefinedfieldofknowledgethatstrivestobeexhaustive,asfarasisreasonablypossible:

● Exhaustivecollectionofdigitalmaterials● Extensivecollectionofrecordsaboutpublishedmaterials(metadata).

3.PurposeTheKSPservesthesystematiccollection,registration,descriptionof,andlong-termaccesstodifferentresourcesproducedbyCESSDASPorforCESSDASPwiththepurposeoffosteringknowledge-exchangeandskillstransferintheEuropeanSocialScienceDataArchivinglandscape.TheKSPminimizestheriskthatresourcesarelostorbecomeinaccessible.4.ScopeTheKSPmainlykeepsacurrentfocus,butitwillalsoseektogatherresourcesretrospectively.ThisincludesdocumentationofCESSDAExpertSeminarsandotherCESSDAevents.TheKSPfocusesondigitalresources,butalsomaintainsmetadatarecordsaboutpublicationsorotherrelatedmaterials.TheKSPacquiresmaterialsinthenationallanguagesoftheCESSDASPs,however,aminimummetadatashouldbeprovidedinEnglishforallmaterialsincludedinthecollection.TheCollectionconsistsof:

● resourcesdescribingorcoveringdifferentareasofworkinsocialsciencedataservices,suchas:DataAccess,Dissemination,andOpenData,Archiving(CurationandPreservation),MetadataandStandards,ResearchDataManagement,Pre-ingest,DataAcquisition,DataProcessingandDocumentation,Ingest,Training,ManagementofDataArchives,DataProtectionandEthics,PersistentIdentifiers,andOther.

● Differentresourcetypes,suchas:Trainingresources:Guidelinesormanuals,Trainingresources:Webinars,Trainingresources:e-tutorials,Softwaretools,Policyoradvocacydocuments,Presentations,ReportsandalsoUsersatisfactionsurveys,Scholarlypublications(e.g.articles,collections,monographs),Blogpostsorothersocialmedia,otherTrainingresources.

● MaterialsinalllanguagesusedbyCESSDASPs,withaminimumofdescriptivemetadatainEnglish.

D2.2 – v. 1.0

Page27of30

5.ResponsibilityTheKSPtakesresponsibilityforthelong-termaccesstoandprotectionofresourcesinthecollection.TrainingsandmanagementaredevelopedaccordinglybytheCESSDAMainOfficeincooperationwiththeEditorialCommittee.6.Selectioncriteria

1. Scope:Resourceshouldberelatedtothescopeasdefinedinthisdocument.2. Content:ResourceshouldberelevanttootherCESSDAmembersorobservers,itshouldbringnew

(added)value.Duplicationofdocumentswiththesameorverysimilarcontentshouldbeavoided,exceptions:resourceisofferedinadifferentlanguage.

3. Language:ResourcecanbeinanylanguageusedbyCESSDAmembers,butaminimumofdescriptivemetadatashouldbeprovidedinEnglish.

4. Copyright:Resourceshouldpreferablyuseanopenlicence(e.g.CreativeCommonsorGPL).Ifnoopenlicenseisprovided,theKSPmaydecideonlytorecordthemetadataoftheresource.

5. Duplication:IfaresourcehasbeenalreadypublishedelsewhereandreceivedaPID,theKSPcollectsonlymetadata.

Selectioncriteriaaretobeusedby(potential)depositorsandeditors.7.StakeholdersStakeholdersperformdifferentrolesfortheKSP.Thesearedistinguishedasfollows:

● Depositors:submitresourcestotheplatform.● Users:searchforanddownloadcontentfromtheplatform.● Editors:managethecontent-sideoftheplatform.● Administrators:managethetechnology-sideoftheplatform

Stakeholderscomefrom:● CESSDAMainOffice● KSPEditorialCommittee● CESSDAServiceProviders● CESSDAObserversandaspiringServiceProviders● Other(socialscience)dataarchives● Socialscienceeducators● Socialscienceresearchers● Academicsupportstaff(administration,librarystaff,etc.)● CESSDAMembers(i.e.ministries)● PolicymakersonnationalandEuropeanlevel● Other

8.PlatformuseandmanagementStakeholdersasdefinedinthefollowingareinvitedtoshareandaccessresources,forexampletosupporttheprocessofsettinguporrunningadataserviceasaserviceprovidertoCESSDA.8.1DepositorsDepositorscomefrom:

● CESSDAMainOffice● KSPEditorialCommittee● CESSDAServiceProviders● CESSDAObserversandaspiringServiceProviders

D2.2 – v. 1.0

Page28of30

Depositorssubmitresourcestotheplatform.They:1)Checkiftheresourcefitsselectioncriteria2)ProvidemetadataanddescriptioninEnglish,eveniftheresourcesisinalanguageotherthanEnglish.Tosupportthedepositprocess,itisrecommendedthatCESSDASPsassignaliaisonresponsiblefordepositingresourcestotheKSP.8.2EditorsEditorscomefrom:

● CESSDAMainOffice● KSPEditorialCommittee

Editorsmanagethecontent-sideoftheplatform.Editorsfollowselectioncriteriatoreducepersonalbiasbysettingindividualselectiondecisionsandtoensurecontinuityandconsistencyinselectionandrevision.EditorsareelectedbyCESSDAMainOffice/BoardofDirectors/GeneralAssemblyforthemandateoftwoyears.Theycanbere-elected.NumberofeditorsandtheirmandateisdeterminedbyCESSDAMainOffice.8.3AdministratorsAdministratorsmanagethetechnology-sideoftheplatform.TheyareappointedbyCESSDAMainOffice.8.4UsersAnyonecanusetheresourcescollectedintheKSP.However,itisenvisionedthatusersmainlycomefrom:

● CESSDAMainOffice● KSPEditorialCommittee● CESSDAServiceProviders● CESSDAObserversandaspiringServiceProviders● Other(socialscience)dataarchives● Socialscienceeducators● Socialscienceresearchers● Academicsupportstaff(administration,librarystaff,etc.)● CESSDAMembers(i.e.ministries)● PolicymakersonnationalandEuropeanlevel

Userssearchforanddownloadcontentfromtheplatform.TheKSPdistinguishesAnonymousandRegisteredUsers.KSPresourcesusedin(research)publicationsmustbecitedaccuratelyandinsufficientdetail.Sourcesarecitedwithinthetext,withintablesandgraphs,andinpublicationreferences.8.5KSPEditorialCommitteeTheroleoftheCommitteeistovouchsafethelong-termdevelopmentandmanagementoftheplatform,andactasaninstanceofqualityassurance.TheEditorialCommitteeconsistsofKSPadministrators,editors,andliaisons.

D2.2 – v. 1.0

Page29of30

Ifnootheragreementsaremade,membersoftheEditorialcommitteeareappointedforaperiodof2years.9.Revisionofthedocument/policyPolicyistobereviewedandupdatedaccordingtothedevelopmentandneeds.

D2.2 – v. 1.0

Page30of30

APPENDIX4:DEPOSITANDLICENSINGAGREEMENTFORRESOURCESUPLOADED

TOTHECESSDAKNOWLEDGE-SHARINGPLATFORM(DRAFT)ThisdepositagreementismodeledonthecontractusedbytheUniversityofGothenburginitslibrary'sopenaccesssystem.IthasbeencheckedbytheUniversitylawyerforvalidity.

1.AgreementforpublishingontheCESSDAKnowledge-SharingPlatform

TheOwneroftheResourceundertakestogranttherighttotheConsortiumofEuropeanSocialScienceDataArchives (CESSDA) to publish the Resource on the CESSDA Knowledge-Sharing Platform (KSP). The right topublishincludestherighttomaketheResourceavailable.ThisagreementshallnotimposeanylimitationsoftheOwner’srighttomakeuseoftheResource.

2.Durationandcancellationoftheagreement

TheagreementshallremaininforceuntiltheOwnernotifiesCESSDAthattherightshallbecancelled.UponacancellationCESSDAnolongerhastherighttopublishtheResourceontheCESSDAKSPandshallimmediatelyremove theResource. CESSDA can, on its behalf, cancel the agreement with immediate effect andhenceremovetheResourcefromtheKSP.Nomotivationneedstobestatedfortheremoval.

3.OriginsoftheResource

The Owner shall ensure that she/he/they has the right to use included material where appropriate(illustrationsetc),andhastherighttodisposeoftheResourceforpublicationinaccordancewiththepresentagreement.

ShoulditbeknownthattheOwnerdoesnothavethepermissiontousepartoftheResourceortheResourceinitswhole,orlackthenecessarypermissionsasstatedabove,theOwnershallensuretoindemnifyCESSDA.

4.Publicationlicense

PleasechooseunderwhichlicencetheResourcecanbeusedbythirdparties.

● CCBYhttps://creativecommons.org/licenses/by/4.0/● CCBYNChttps://creativecommons.org/licenses/by-nd/4.0/● CCBYNCSAhttps://creativecommons.org/licenses/by-nc-sa/4.0/● CCBYNCNDhttps://creativecommons.org/licenses/by-nc-nd/4.0/● Other_________(pleaseprovideaname/descriptionofthepreferredlicense)

If you need help deciding on a license, use this license selector: https://ufal.github.io/public-license-selector/#

5.Reimbursement

No reimbursements are to follow from this agreement.Anyassociated costs are the responsibilityof eachpartrespectively.

6.Validityoftheagreement

ThepresentagreementshallcomeintoforceimmediatelyafteracceptancebytheOwner.

CESSDA Strengthening and Widening · D2.2 – v. 1.0 Page 4 of 30 EXECUTIVE SUMMARY Over the years,...

Documents

Transcript of CESSDA Strengthening and Widening · D2.2 – v. 1.0 Page 4 of 30 EXECUTIVE SUMMARY Over the years,...