48 · Survey Results: Survey Questions and Responses
DATA ARCHIVE CHARACTERISTICS
We would appreciate more details about the characteristics of your current research data archiving solution.
21. Please specify your library’s archiving solution. Check all that apply. N=40
Our institutional repository is used to archive research data (and used for text documents) 32 80%
The library hosts or is directly involved with archiving research data at an external archive or repository
service, such as DuraSpace or Dataverse
17 43%
The library operates a research data archive dedicated to data deposits and access 13 33%
The library is involved with data archiving that is primarily operated by another department/group at our
institution
6 15%
[Editor’s note: After a further analysis of respondents’ answers and a review of archive websites, the survey authors assigned
these 40 responses to two categories: IRs with Data (35 respondents) and Data Archives (5 respondents). Those categories are
represented in questions 22 through 31 below.]
22. Which platform(s) and/or software are you using for your archiving solution (e.g., DSpace)? N=38
BePress Digital Commons (2 responses)
BePress Digital Commons, DuraCloud campus is investigating DSpace and Fedora Commons.
BePress Digital Commons. We are developing and will soon transition to a Fedora managed data repository that will
contain research data but many other kinds of data and objects as well.
Chronopolis
Custom repository built with open source tools including Python, Django, Soir, Lucene, Jquery, ubuntu, Celery,
PostgreSQL and WordPress.
DAITSS
Dataverse
Drupal
DSpace (11 responses)
DSpace (with a planned conversion to Hydra/Fedora)
DSpace (for the institutional repository), Dataverse (for an archive external to library)
DSpace, Dark Archive
DSpace, Dataverse
Fedora Commons (3 responses)
Fedora, Hydra (2 responses)
Fedora, iRODS to manage storage and preservation functions
DATA ARCHIVE CHARACTERISTICS
We would appreciate more details about the characteristics of your current research data archiving solution.
21. Please specify your library’s archiving solution. Check all that apply. N=40
Our institutional repository is used to archive research data (and used for text documents) 32 80%
The library hosts or is directly involved with archiving research data at an external archive or repository
service, such as DuraSpace or Dataverse
17 43%
The library operates a research data archive dedicated to data deposits and access 13 33%
The library is involved with data archiving that is primarily operated by another department/group at our
institution
6 15%
[Editor’s note: After a further analysis of respondents’ answers and a review of archive websites, the survey authors assigned
these 40 responses to two categories: IRs with Data (35 respondents) and Data Archives (5 respondents). Those categories are
represented in questions 22 through 31 below.]
22. Which platform(s) and/or software are you using for your archiving solution (e.g., DSpace)? N=38
BePress Digital Commons (2 responses)
BePress Digital Commons, DuraCloud campus is investigating DSpace and Fedora Commons.
BePress Digital Commons. We are developing and will soon transition to a Fedora managed data repository that will
contain research data but many other kinds of data and objects as well.
Chronopolis
Custom repository built with open source tools including Python, Django, Soir, Lucene, Jquery, ubuntu, Celery,
PostgreSQL and WordPress.
DAITSS
Dataverse
Drupal
DSpace (11 responses)
DSpace (with a planned conversion to Hydra/Fedora)
DSpace (for the institutional repository), Dataverse (for an archive external to library)
DSpace, Dark Archive
DSpace, Dataverse
Fedora Commons (3 responses)
Fedora, Hydra (2 responses)
Fedora, iRODS to manage storage and preservation functions
