2.0 - Ricgraph

The following improvements have been made to Ricgraph.

Structural change:

• Previously, Ricgraph used the Python module py2neo to connect with the graph database backend Neo4j. This module is end-of-life. Now, Ricgraph uses the Python module neo4j. This required many changes, including explicit Cypher calls in the code. This results in a faster Ricgraph, and it may be possible to use other graph database backends that use the same Python module (such as Memgraph or Avantgraph).

Ricgraph Explorer:

• Added a function that finds with which (sub-)organizations a person collaborates.
• Modifications to make Ricgraph Explorer run in a multi-user environment. This includes an Apache config file, and changes so that Ricgraph Explorer can be run as a Linux service, or using WSGI.

Ricgraph:

• Cleanup and optimization of code.
• Added a script to count the number of organizations that contributed to a category, so that you will be able to see which (sub-)organizations collaborate.
• Modifications to make Ricgraph run in a multi-user environment.
• A call to get_personroot_node() or get_all_personroot_nodes() now returns person-root nodes of any type of node.
• Previously, if a new node had a FULL_NAME that was already in Ricgraph, the new node was joined with the node already present. It appears that in case you harvest multiple source systems, this may not be a good idea: a person named J. Doe from source system 1 may be someone else than person J. Doe from source system 2. Thus, this is not done any more, unless you set RICGRAPH_NODEADD_MODE to something else than 'strict'.
• Modified initialization file by renaming a section, and adding and renaming graph database backend parameters.
• Removed function get_edges().

Harvest scripts:

• Added University Medical Center Utrecht to the list of nodes to rename in the batch harvest script batch_harvest.py.

Documentation:

• Added the reference publication: Rik D.T. Janssen, Ricgraph: A Flexible and Extensible Graph to Explore Research in Context from Various Systems. January 2024. Submitted to SoftwareX. https://doi.org/10.2139/ssrn.4712466.
• Added use cases as in the reference publication.
• Added documentation for Ricgraph Explorer.
• Added documentation how to run Ricgraph and Ricgraph Explorer in a multi-user environment. Please read Ricgraph as a server on Linux.
• Added a Ricgraph presentation and a table where Ricgraph has been used.
• Added an explation how to dump data in Neo4j Desktop and use it in Neo4j Community Edition.
• Reorganized the documentation structure.
• Updated badges in README.md file.
• And many other improvements and clarifications to the documentation.

GitHub:

• The default branch name of Ricgraph in GitHub has been renamed from master to main.

Upgrading:

• If you upgrade from any Ricgraph version, you will need to re-install Ricgraph, re-create your Ricgraph initialization file, and reharvest your sources. This is due to the many changes.

1.14 - Ricgraph

The following improvements have been made to Ricgraph.

Ricgraph Explorer:

• The option to get more information about persons or their results in an organization is much faster.
• The option to find persons that share research output types with another person is faster.
• Removed the option to find overlap in source systems for an organization.
• Added a transparant favicon.

If you upgrade from Ricgraph v1.13, you do not need to reharvest your sources. If you upgrade from Ricgraph v1.11 or earlier, you do need to reharvest your sources.

1.13 - Ricgraph

The following improvements have been made to Ricgraph.

Ricgraph Explorer:

• Full rewrite of the code, to make the structure easier to understand and the code easier to extend.
• User experience improvements, such as a new flow through the application, buttons with predefined search queries, and dropdown lists for various input fields.
• Added a cache for nodes.
• Statistics such as the names of the harvested systems, number of nodes and edges, and use of the node cache.
• Speed improvements.

Ricgraph:

• Minor changes related to the rewrite of Ricgraph Explorer.

If you upgrade from Ricgraph v1.12, you do not need to reharvest your sources. If you upgrade from Ricgraph v1.11 or earlier, you do need to reharvest your sources.

1.12 - Ricgraph

The following improvements have been made to Ricgraph.

Ricgraph Explorer:

