69:
also claimed to increase research efficiency since both the data collector and other researchers might be able to understand and use well-annotated data in the future. One component of a data management plan is data archiving and preservation. By deciding on an archive ahead of time, the data collector can format data during collection to make its future submission to a database easier. If data are preserved, they are more relevant since they can be re-used by other researchers. It also allows the data collector to direct requests for data to the database, rather than address requests individually. A frequent argument in favor of preservation is that data that are preserved have the potential to lead to new, unanticipated discoveries, and they prevent duplication of scientific studies that have already been conducted. Data archiving also provides insurance against loss by the data collector.
376:(ESRC) have had a research data policy in place. The current ESRC Research Data Policy states that research data created as a result of ESRC-funded research should be openly available to the scientific community to the maximum extent possible, through long-term preservation and high-quality data management.
379:
ESRC requires a data management plan for all research award applications where new data are being created. Such plans are designed to promote a structured approach to data management throughout the data lifecycle, resulting in better quality data that is ready to archive for sharing and re-use. The
68:
Preparing a data management plan before data are collected is claimed to ensure that data are in the correct format, organized well, and better annotated. This could arguably save time in the long term because there is no need to re-organize, re-format, or try to remember details about data. It is
272:
Researchers should identify an appropriate archive for the long-term preservation of their data. By identifying the archive early in the project, the data can be formatted, transformed, and documented appropriately to meet the requirements of the archive. Researchers should consult colleagues and
424:
practices. Most funders do not require a DMP after grants are awarded, thus robbing stakeholders of the powerful tool that an active DMP can be. Best practice would be to "require maintenance of the data management plan following award and during the active phase of a study." At present, data
55:
and analysis, and expanded across engineering and scientific disciplines in the 1970s and 1980s. Up until the early 2000s, DMPs were used "for projects of great technical complexity, and for limited mid-study data collection and processing purposes". In the 2000s and later,
185:
are the contextual details, including any information important for using data. This may include descriptions of temporal and spatial details, instruments, parameters, units, files, etc. Metadata is commonly referred to as “data about data”. Issues to be considered include:
316:(NSF) must include a Data Management Plan that is no more than two pages. This is a supplement (not part of the 15-page proposal) and should describe how the proposal will conform to the Award and Administration Guide policy (see below). It may include the following:
395:, as a place of deposit for research data, with award holders required to offer data resulting from their research grants via the UK Data Service. The Archive enables data re-use by preserving data and making them available to the research and teaching communities.
289:
Data management and preservation costs may be considerable, depending on the nature of the project. By anticipating costs ahead of time, researchers ensure that the data will be properly managed and archived. Potential expenses that should be considered are
403:
There are three major themes identified in the literature in terms of benefits of DMPs: professional benefits, economic benefits and institutional benefits. It has been argued that DMPs can form a catalyst for researchers to improve their
420:'s list of criteria for a DMP. Researchers shared DMP text. DMPs are often regarded as an "administrative exercise rather than an integral part" of the research process, and it has been acknowledged that DMPs do not guarantee good
276:
Early in the project, the primary researcher should identify what data will be preserved in an archive. Usually, preserving the data in its most raw form is desirable, although data derivatives and products can also be
217:
Include information about how data will be shared, including when the data will be accessible, how long the data will be available, how access can be gained, and any rights that the data collector reserves for using
232:
issues. Who owns the copyright? What are the institutional, publisher, and/or funding agency policies associated with intellectual property? Are there embargoes for political, commercial, or patent reasons?
280:
An individual should be identified as the primary contact person for archived data, and ensure contact information is always kept up-to-date in case there are requests for data or information about data.
273:
professional societies in their discipline to determine the most appropriate database, and include a backup archive in their data management plan in case their first choice goes out of existence.
923:
238:
Indicate how the data should be cited by others. How will the issue of persistent citation be addressed? For example, if the data will be deposited in a public archive, will the dataset have a
80:"There is no general and definitive list of topics that should be covered in a DMP for a research project", and researchers are often left to their own devices as to how to fill out a DMP.
214:
Describe any obligations that exist for sharing data collected. These may include obligations from funding agencies, institutions, other professional organizations, and legal requirements.
153:
If existing data are used, what are their origins? How will the data collected be combined with existing data? What is the relationship between the data collected and existing data?
416:
In practice, however, DMPs often fall short of their stated goals. A 2012 review of DMP policies by research funders found that policies were missing several elements from the
384:, the ESRC's flagship data service, provides practical guidance on research data management planning suitable for social science researchers in the UK and around the world.
72:
In the 2010s, funding agencies increasingly required data management plans as part of the proposal and evaluation process, despite little or no evidence of their efficacy.
700:
349:
Investigators can keep their legal rights over their intellectual property, but they still have to make their results, data, and collections available to others
894:
892:
Dietrich, Dianne; Adamus, Trisha; Miner, Alison; Steinhart, Gail (2012). "De-Mystifying the Data
Management Requirements of Research Funders".
736:
469:
48:
before the project begins; this may lead to data being well-managed in the present, and prepared for preservation in the future.
1121:: DMP Toolkit of The Consortium of Universities of the Region of Madrid and the UNED for Library Cooperation (Madroño - Spain)
595:
373:
336:
Policy summarized from the NSF Award and
Administration Guide, Section 4 (Dissemination and Sharing of Research Results):
711:
150:
Quality assurance & quality control measures that will be taken during sample collection, analysis, and processing.
1066:
1038:
845:
631:
676:
343:
Share data, samples, physical collections, and supporting materials with others, within a reasonable time frame
89:
A description of data to be produced by the project. This might include (but is not limited to) data that are:
1107:
1087:
921:
Parham, Susan Wells; Doty, Chris (October 2012). "NSF DMP content analysis: What are researchers saying?".
204:
commonly used in the respective scientific discipline? There should be justification for the format chosen.
297:
Hardware and/or software needed for data management, backing up, security, documentation, and preservation
313:
1102:
966:
787:
247:
751:
498:"From Plan to Action: Successful Data Management Plan Implementation in a Multidisciplinary Project"
1134:
417:
822:
147:
File formats that will be used, justify those formats, and describe the naming conventions used.
759:
243:
239:
225:
975:
8:
392:
97:
979:
1097:
1011:
998:
961:
653:
626:
559:
251:
201:
1029:
Donelly, Martin (2012). "Data management plans and planning". In Pryor, Graham (ed.).
1062:
1034:
1003:
730:
658:
577:
92:
41:
1015:
563:
540:
Smale, Nicholas; Unsworth, Kathryn; Denyer, Gareth; Barr, Daniel (17 October 2018).
477:
32:
is completed. The goal of a data management plan is to consider the many aspects of
993:
983:
940:
932:
903:
806:"Dissemination and Sharing of Research Results - NSF - National Science Foundation"
648:
640:
551:
541:
509:
51:
DMPs were originally used in 1966 to manage aeronautical and engineering projects'
599:
988:
960:
Miksa, Tomasz; Simms, Stephanie; Mietchen, Daniel; Jones, Sarah (28 March 2019).
936:
434:
421:
388:
381:
159:
52:
33:
294:
Personnel time for data preparation, management, documentation, and preservation
1112:
833:
805:
644:
1128:
514:
497:
405:
45:
1115:: Prepare and Manage Data: Guidance and tools for social science researchers
874:
131:
After collection, how will the data be processed? Include information about
1007:
662:
449:
439:
194:
853:
190:
How detailed has the metadata to be in order to make the data meaningful?
1118:
425:
sharing plans are more important than data management plans to funders.
156:
How will the data be managed in the short-term? Consider the following:
924:
Bulletin of the
American Society for Information Science and Technology
625:
Williams, Mary; Bagwell, Jacqueline; Nahm Zozus, Meredith (July 2017).
496:
Burnette, Margaret; Williams, Sarah; Imker, Heidi (16 September 2016).
57:
945:
304:
The data management plan should include how these costs will be paid.
907:
444:
229:
128:
How will the data be acquired? When and where will they be acquired?
555:
193:
How will the metadata be created and/or captured? Examples include
182:
140:
102:
37:
596:"Data Management & Sharing Frequently Asked Questions (FAQs)"
546:
323:
The standards to be used for data and metadata format and content
29:
60:
and economic policies drove the development and uptake of DMPs.
28:
are to be handled both during a research project, and after the
1092:
962:"Ten principles for machine-actionable data management plans"
542:"The History, Advocacy and Efficacy of Data Management Plans"
891:
846:"Managing and Sharing Research Data - SAGE Publications Inc"
197:, GPS hand-held units, Auto-saved files on instruments, etc.
408:
and data management practices, often aided by the library.
255:
208:
83:
25:
1084:: Create Smart Data Management Plans for FAIR Open Science
834:
Prepare and manage data: Guidance from the UK Data
Service
624:
259:
1081:
266:
200:
What format will be used for the metadata? What are the
959:
539:
300:
Costs associated with submitting the data to an archive
221:
Address any ethical or privacy issues with data sharing
578:"Why manage & share your data? - Data management"
495:
235:
Describe the intended future uses/users for the data
168:
Security & protection of data and data products
775:Ecological Data: Design, Management and Processing
1126:
627:"Data management plans: the missing perspective"
620:
618:
616:
491:
489:
487:
1108:LTER Blog: How to write a data management plan
895:Issues in Science and Technology Librarianship
177:
1033:. London: Facet Publishing. pp. 83–104.
387:ESRC has a longstanding arrangement with the
1059:Delivering research data management services
752:"Tools for version control of research data"
613:
535:
533:
531:
529:
527:
525:
484:
367:
340:Promptly publish with appropriate authorship
307:
920:
997:
987:
944:
652:
522:
513:
209:Policies for access, sharing, and re-use
84:Information about data & data format
1028:
24:is a formal document that outlines how
1127:
735:: CS1 maint: archived copy as title (
171:Who will be responsible for management
1056:
267:Long-term storage and data management
875:"UK Data Archive - WHO CAN DEPOSIT?"
677:"Elements of a Data Management Plan"
374:Economic and Social Research Council
75:
13:
1051:
329:Policies and provisions for re-use
14:
1146:
1075:
632:Journal of Biomedical Informatics
502:Journal of eScience Librarianship
358:Award negotiations and conditions
352:Policies will be implemented via
312:All grant proposals submitted to
165:Backing up data and data products
773:Michener,WK and JW Brunt. 2000.
749:
1119:Plan de GestiĂłn de Datos PaGoDa
1022:
953:
914:
885:
867:
838:
827:
816:
798:
780:
767:
326:Policies for access and sharing
823:ESRC Research Data Policy 2010
743:
693:
669:
588:
570:
474:University of Virginia Library
462:
411:
1:
1103:NSF Grant Proposal Guidelines
455:
346:Share software and inventions
63:
989:10.1371/journal.pcbi.1006750
937:10.1002/bult.2012.1720390113
7:
428:
398:
314:National Science Foundation
178:Metadata content and format
10:
1151:
967:PLOS Computational Biology
777:. Blackwell Science, 180p.
645:10.1016/j.jbi.2017.05.004
368:ESRC Data Management Plan
284:
515:10.7191/jeslib.2016.1101
332:Plans for archiving data
308:NSF Data Management Plan
1098:Digital Curation Centre
1082:Data Stewardship Wizard
418:Digital Curation Centre
1057:Pryor, Graham (2014).
1031:Managing research data
879:www.data-archive.ac.uk
470:"Data Management Plan"
760:University of Antwerp
372:Since 1995, the UK's
240:persistent identifier
226:intellectual property
1061:. Facet Publishing.
141:Scientific workflows
117:Curriculum materials
108:Physical collections
18:data management plan
980:2019PLSCB..15E6750M
681:www.icpsr.umich.edu
393:University of Essex
361:Support/incentives
202:metadata standards
708:libraries.mit.edu
582:libraries.mit.edu
320:The types of data
262:) assigned to it?
42:data preservation
1142:
1072:
1045:
1044:
1026:
1020:
1019:
1001:
991:
957:
951:
950:
948:
918:
912:
911:
908:10.5062/F44M92G2
889:
883:
882:
871:
865:
864:
862:
861:
852:. Archived from
842:
836:
831:
825:
820:
814:
813:
802:
796:
795:
788:"GPG Chapter II"
784:
778:
771:
765:
764:
756:
747:
741:
740:
734:
726:
724:
722:
716:
710:. Archived from
705:
697:
691:
690:
688:
687:
673:
667:
666:
656:
622:
611:
610:
608:
607:
598:. Archived from
592:
586:
585:
574:
568:
567:
537:
520:
519:
517:
493:
482:
481:
476:. Archived from
466:
76:Major components
1150:
1149:
1145:
1144:
1143:
1141:
1140:
1139:
1135:Data management
1125:
1124:
1113:UK Data Service
1078:
1069:
1054:
1052:Further reading
1049:
1048:
1041:
1027:
1023:
974:(3): e1006750.
958:
954:
919:
915:
890:
886:
873:
872:
868:
859:
857:
850:www.sagepub.com
844:
843:
839:
832:
828:
821:
817:
804:
803:
799:
786:
785:
781:
772:
768:
754:
748:
744:
728:
727:
720:
718:
714:
703:
701:"Archived copy"
699:
698:
694:
685:
683:
675:
674:
670:
623:
614:
605:
603:
594:
593:
589:
576:
575:
571:
538:
523:
494:
485:
480:on Nov 9, 2012.
468:
467:
463:
458:
435:Data management
431:
422:data management
414:
401:
391:, based at the
389:UK Data Archive
382:UK Data Service
370:
355:Proposal review
310:
287:
269:
211:
180:
160:Version control
86:
78:
66:
53:data collection
34:data management
12:
11:
5:
1148:
1138:
1137:
1123:
1122:
1116:
1110:
1105:
1100:
1095:
1090:
1085:
1077:
1076:External links
1074:
1067:
1053:
1050:
1047:
1046:
1039:
1021:
952:
913:
884:
866:
837:
826:
815:
797:
779:
766:
742:
692:
668:
612:
587:
569:
556:10.1101/443499
521:
483:
460:
459:
457:
454:
453:
452:
447:
442:
437:
430:
427:
413:
410:
400:
397:
369:
366:
365:
364:
363:
362:
359:
356:
350:
347:
344:
341:
334:
333:
330:
327:
324:
321:
309:
306:
302:
301:
298:
295:
286:
283:
282:
281:
278:
274:
268:
265:
264:
263:
236:
233:
222:
219:
215:
210:
207:
206:
205:
198:
191:
179:
176:
175:
174:
173:
172:
169:
166:
163:
154:
151:
148:
145:
144:
143:
138:
135:
129:
126:
125:
124:
121:
118:
115:
112:
109:
106:
100:
95:
85:
82:
77:
74:
65:
62:
9:
6:
4:
3:
2:
1147:
1136:
1133:
1132:
1130:
1120:
1117:
1114:
1111:
1109:
1106:
1104:
1101:
1099:
1096:
1094:
1091:
1089:
1086:
1083:
1080:
1079:
1073:
1070:
1068:9781856049337
1064:
1060:
1042:
1040:9781856048910
1036:
1032:
1025:
1017:
1013:
1009:
1005:
1000:
995:
990:
985:
981:
977:
973:
969:
968:
963:
956:
947:
942:
938:
934:
930:
926:
925:
917:
909:
905:
901:
897:
896:
888:
880:
876:
870:
856:on 2014-04-07
855:
851:
847:
841:
835:
830:
824:
819:
811:
807:
801:
793:
789:
783:
776:
770:
762:
761:
753:
746:
738:
732:
717:on 4 May 2018
713:
709:
702:
696:
682:
678:
672:
664:
660:
655:
650:
646:
642:
638:
634:
633:
628:
621:
619:
617:
602:on 2017-07-11
601:
597:
591:
583:
579:
573:
565:
561:
557:
553:
549:
548:
543:
536:
534:
532:
530:
528:
526:
516:
511:
507:
503:
499:
492:
490:
488:
479:
475:
471:
465:
461:
451:
448:
446:
443:
441:
438:
436:
433:
432:
426:
423:
419:
409:
407:
406:data literacy
396:
394:
390:
385:
383:
377:
375:
360:
357:
354:
353:
351:
348:
345:
342:
339:
338:
337:
331:
328:
325:
322:
319:
318:
317:
315:
305:
299:
296:
293:
292:
291:
279:
275:
271:
270:
261:
257:
253:
249:
245:
241:
237:
234:
231:
227:
223:
220:
216:
213:
212:
203:
199:
196:
195:lab notebooks
192:
189:
188:
187:
184:
170:
167:
164:
161:
158:
157:
155:
152:
149:
146:
142:
139:
136:
134:Software used
133:
132:
130:
127:
122:
119:
116:
113:
110:
107:
104:
101:
99:
98:Observational
96:
94:
91:
90:
88:
87:
81:
73:
70:
61:
59:
54:
49:
47:
43:
39:
35:
31:
27:
23:
19:
1058:
1055:
1030:
1024:
971:
965:
955:
931:(1): 37–38.
928:
922:
916:
899:
893:
887:
878:
869:
858:. Retrieved
854:the original
849:
840:
829:
818:
809:
800:
791:
782:
774:
769:
758:
745:
719:. Retrieved
712:the original
707:
695:
684:. Retrieved
680:
671:
636:
630:
604:. Retrieved
600:the original
590:
581:
572:
545:
508:(1): e1101.
505:
501:
478:the original
473:
464:
450:Open science
440:Data sharing
415:
402:
386:
378:
371:
335:
311:
303:
288:
181:
93:Experimental
79:
71:
67:
50:
40:generation,
21:
17:
15:
810:www.nsf.gov
792:www.nsf.gov
750:Guns, Raf.
639:: 130–142.
412:In practice
114:Simulations
946:1853/44391
860:2014-04-01
721:12 January
686:2015-09-30
606:2018-04-06
550:: 443499.
456:References
277:preserved.
137:Algorithms
105:or derived
64:Importance
58:E-research
1093:DMPonline
445:Open data
230:copyright
162:for files
1129:Category
1016:85563774
1008:30921316
731:cite web
663:28499952
564:91931719
429:See also
399:Benefits
224:Address
183:Metadata
120:Software
46:analysis
38:metadata
1088:DataONE
999:6438441
976:Bibcode
654:6697079
547:bioRxiv
242:(e.g.,
30:project
1065:
1037:
1014:
1006:
996:
902:(70).
661:
651:
562:
285:Budget
252:Handle
228:&
123:Images
111:Models
44:, and
1012:S2CID
755:(PDF)
715:(PDF)
704:(PDF)
560:S2CID
218:data.
1063:ISBN
1035:ISBN
1004:PMID
737:link
723:2022
659:PMID
256:PURL
26:data
994:PMC
984:doi
941:hdl
933:doi
904:doi
649:PMC
641:doi
552:doi
510:doi
260:URN
248:DOI
244:ARK
103:Raw
22:DMP
20:or
1131::
1010:.
1002:.
992:.
982:.
972:15
970:.
964:.
939:.
929:39
927:.
900:70
898:.
877:.
848:.
808:.
790:.
757:.
733:}}
729:{{
706:.
679:.
657:.
647:.
637:71
635:.
629:.
615:^
580:.
558:.
544:.
524:^
504:.
500:.
486:^
472:.
258:,
254:,
250:,
246:,
36:,
16:A
1071:.
1043:.
1018:.
986::
978::
949:.
943::
935::
910:.
906::
881:.
863:.
812:.
794:.
763:.
739:)
725:.
689:.
665:.
643::
609:.
584:.
566:.
554::
518:.
512::
506:5
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.