ABCDEFGHIJKLMNOPQRSTUVWXYZAAABACADAEAFAGAH
1
ProgressDuration (in seconds)FinishedRecordedDateQ1.0Q1.1Q2S1S1_5_TEXTS2S3S4S5S6S7S8S9N1N1_7_TEXTN2N3N4N5N6N7N8P1P1_8_TEXTP2P3P4P4P5P6
2
ProgressDuration (in seconds)FinishedRecorded DateName of organization
Does your organization currently support/provide/develop research data repository services?
Does your organization currently use a Samvera application (Hyrax, Hyku, Avalon, Sufia, etc) for research data?
Which Samvera application do you currently use for research data? - Selected Choice
Which Samvera application do you currently use for research data? - other - Text
Is it local or a hosted service?Why did you choose the Samvera application over another solution?Which features in the Samvera application meet your institution's data repository needs?Which are the most important features for supporting data? (list your top three features)What features are currently missing in Hyrax/Hyku for the research data repository needs at your institution?Is there any other information you would like to share?
May we reach out to you if we have any follow up questions? If yes, please provide your email address.
Your email address
What application are you currently using or actively planning to use for research data? - Selected Choice
What application are you currently using or actively planning to use for research data? - Other - Text
Is it local or a hosted service?What are the features in your current application that meet your institution's research data needs?What features needed by your institution are currently missing or not yet developed in your research data application?If you considered adopting Samvera software for research data (Hyrax/Hyku) and chose not to, why not?Is there any other information you would like to share?
May we reach out to you if we have any follow up questions? If yes, please provide your email address.
Your email address
Which applications are you considering to use for research data? - Selected Choice
Which applications are you considering to use for research data? - Other - Text
What are the required features your organization has determined are needed for a research data repository?
Are there any other requirements aside from features that are part of your evaluation?
If you have not already adopted Samvera software for research data (Hyrax/Hyku), why not?Is there any other information you would like to share?
May we reach out to you if we have any follow up questions? If yes, please provide your email address.
Your email address
3
100319True9/12/2022 14:42:51Emory UniversityYesNoDataverseHostedSystem administration provided by hosting institution. DOIs provided for each dataset. Ability to customize our hosted instance. Shibboleth authentication integrated with our university identity management system.
Dashboard of usage statistics is quite limited. Further ability to customize the user interface for our institutional users. Embargo option for making datasets publicly accessible at a specific future date (our hosted instance is typically a few versions behind the latest software version).
Institutional support to develop is seriously limited by local resources.Yesjennifer.doty@emory.edu
4
100681True9/12/2022 16:21:04University of HullYesYesotherHydraLocalAs part of our adoption of the original Hydra code, we wished to ensure that we created a repository solution that could cater for many different types of content, including research data.
We designed our own repository based on the Hydra code, so there were no specific features. But we found the ability to display research datasets in their own specific way (incl. geo-referencing) and developing a specific research data model were particularly helpful.
Geo-referencing
Specific data model
Identifier management		It would be great to have ways of looking inside a dataset. Better options for showing the relationship between files (incl. past versions) will help navigation by researchers.
Having a way of looping research data through a preservation workflow will facilitate longer-term curation.
Yesc.awre@hull.ac.uk
5
100171True9/13/2022 5:48:05Qatar National LibraryYesNoFigShareHostedCustom review workflow for data submission.
Custom metadata schema.
DOI		More granular metadata
More customisable review and publishing workflow		Lack of expertise to support maintenance and developmentYesashaon@qnl.qa
6
10012938True9/13/2022 12:50:54Indiana UniversityYesYesHyraxLocalWe chose Samvera over other solutions because of the flexibility. It lets us tailor the repository to meet the unique needs of academic researchers and institutions.Allowing metadata flexibility to support a variety of data set types is important.
The main missing features in out-of-the-box Hyrax that would help support data are built-in DOI support, and integration with large-data storage. That's the part that we are missing which is why we are having to build it ourselves.