• User experience improvements.
• Speed improvements

Ricgraph:

• The FULL_NAME of nodes is cached in the comment field of its person-root node.
• Limit the number of organization nodes to return in filterorganization() for improvement of speed.
• Changed the object identifier of nodes from RCGNode to RicgraphNode.

Harvest scripts:

• In case a person is part of multiple (child) organizations (such as university, faculty, department, unit), this person will be connected to all of these (child) organizations.
• Pure harvesting: more author names will be added to Ricgraph: the not active persons, the external persons and the author collaborations.
• Pure harvesting: projects without identifiers will be harvested.
• Pure harvesting: projects are connected to all of their parent organizations.

Documentation:

• Added Ricgraph abstract, presentation and video at Pure International Conference 2023 in Dubrovik, Croatia.
• Added several badges in README.md.
• Added metadata for the Clariah tools website, and for other sites that obtain their metadata from the Clariah tools website.

If you upgrade from Ricgraph v1.11 or earlier, you need to reharvest your sources.

1.11 - Ricgraph

The following improvements have been made to Ricgraph.

Ricgraph explorer:

• Now you can find information about persons or their results in a (child) organization (unit, department, faculty, university). For example, you can find out what data sets or software are produced in your faculty. Or the skills of all persons in your department. Of course this is only possible in case you have harvested them.
• Also, you can find out with whom a person shares research output types. For example, you can find out with whom someone shares software or data sets.
• You can get tables showing how you can enrich a source system based on other systems you have harvested. For example, suppose you have harvested both Pure and OpenAlex, using this feature you can find out which publications in OpenAlex are not in Pure. You might want to add those to Pure.
• The search page has been restructured and improved.
• All pages use the URL parameter/value mechanism (i.e. similar to hostname/webpage/?parameter1=value1&parameter2=value2).

Ricgraph:

• The functions get_all_neighbor_nodes() and get_all_neighbor_nodes_person() now have an optional parameter limiting the number of neighbor nodes to return. This is used for a speedup of Ricgraph explorer.

If you upgrade from Ricgraph v1.10, you do not need to reharvest your sources.

1.10 - Ricgraph

The following improvements have been made to Ricgraph.

Ricgraph explorer:

• If you have harvested from more than one source, it may be possible that a record which you've harvested from system 2 (say, ORCID 1234 for Alice), may already be in Ricgraph because it was also present in system 1. This is perfectly fine behaviour. This ORCID record will not be inserted twice, because it is already present. The only modification will be that system 2 is added to the _source list of the ORCID record of Alice. In this new release, Ricgraph explorer has an option to create a table that shows the overlap in harvests from different source systems. You do a query in Ricgraph (e.g. show all ORCID nodes), and then you choose to show a table that summarizes the number of ORCID nodes which were only found in one source, and which were found in multiple sources. Another table gives a detailed overview how many nodes originate from which different source systems. Then, you can drill down by clicking on a number in one of these two tables to find the nodes corresponding to that number. In the example ORCID node of Alice, the first table will tell you that there is 1 node found in multiple sources, and the second table will tell you that this node originated from system 1 and system 2 by showing a "1" in row and column representing these systems. Another use of this table is that you e.g. find Alices node, and then the tables will show which of the nodes connected to Alice (e.g. her journal articles or software packages) are unique to only one source system, and which nodes originate from multiple sources.

Ricgraph:

• Now there are global research output type names defined in ricgraph.py, such als journal article or software. Each harvest script has a mapping table that translates the name used in that source (e.g. article) to the name which is used in Ricgraph (journal article). The advantage of this is that there is one place where all research output type names are defined, and that there is only one way how they show up in Ricgraph.

Harvest scripts:

