-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathfind.software.bib
More file actions
74 lines (70 loc) · 7.1 KB
/
find.software.bib
File metadata and controls
74 lines (70 loc) · 7.1 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
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
@article{gey2025find,
author = {Ronny Gey and Daniel Mietchen and Oliver Karras and Tim Wittenborg and Moritz Schubotz and Jan Bumberger},
title = {find.software: Foundations for Interdisciplinary Discovery of (Research) Software},
volume = {11},
number = {},
year = {2025},
doi = {10.3897/rio.11.e179253},
publisher = {Pensoft Publishers},
abstract = {Across essentially all fields of research, many aspects of the respective research processes – whether experimental, theoretical, empirical or outright computational – are closely related to software. Yet the process of finding software that is directly suitable or at least a good starting point for a given research task is cumbersome.This project aims to develop a community-driven system that provides potential users of research software with a diversity of pathways towards actually finding software that closely matches their research needs if such software exists. Conversely, it will provide software developers with mechanisms to make their software findable for research-related tasks and it will highlight mismatches between software supply and demand for specific tasks.To this end, we will document how various stakeholders of the research landscape have been searching for – or stumbling upon – research software so far, identify variables associated with successful search outcomes and build workflows that assist in describing software and associated concepts in a standardised fashion. These descriptions will then be aligned across various sources of relevant information and integrated into Wikidata, the knowledge graph that anyone can edit and that already contains considerable breadth and depth of information related to research, software and their interactions.While keeping an eye on similar approaches to software discovery that might work in parts of the research ecosystem, existing Wikidata content and workflows will be reviewed and built upon. Additional documentation, tooling and workflows will be developed to enrich, expand, curate, query and explore this content, both for specific use cases and with ongoing engagement of the communities involved in research software, open data or collaborative curation. Within its three years, the project seeks to establish a dedicated community overseeing a well-documented and smoothly running infrastructure for software discovery and to devise a plan for how this can be sustained for the longer term.},
issn = {},
pages = {e179253},
URL = {https://doi.org/10.3897/rio.11.e179253},
eprint = {https://doi.org/10.3897/rio.11.e179253},
journal = {Research Ideas and Outcomes}
}
@misc{gey2026,
author = {Gey, Ronny and
Mietchen, Daniel and
Karras, Oliver and
Satpute, Ankit},
title = {find.software: Foundations for Interdisciplinary
Discovery of (Research) Software
},
month = mar,
year = 2026,
publisher = {Zenodo},
version = {1.0},
doi = {10.5281/zenodo.18756364},
url = {https://doi.org/10.5281/zenodo.18756364},
}
@techreport{wittenborg2025,
title = {Research {{Software Discovery}}: {{How}} Do We {{Want}} to {{Search Research Software}} and {{Where}} Do We {{Want}} to {{Find}} It?: {{A deRSE25}} Workshop Report},
shorttitle = {Research {{Software Discovery}}},
author = {Wittenborg, Tim and Gey, Ronny and Karras, Oliver and Mietchen, Daniel and Struck, Alexander},
year = {2025},
month = may,
institution = {Zenodo},
doi = {10.5281/ZENODO.14878664},
url = {https://zenodo.org/doi/10.5281/zenodo.14878664},
abstract = {The workshop aimed to identify current challenges in research software discovery and propose actionable improvements. Using a World Caf{\textasciiacute}e discussion format, participants explored topics such as the effectiveness of current discovery systems, metadata classification, hosting infrastructures, and AI integration. The workshop generated concrete recommendations for enhancing~research software discovery, benefiting developers, researchers, and institutions.},
copyright = {Creative Commons Attribution 4.0 International},
langid = {english},
keywords = {Discovery,Research Software}
}
@misc{gey2025,
title = {Seek and {{You Shall Find}} - {{Or Not}}! {{Why Can}}'t {{We Find}} the {{Research Software We Really Need}}?},
author = {Gey, Ronny and Wittenborg, Tim and Mietchen, Daniel and Struck, Alexander and Karras, Oliver},
year = {2025},
month = feb,
publisher = {Zenodo},
doi = {10.5281/ZENODO.14878607},
url = {https://zenodo.org/doi/10.5281/zenodo.14878607},
abstract = {Software discovery is a crucial aspect of research, yet it remains a challenging process due to various reasons: The lack of a centralized or domain-tailored search and publication infrastructure, insufficient software citations, the prevailing unavailability of software (versions) and many others. Researchers tend to utilize general search engines and their social network before considering code repositories, (text + data) repositories, and package management platforms, among other locations, to find the software they need. The resulting fragmented ecosystem is characterized by parallel developments from different, yet partially overlapping, redundant and non-interoperable infrastructure providers and research communities. Moreover, the discovery process is further complicated by missing or imperfect metadata, which can lead to limited search results. To address these challenges, it is essential to gain a deeper understanding of the different software publication and discovery systems. We describe available discovery options, including code and publication repositories, domain, geographic, or institution-specific catalogs, classical search engines, curated lists, knowledge graphs, social networks, and all of these in various combinations, with and without the use of artificial intelligence. Besides characterizing each option, we will present examples, challenges and recommendations for an improved software discovery process. In addition, we will discuss the role of different stakeholders (e.g. developers, users, funders, publishers) and what they could do for better findability.},
copyright = {Creative Commons Attribution 4.0 International},
langid = {english},
keywords = {deRSE25,Research Software Discovery,Research Software Engineering}
}
@misc{struck2025,
title = {Review of Discovery Pathways for Research Software Discovery},
author = {Struck, Alexander and Wittenborg, Tim and Gey, Ronny},
year = {2025},
month = may,
publisher = {Zenodo},
doi = {10.5281/ZENODO.15430737},
url = {https://zenodo.org/doi/10.5281/zenodo.15430737},
abstract = {We analysed discovery pathways for research software discovery, e.g. code repositories, software repositories, catalogs, knowledge graphs, curated lists, search engines or software archives. We used criteria related to content, search functionality, organisational and technological aspects of the pathway and the options for item evaluation.},
copyright = {Creative Commons Attribution Share Alike 4.0 International},
langid = {english},
keywords = {Knowledge Discovery,Research Software}
}