https://github.com/ctwhome/research-software-directory
The Research Software Directory is a content management system that is tailored to software.
Science Score: 23.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
○codemeta.json file
-
○.zenodo.json file
-
✓DOI references
Found 3 DOI reference(s) in README -
✓Academic publication links
Links to: zenodo.org -
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (9.7%) to scientific vocabulary
Last synced: 9 months ago
·
JSON representation
Repository
The Research Software Directory is a content management system that is tailored to software.
Basic Info
- Host: GitHub
- Owner: ctwhome
- License: apache-2.0
- Default Branch: master
- Homepage: https://research-software.nl
- Size: 151 MB
Statistics
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
- Releases: 0
Fork of research-software-directory/research-software-directory
Created about 5 years ago
· Last pushed over 5 years ago
https://github.com/ctwhome/research-software-directory/blob/master/
[](https://www.research-software.nl/software/research-software-directory)
[](https://doi.org/10.5281/zenodo.1154130)
[](https://github.com/research-software-directory/research-software-directory/actions?query=workflow%3A%22Admin+tests%22)
[](https://github.com/research-software-directory/research-software-directory/actions?query=workflow%3A%22Frontend+tests%22)
[](https://github.com/research-software-directory/research-software-directory/actions?query=workflow%3A%22Backend+tests%22)
[](https://github.com/research-software-directory/research-software-directory/actions?query=workflow%3A%22Integration+tests%22)
[](https://github.com/research-software-directory/research-software-directory/actions?query=workflow%3A%22Check+Markdown+links%22)
# Research Software Directory
## What is it?
The Research Software Directory is a content management system that is tailored to research software.
The idea is that institutes for whom research software is an important output, can run their own instance of the Research Software Directory. The system is designed to be flexible enough to allow for different data sources, database schemas, and so on. By default, the Research Software Directory is set up to collect data from GitHub, Zenodo, Zotero, as well as Medium blogs.
For each software package, a _product page_ can be created on the Research Software Directory if the software is deemed useful to others.
## What the Research Software Directory can do for you
The Research Software Directory:
1. presents software packages alongside the context necessary for visitors to understand how the software can help them
1. makes scientific impact of research software visible in a qualitative way
1. provides automatically generated citation metadata in a variety of reference manager file formats, for easy citation
1. improves findability of software packages by applying Search Engine Optimization techniques such as schema.org metadata. This helps search engines understand what a given software package is about, thus improving ranking of search results
1. provides aggregated insights through a metrics dashboard, helping to make more accurate and more timely business decisions
1. provides metadata about its software packages via [OAI-PMH](https://www.openarchives.org/pmh/), the standard protocol for metadata harvesting. Digital libraries and other services can use this feature to automatically update their records with data about the software packages published in the Research Software Directory.
1. provides all of its data via a JSON API
1. integrates with third-party services such as [Zotero](http://zotero.org/) (reference manager), [Zenodo](https://zenodo.org/) (archiving), GitHub (code development platform)
## Examples
1. [https://research-software.nl](https://research-software.nl)
1. [https://software.process-project.eu](https://software.process-project.eu)
## Try it out
### Requirements
1. You'll need a minimum of about 3 GB free disk space to
store the images, containers and volumes that we will be making.
1. Linux OS (we use Ubuntu 18.04)
1. [docker](https://docs.docker.com/install/) (v19.03 or later)
1. [docker-compose](https://docs.docker.com/compose/install/) (v1.26 or later)
1. [git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) (v2.21 or later)
### Instructions
To quickly get a running Research Software Directory up and running on your local machine do the following
1. Fork this repo to your own GitHub organization or GitHub profile and clone it
1. Start the complete stack using
```shell
cp rsd-secrets.env.example .env
docker-compose build
docker-compose up
```
Go to [http://localhost](http://localhost) (disregard certificate warning) to see the Research Software Directory
website. You should be able to see all non-authenticated pages, but editing data or harvesting data from external
sources won't work. To bring up the website with all bells and whistles, refer to selected resources from the list
below.
## Further resources
1. [Entering data about your software in an existing instance](./docs/entering-data.md)
1. [Configuring your instance to use your own data sources](./docs/configuring-your-instance-to-use-your-own-data-sources.md)
1. [Changing the look and feel](./docs/changing-the-look-and-feel.md)
1. [Hosting your instance online](./docs/hosting.md)
1. [Running an instance of the Research Software Directory in production](./docs/production.md)
1. [Finding your way: Research Software Directory services](./docs/services-overview.md)
1. [Documentation for developers](./docs/documentation-for-developers.md)
1. [Documentation for maintainers](./docs/documentation-for-maintainers.md)
1. [Security concerns](./docs/security.md)
1. [Contributing](./.github/CONTRIBUTING.md)
Owner
- Name: Jesse Gonzalez
- Login: ctwhome
- Kind: user
- Location: Amsterdam (Netherlands)
- Company: Netherlands eScience Center
- Website: https://www.ctwhome.com
- Twitter: ctwhome
- Repositories: 130
- Profile: https://github.com/ctwhome
Research Engineer at @NLeSC