• Modifications for the mapping table for research output type names.
• For organizations, now their names are used for the value field, so you can search for an organization name. Previously, Ricgraph used identifiers, such as local Pure UUIDs or RORs. Although the latter might be preferred, I changed this because there do not seem to be generally used organization identifiers yet for sub organizations (for e.g. faculties or departments of a university).
• Pure harvesting: suppose Alice works for University X, Faculty Y, and Department Z. Previously this hierarchy was represented in Ricgraph. Now, each of the (sub) organizations a person works for, are directly connected to the person-root node of this person. In the example with Alice, the node for University X is connected to the person-root node of Alice, as are the nodes for Faculty Y and Department Z. This has the advantage that you are able to select e.g. University X, and find the persons working for this university, or that you can select e.g. Faculty Y, and find the persons involved with that faculty, etc.
• Pure harvesting: if a person works for multiple (sub) organizations, this person will be connected to all of these (sub) organizations. Previously a person was only connected to one (sub) organization.
• The batch harvesting script batch_harvest.py now has some error checking. Also, you can have this script modify your graph specific for your organization. For example, for Utrecht University, in the Pure harvest we find organization name University: Universiteit Utrecht, while this same organization is called Utrecht University in OpenAlex. In the batch script we change the name from the former to the latter, so that records harvested from OpenAlex will be mapped to the same organization as records harvested from Pure. This ensures a more concise graph.

1.9 - Ricgraph

The following improvements have been made to Ricgraph.

Harvest to Ricgraph:

• Harvesting of OpenAlex has been modified because OpenAlex changed some of their "type"s of their Works. E.g. there used to be a type "journal-article" but this has been renamed to "article".
• Harvesting of photos of the Utrecht University staff pages has been made more robust.

Ricgraph explorer:

• Modifications to implement the more robust way of harvesting photos from the Utrecht University staff pages.

If you use this release to update your version of Ricgraph, you will need to reharvest your sources. That means that you will need to empty Ricgraph. Sometimes, Python throws an error. If so, please go to error while empying Ricgraph how to repair that.

1.8 - Ricgraph

The following improvements have been made to Ricgraph.

Ricgraph explorer:

• There are two methods for exploring Ricgraph: (1) find your first node by using exact match, or (2) find your first node by using search on a field value.
• There are two methods for viewing the results: (1) a person_view: only show relevant columns, research outputs will be presented in a tabbed format, or (2) a details_view: show all columns, research outputs will be presented in a table with facets.

Ricgraph:

• Several modifications to implement the changes in Ricgraph explorer.

Documentation:

• The images of the graphs have been modified. Now they show what type of object a node it is (by having a special icon for article, data set, etc.) and from which system it was harvested (by having a specific color).

1.7 - Ricgraph

The following improvements have been made to Ricgraph.

Ricgraph, Pure harvesting script:

• The Pure harvesting script can now harvest projects from Pure, if your Pure uses them. Use the parameter "--harvest_projects". Read more about Pure harvesting and the use of this parameter.
• Pure has two APIs, a READ and a CRUD API. Previously, you could only use the READ API. Now you can use both. Read more about their advantages and their disadvantages. The author would recommend to use the Pure READ API.

Documentation:

• Added "mentions", those are places where Ricgraph is mentioned, as well as presentations about Ricgraph. Read more about these mentions.

1.6 - Ricgraph

The following improvements have been made to Ricgraph.

Ricgraph:

• Added a parameter "--organization" to some harvest scripts, so that they can be used for harvesting data from different organizations.
• Added a parameter "--empty_ricgraph" to the harvest scripts, to indicate whether Ricgraph should be emptied or not.
• Modified the initialization file ricgraph.ini-sample. You will need to copy this file to ricgraph.ini and fill in your own (organization) values. Some keys have an "organization abbreviation", which can be passed to the parameter "--organization" of a harvest script, or which can be filled in when running a script.
• Added a batch script to to run a number of harvest scripts after each other.

Documentation:

• Added a comparison of Ricgraph to other systems, such as Lens, OpenAire Graph and OpenAlex.
• Modified documentation to explain how to harvest data from different organizations.