| Architecture |
Access, Performance, Storage, Data quality, Data security |
Axelsson and Schroeder, 2009; Constable et al., 2010; Cooper, 2007; De Wolf et al., 2006; Enke et al., 2012; Haddow et al., 2011; Huang et al., 2012; Jarnevich et al., 2007; Kowalczyk and Shankar, 2011; Linkert et al., 2010; Resnik, 2010; Rodgers and Nolte, 2006; Rushby, 2013; Sayogo and Pardo, 2013; Teeters et al., 2008 |
Access: “It is not permitted, for example, for a faculty member to obtain the data for his or her own research project and then “lend” it to a graduate student to do related dissertation research, even if the graduate student is a research staff signatory, unless this use is specifically stated in the research plan.” (Rodgers and Nolte, 2006, p. 90) |
| Usability |
Tools and applications, Technical support |
Axelsson and Schroeder, 2009; Haendel et al., 2012; Mennes et al., 2013; Nicholson and Bennett, 2011; Ostell, 2009; Teeters et al., 2008 |
Tools and applications: “At the same time, the platform should make it easy for researchers to share data, ideally through a simple one-click upload, with automatic data verification thereafter.” (Mennes et al. 2013, p. 688) |
| Management software |
Data documentation, Metadata standards |
Acord and Hartley, 2012; Axelsson and Schroeder, 2009; Breese et al., 2012; Constable et al., 2010; Delson et al., 2007; Edwards et al., 2011; Enke et al., 2012; Gardner et al., 2003; Jiang et al., 2013; Jones et al., 2012; Karami et al., 2013; Linkert et al., 2010; Myneni and Patel, 2010; Nelson, 2009; Parr, 2007; Sansone and Rocca-Serra, 2012; Teeters et al., 2008; Tenopir et al., 2011 |
Data documentation: “The authors came to the conclusion that researchers often fail to develop clear, well-annotated datasets to accompany their research (i.e., metadata), and may lose access and understanding of the original dataset over time.” (Tenopir et al. 2011, p. 2) |
