[](https://doi.org/10.5281/zenodo.7524314)
[](https://doi.org/10.1016/j.softx.2024.101736)
[](https://www.ricgraph.eu)
[](https://github.com/UtrechtUniversity/ricgraph/releases)
[](https://pypi.org/project/ricgraph)
[](https://pypistats.org/packages/ricgraph)
[](LICENSE)
[](https://www.repostatus.org/#active)
[](https://github.com/CLARIAH/clariah-plus/blob/main/requirements/software-metadata-requirements.md#15--you-should-express-a-technology-readiness-level)
[](https://fairsoftwarechecklist.net/v0.2?f=31&a=32113&i=32110&r=123)
<!---
Note, the lines 'Website' and
'PyPI downloads' end in two spaces, to force a line break but not a paragraph break.
--->
<img alt="Ricgraph logo" src="https://raw.githubusercontent.com/UtrechtUniversity/ricgraph/refs/heads/main/docs/images/ricgraph_logo.png" height="30">
# Ricgraph - Research in context graph
## What is Ricgraph?
Ricgraph, also known as Research in context graph, enables the exploration of researchers,
teams, their results,
collaborations, skills, projects, and the relations between these items.
Ricgraph can store many types of items into a single graph.
These items can be obtained from various systems and from
multiple organizations. Ricgraph facilitates reasoning about these
items because it infers new relations between items,
relations that are not present in any of the separate source systems.
It is flexible and extensible, and can be
adapted to new application areas.
### Motivation
Ricgraph, also known as Research in context graph, is software that is about
relations between items. These items can be collected from various source
systems and from multiple organizations. We
explain how Ricgraph works by applying it to the application area
*research information*. We show the insights that can be
obtained by combining information from various source systems,
insight arising from new relations that are not present
in each separate source system.
*Research information* is about anything related to research: research
results, the persons in a research team, their
collaborations, their skills, projects in which they have
participated, as well as the relations between these entities.
Examples of *research results* are publications, data sets, and software.
Example use cases from the application area research information are:
| Use case | In Ricgraph |
|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|
| As a journalist, I want to find researchers with a certain skill S and their publications, so that I can interview them for a newspaper article. Example skills can be: *climate change* or *stem cells*. | <img src="https://raw.githubusercontent.com/UtrechtUniversity/ricgraph/main/docs/images/journalist-use-case.jpg" width="700"> |
| As a librarian, I want to enrich my local research information system with research results from person A that are in other systems (in orange, *RIS2*) but not in ours (in green, *RIS1*), so that we have a more complete view of research at our university. | <img src="https://raw.githubusercontent.com/UtrechtUniversity/ricgraph/main/docs/images/librarian-use-case.jpg" width="700"> |
| As a researcher A, I want to find researchers from other universities that have co-authored publications written by the co-authors of my own publications, so that I can read their publications to find out if we share common research interests. | <img src="https://raw.githubusercontent.com/UtrechtUniversity/ricgraph/main/docs/images/researcher-use-case.jpg" width="700"> |
These use cases use different types of information (called *items*):
researchers, skills, publications,
etc. Most often, these types of information are not stored in
one system, so the use cases may be difficult or
time-consuming to answer. However, by using Ricgraph, these
use cases (and many others) are easy to answer, as will be
explained throughout this documentation.
Although this documentation illustrates Ricgraph in the application area
research information, the principle “relations
between items from various source systems” is general,
so Ricgraph can be used in other application areas.
### Main contributions of Ricgraph
* Ricgraph can store many types of items in a single graph.
* Ricgraph harvests multiple source systems into a single graph.
* Ricgraph Explorer is the exploration tool for Ricgraph.
* Ricgraph facilitates reasoning about items because it infers new relations between items.
* Ricgraph can be tailored for an application area.
### Read more about Ricgraph
For a gentle introduction in Ricgraph, read the reference publication:
Rik D.T. Janssen (2024). Ricgraph: A flexible and extensible graph to explore research in
context from various systems. *SoftwareX*, 26(101736).
https://doi.org/10.1016/j.softx.2024.101736.
You might also want to read the documentation in
the [Ricgraph GitHub repository](https://github.com/UtrechtUniversity/ricgraph).
To use Ricgraph, installing the [Ricgraph package from PyPI](https://pypi.org/project/ricgraph)
is not sufficient. Please read the
installation instructions in the Ricgraph GitHub repository.
Raw data
{
"_id": null,
"home_page": null,
"name": "ricgraph",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.9",
"maintainer_email": null,
"keywords": "Ricgraph, Ricgraph Explorer, Ricgraph REST API, Research in context graph, Graph, Graph database, Data harvesting, Data enrichment, Data linking, Linked data, Knowledge graph, Metadata, Utrecht University",
"author": "Rik D.T. Janssen",
"author_email": null,
"download_url": "https://files.pythonhosted.org/packages/9a/8c/4faa873231128982c289900caae09eaabbb4feea232eb60f2c9e42a82532/ricgraph-2.7.tar.gz",
"platform": null,
"description": "[](https://doi.org/10.5281/zenodo.7524314)\n[](https://doi.org/10.1016/j.softx.2024.101736)\n[](https://www.ricgraph.eu) \n\n[](https://github.com/UtrechtUniversity/ricgraph/releases)\n\n\n[](https://pypi.org/project/ricgraph)\n[](https://pypistats.org/packages/ricgraph) \n[](LICENSE)\n[](https://www.repostatus.org/#active)\n[](https://github.com/CLARIAH/clariah-plus/blob/main/requirements/software-metadata-requirements.md#15--you-should-express-a-technology-readiness-level)\n[](https://fairsoftwarechecklist.net/v0.2?f=31&a=32113&i=32110&r=123)\n<!---\nNote, the lines 'Website' and\n'PyPI downloads' end in two spaces, to force a line break but not a paragraph break.\n--->\n\n<img alt=\"Ricgraph logo\" src=\"https://raw.githubusercontent.com/UtrechtUniversity/ricgraph/refs/heads/main/docs/images/ricgraph_logo.png\" height=\"30\"> \n\n# Ricgraph - Research in context graph \n\n## What is Ricgraph?\n\nRicgraph, also known as Research in context graph, enables the exploration of researchers, \nteams, their results,\ncollaborations, skills, projects, and the relations between these items.\n\nRicgraph can store many types of items into a single graph. \nThese items can be obtained from various systems and from\nmultiple organizations. Ricgraph facilitates reasoning about these \nitems because it infers new relations between items,\nrelations that are not present in any of the separate source systems. \nIt is flexible and extensible, and can be\nadapted to new application areas.\n\n### Motivation\n\nRicgraph, also known as Research in context graph, is software that is about\nrelations between items. These items can be collected from various source \nsystems and from multiple organizations. We\nexplain how Ricgraph works by applying it to the application area \n*research information*. We show the insights that can be\nobtained by combining information from various source systems, \ninsight arising from new relations that are not present\nin each separate source system.\n\n*Research information* is about anything related to research: research \nresults, the persons in a research team, their\ncollaborations, their skills, projects in which they have \nparticipated, as well as the relations between these entities.\nExamples of *research results* are publications, data sets, and software.\n\nExample use cases from the application area research information are:\n\n| Use case | In Ricgraph |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|\n| As a journalist, I want to find researchers with a certain skill S and their publications, so that I can interview them for a newspaper article. Example skills can be: *climate change* or *stem cells*. | <img src=\"https://raw.githubusercontent.com/UtrechtUniversity/ricgraph/main/docs/images/journalist-use-case.jpg\" width=\"700\"> |\n| As a librarian, I want to enrich my local research information system with research results from person A that are in other systems (in orange, *RIS2*) but not in ours (in green, *RIS1*), so that we have a more complete view of research at our university. | <img src=\"https://raw.githubusercontent.com/UtrechtUniversity/ricgraph/main/docs/images/librarian-use-case.jpg\" width=\"700\"> |\n| As a researcher A, I want to find researchers from other universities that have co-authored publications written by the co-authors of my own publications, so that I can read their publications to find out if we share common research interests. | <img src=\"https://raw.githubusercontent.com/UtrechtUniversity/ricgraph/main/docs/images/researcher-use-case.jpg\" width=\"700\"> |\n\n\nThese use cases use different types of information (called *items*):\nresearchers, skills, publications,\netc. Most often, these types of information are not stored in \none system, so the use cases may be difficult or\ntime-consuming to answer. However, by using Ricgraph, these \nuse cases (and many others) are easy to answer, as will be\nexplained throughout this documentation.\n\nAlthough this documentation illustrates Ricgraph in the application area \nresearch information, the principle \u201crelations\nbetween items from various source systems\u201d is general, \nso Ricgraph can be used in other application areas.\n\n### Main contributions of Ricgraph\n\n* Ricgraph can store many types of items in a single graph.\n* Ricgraph harvests multiple source systems into a single graph.\n* Ricgraph Explorer is the exploration tool for Ricgraph.\n* Ricgraph facilitates reasoning about items because it infers new relations between items.\n* Ricgraph can be tailored for an application area.\n\n### Read more about Ricgraph\n\nFor a gentle introduction in Ricgraph, read the reference publication: \nRik D.T. Janssen (2024). Ricgraph: A flexible and extensible graph to explore research in\ncontext from various systems. *SoftwareX*, 26(101736).\nhttps://doi.org/10.1016/j.softx.2024.101736.\n\nYou might also want to read the documentation in \nthe [Ricgraph GitHub repository](https://github.com/UtrechtUniversity/ricgraph).\nTo use Ricgraph, installing the [Ricgraph package from PyPI](https://pypi.org/project/ricgraph) \nis not sufficient. Please read the\ninstallation instructions in the Ricgraph GitHub repository.\n",
"bugtrack_url": null,
"license": null,
"summary": "Ricgraph - Research in context graph",
"version": "2.7",
"project_urls": {
"Documentation": "https://github.com/UtrechtUniversity/ricgraph/blob/main/README.md",
"Download": "https://github.com/UtrechtUniversity/ricgraph/releases",
"GitHub": "https://github.com/UtrechtUniversity/ricgraph",
"Issues": "https://github.com/UtrechtUniversity/ricgraph/issues",
"Release Notes": "https://github.com/UtrechtUniversity/ricgraph/releases",
"Website": "https://www.ricgraph.eu"
},
"split_keywords": [
"ricgraph",
" ricgraph explorer",
" ricgraph rest api",
" research in context graph",
" graph",
" graph database",
" data harvesting",
" data enrichment",
" data linking",
" linked data",
" knowledge graph",
" metadata",
" utrecht university"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "52d928653907e25ced6c616efc0c21c8268c2a39a48a48c7c27a66345cea6817",
"md5": "ad16b76d90513a3ca4e1cfd3647cae35",
"sha256": "fff9374371201a9d0728bb76d651e62bb61eaa631018e478b5dcfbf8d71e6cc7"
},
"downloads": -1,
"filename": "ricgraph-2.7-py3-none-any.whl",
"has_sig": false,
"md5_digest": "ad16b76d90513a3ca4e1cfd3647cae35",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.9",
"size": 29456,
"upload_time": "2024-12-03T12:35:57",
"upload_time_iso_8601": "2024-12-03T12:35:57.139833Z",
"url": "https://files.pythonhosted.org/packages/52/d9/28653907e25ced6c616efc0c21c8268c2a39a48a48c7c27a66345cea6817/ricgraph-2.7-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "9a8c4faa873231128982c289900caae09eaabbb4feea232eb60f2c9e42a82532",
"md5": "7ac5517271a29c9b61558a0d3523fb96",
"sha256": "f7fd7da382fbf9ffb835a31e5aaf7e2b3efb6a88f11b7592d7e45f841d890c86"
},
"downloads": -1,
"filename": "ricgraph-2.7.tar.gz",
"has_sig": false,
"md5_digest": "7ac5517271a29c9b61558a0d3523fb96",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.9",
"size": 35758,
"upload_time": "2024-12-03T12:35:58",
"upload_time_iso_8601": "2024-12-03T12:35:58.825786Z",
"url": "https://files.pythonhosted.org/packages/9a/8c/4faa873231128982c289900caae09eaabbb4feea232eb60f2c9e42a82532/ricgraph-2.7.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-12-03 12:35:58",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "UtrechtUniversity",
"github_project": "ricgraph",
"travis_ci": false,
"coveralls": false,
"github_actions": false,
"requirements": [
{
"name": "build",
"specs": []
},
{
"name": "connexion",
"specs": []
},
{
"name": "flask",
"specs": []
},
{
"name": "gunicorn",
"specs": []
},
{
"name": "markupsafe",
"specs": []
},
{
"name": "neo4j",
"specs": [
[
">=",
"5.8"
]
]
},
{
"name": "numpy",
"specs": []
},
{
"name": "openapi_markdown",
"specs": []
},
{
"name": "pandas",
"specs": []
},
{
"name": "pyalex",
"specs": []
},
{
"name": "ratelimit",
"specs": []
},
{
"name": "requests",
"specs": []
},
{
"name": "ricgraph",
"specs": [
[
"==",
"2.7"
]
]
},
{
"name": "twine",
"specs": []
},
{
"name": "Sickle",
"specs": []
},
{
"name": "xmltodict",
"specs": []
}
],
"lcname": "ricgraph"
}
JSON