While the flexibility of building things ourselves is an advantage of Hyrax, with the limited resources of academic institutions some major features like this would help make institutional repositories a more sustainable endeavor.
Yesejfridma@iu.edu
7
100398True9/14/2022 7:43:17University of North Carolina at Chapel HillYesYesHyraxLocalWe are already using Samvera as our institutional repository and it was easy to integrate research data services into our existing repository.customizable worktype
I can customize the fields on the form to reflect data and they don't have to be the same as the other worktypes. I can also specify which fields are required, which don't have to be the same as other worktypes. Hyrax is capable of ingesting large files (although not via the form, which has been an issue for us)
A way to ingest large datasets. We are using bulkrax for this currently, but it is clunky, slow and chews up a lot of resources.Yesrkati@email.unc.edu
8
1002316True9/14/2022 11:22:51NorthwesternYesYesHyraxLocal
More to the story--we recently purchased a membership to Dryad because of limitations with Hyrax. We are not going to mediate whether someone adds a dataset to our Hyrax instance as we will still run it for publications, but will direct people to Dryad for larger filesets and the other integrations Dryad offers.
Hyrax allowed for unmediated deposits, Dryad offered mediation. Hyrax could accept up to 2GB files, Dryad accepts up to 10GB (300GB per data set). I have a document with a short list comparison if you want it (just contact Carolyn Caizzi).This is hard for me to answer organizationally. My own thinking: large file support; Deposit-level Views, downloads, and administrative reporting tools; rest API.large file support. deposit level usage stats. well documented rest api.Yescarolyn.caizzi@northwestern.edu
9
100895True9/14/2022 14:54:45University of VirginiaYesNoDataverseLocal
Mints DOIs or handles, Shibboleth login as well as ORCID, can deposit zipped files which are automatically unzipped and the directory structure is kept, conforms to DDI metadata schema (a dataset schema), integrated with github (github files can be automatically added to a Dataverse dataset), offers private and anonymous access (URLs) for non-published datasets. Other metadata schemas can be added easily. admins can easily create OAI-PMH harvesting sets, can deposit, edit records from either the UI or via API, has embargo - which automatically releases at set-date, has file previewers for text, tabular, image, audio, video, and geospatial files, supporst S3 or Swift cloud and users can choose between filesystem or object storage, configurable per collection and per dataset among others listed here: https://dataverse.org/software-features
Cannot apply licenses per file - licenses are per dataset which can contain files with different licenses (i.e., data & software)
Samvera software did not have any of the features a data repository needs (see my list of features in Dataverse). My institution does not have programmers or a staff to modify the Samvera software enough to make it useful for datasets. Not being able to modify the metadata scheme to fit datasets is a big problem.

Dataverse was easy plug-n-play after setting a few configurations. No customizations to the code is/was needed.
Yesshlake@virginia.edu
10
1001078True9/15/2022 8:20:43Virginia Tech University LibrariesYesNoOtherFigshare for institutions (maybe should be counted as figshare)HostedRepository capability/functionality: Effective UX/UI, API can help with preservation workflow, Integrates with VT Elements

Administrative: Curation Review, Usage tracking, Data Governance - we own the data, Support Needed - we have $$$, in-house support an issue

Use of this platform allows us to
- Take less time talking to our researchers about how to use the platform
More easily automate/improve preservation and curation workflows, including within the Data Curation Network
Keep up with the larger data repository landscape (e.g. integrations with other services like Gitlab)
Work with the figshare for institutions community in requesting enhancements and features, developing API code


- Improving the pushing of more repository metadata to DataCite
- Figshare's embargo functionality is ungood, would like it removed		When we were using Sufia back before 2019, it was highly customized and we could not maintain the in-house support necessary to keep it running well.

Additionally my impressions from my time at Samvera Connect (2018) was that research data archiving/sharing was not a central use case for the Samvera community. Which is fine! Applications can't be everything to everyone...focusing on the needs of in-house digital archivists is a reasonable scope		NoYesjpetters@vt.edu
11
1001036True9/15/2022 13:48:02University of CincinnatiYesYesHyraxLocalAt the time we implemented our repository (2013), Samvera was the better solution for us compared to Islandora.The preservation piece meets our needs. The ability to create new "heads" meets our needs. The blacklight interface meets our needs.version control
Customizable facets
Bulk import/export capabilities		The ability to upload and preserve the hierarchy of our research data.
ORCID integration: ability to import and export based on someone's ORCID
Ability to include/access external research data		Yesglen.horton@uc.edu
12
100950True9/16/2022 3:11:24Ruhr Universität Bochum (Germany)NoSamveraCore functions
Data ingest and mediation of data storage
Sharing and publishing data
Faceted search
Versioning and PID assignment
Metadata management
Connection to the local infrastructure (S3-compatible storage systems)
Role and rights management / Authorization management
Core properties
Adaptability to the research workflow
Modular design for expandability
Open standardized interfaces
Simple and low-threshold usability: requirements for screen design
 "FAIR Principles" and Recommendations on "Next Generation Repositories"
FOSS licenses and inclusion of as large an OS community as possible
Requirements for use of RDMS		The research data repository service is introduced with the current development.
We work with a service provider to design and develop the repository.
Yesjohannes.frenzel@ruhr-uni-bochum.de
13
079False9/16/2022 3:54:52No
14
743False9/16/2022 17:06:01No
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100