Betty’s (Re) Search Engine

Detailed description of the service 

Service’s Capabilities:

Betty’s (Re) Search Engine performs a federated search to find research software repositories (e.g., on GitHub or GitLab), retrieves corresponding publications, and collects metadata related to these repositories. The engine links the software repositories to research publications or third-party databases using various APIs (e.g., Zenodo, OpenAlex, DataCite). It can also sort repositories based on user preferences such as the number of citations, and allows users to access enriched metadata about research software.

Added Value for the User:

The engine simplifies the task of finding research software related to a given search string, automating the process of linking software repositories to relevant publications. This saves users time and effort, making it easier to access comprehensive metadata, understand the context in which the software has been applied, and identify key research connected to the software. Additionally, it enables better evaluation and benchmarking of research tools.

Service’s Suitability:

The service is suitable for researchers, developers, and academic institutions looking to find software used in research publications. It also benefits those who need to evaluate research tools in specific domains or benchmark their own software against others.

Typical Use Cases:

  • A researcher searching for software used in their field to understand how it was applied in various studies.

  • A developer looking for open-source tools used in academic papers to integrate into their projects.

  • Research institutions aiming to assess the impact of certain software based on citation count and publication context.

Strengths of the Service:

  • Automatic linking of software repositories to research publications.

  • Enrichment of metadata for more informed decision-making.

  • Ability to sort repositories by key factors like citation count.

  • Focus on user privacy, with no centralized storage of credentials or search history.

Weaknesses of the Service:

  • Limited accuracy due to reliance on rule-based search, especially for unstructured references.

  • Lack of support for categorizing or benchmarking research software, which would require additional development.

Terms of use & restrictions

The user requires a GitHub account in order to use the research engine.

Contact 

Vasiliy Seibert, vasiliy.seibert@tu-clausthal.de

References

publications that reference (or report on using) the service

#WhyNFDI

 

Miscellaneous

 

Tags

NFDI4ING services may be relevant to different users according to varying requirements. To support filtering or sorting, we added a tag system outlining which archetype, phase of the data lifecycle, or degree of maturity a service corresponds to. By clicking on one of the tags below, you can get an overview of all services aligned with each tag.

This service has the following tags:

The tags correspond to:
The Archetypes: Services relevant to Alex – Bespoke Experiments, Betty – Research Software Engineering, Caden – Provenance Tracking, Doris – High Performance Computing, Ellen – Complex Systems, Fiona – Data Re-Use and Enrichment

The data lifecycle: Services related to Informing & Planning, Organising & Processing, Describing & Documenting, Storing & Computing,
Finding & Re-Using, Learning & Teaching

The maturity of the service: Services sorted according to their maturity and status of their integration into the larger NFDI service landscape. For this we use the Integration Readiness Level (IRL), ranging from IRL0 (no specifications, strictly internal use) up to IRL4 (fully integrated in the German research data landscape and the EOSC). Click here for a diagram outlining all Integration Readiness Levels.