[REVIEW]: Raphtory: The temporal graph engine for Rust and Python

[editorialbot]

Submitting author: !--author-handle-->@narnolddd<!--end-author-handle-- (Naomi Arnold) Repository: https://github.com/Pometry/Raphtory Branch with paper.md (empty if default branch): paper Version: 0.7.0 Editor: !--editor-->@luizirber<!--end-editor-- Reviewers: @abhishektiwari, @arashbm Archive: 10.5281/zenodo.10530613

Status

Status badge code:

HTML: <a href="https://joss.theoj.org/papers/1fbaaa72bc711cee778c7eca04530286"><img src="https://joss.theoj.org/papers/1fbaaa72bc711cee778c7eca04530286/status.svg"></a>
Markdown: [![status](https://joss.theoj.org/papers/1fbaaa72bc711cee778c7eca04530286/status.svg)](https://joss.theoj.org/papers/1fbaaa72bc711cee778c7eca04530286)

Reviewers and authors:

Please avoid lengthy details of difficulties in the review thread. Instead, please create a new issue in the target repository and link to those issues (especially acceptance-blockers) by leaving comments in the review thread below. (For completists: if the target issue tracker is also on GitHub, linking the review thread in the issue or vice versa will create corresponding breadcrumb trails in the link target.)

Reviewer instructions & questions

@abhishektiwari & @arashbm, your review will be checklist based. Each of you will have a separate checklist that you should update when carrying out your review. First of all you need to run this command in a separate comment to create the checklist:

@editorialbot generate my checklist

The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @luizirber know.

✨ Please start on your review when you are able, and be sure to complete your review in the next six weeks, at the very latest ✨

Checklists

📝 Checklist for @arashbm

📝 Checklist for @abhishektiwari

[editorialbot]

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1137/19M1242252 is OK
- 10.1145/1852658.1852661 is OK
- 10.1209/0295-5075/81/48002 is OK
- 10.1103/physrevlett.110.198701 is OK
- 10.1016/j.future.2019.08.022 is OK
- 10.48550/arXiv.2303.11181 is OK
- 10.1016/j.softx.2022.101301 is OK
- 10.1145/3442442.3452052 is OK
- 10.5281/zenodo.7682609 is OK
- 10.6084/m9.figshare.1164194.v14 is OK
- 10.1103/PhysRevE.85.056115 is OK
- 10.1073/pnas.0903215107 is OK
- 10.1063/1.2711640 is OK
- 10.1145/3159652.3159706 is OK
- 10.1038/srep00397 is OK
- 10.1214/18-aoas1176 is OK
- 10.1073/pnas.0800332105 is OK
- 10.1038/s41567-019-0459-y is OK
- 10.1093/oso/9780198805090.001.0001 is OK
- 10.1007/978-3-642-36461-7 is OK
- 10.1142/q0033 is OK
- 10.1145/3479591 is OK
- 10.1145/3018661.3018731 is OK
- 10.1145/3093742.3093913 is OK
- 10.5281/zenodo.8009585 is OK
- 10.1101/2021.03.26.437187 is OK
- 10.21105/joss.05872 is OK

MISSING DOIs

- No DOI given, and none found for title: Centralities in complex networks
- No DOI given, and none found for title: Dynamic network analysis in Julia
- No DOI given, and none found for title: Exploring network structure, dynamics, and functio...
- No DOI given, and none found for title: RecallGraph

INVALID DOIs

- None

[editorialbot]

:wave: @openjournals/dsais-eics, this paper is ready to be accepted and published.

Check final proof :point_right::page_facing_up: Download article

If the paper PDF and the deposit XML files look good in https://github.com/openjournals/joss-papers/pull/5184, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept

[arfon]

@editorialbot accept

[editorialbot]

Doing it live! Attempting automated processing of paper acceptance...

[editorialbot]

Ensure proper citation by uploading a plain text CITATION.cff file to the default branch of your repository.

If using GitHub, a Cite this repository menu will appear in the About section, containing both APA and BibTeX formats. When exported to Zotero using a browser plugin, Zotero will automatically create an entry using the information contained in the .cff file.

You can copy the contents for your CITATION.cff file here:

CITATION.cff

``` cff-version: "1.2.0" authors: - family-names: Steer given-names: Ben orcid: "https://orcid.org/0000-0001-9446-5690" - family-names: Arnold given-names: Naomi A. orcid: "https://orcid.org/0000-0001-6396-4788" - family-names: Ba given-names: Cheick Tidiane orcid: "https://orcid.org/0000-0002-4035-7464" - family-names: Lambiotte given-names: Renaud orcid: "https://orcid.org/0000-0002-0583-4595" - family-names: Yousaf given-names: Haaroon orcid: "https://orcid.org/0000-0001-5098-5811" - family-names: Jeub given-names: Lucas orcid: "https://orcid.org/0000-0001-8941-9227" - family-names: Murariu given-names: Fabian - family-names: Kapoor given-names: Shivam - family-names: Rico given-names: Pedro orcid: "https://orcid.org/0000-0002-4698-8435" - family-names: Chan given-names: Rachel - family-names: Chan given-names: Louis - family-names: Alford given-names: James - family-names: Clegg given-names: Richard G. orcid: "https://orcid.org/0000-0001-7241-6679" - family-names: Cuadrado given-names: Felix orcid: "https://orcid.org/0000-0002-5745-1609" - family-names: Barnes given-names: Matthew Russell - family-names: Zhong given-names: Peijie - family-names: Pougué-Biyong given-names: John orcid: "https://orcid.org/0000-0002-6582-193X" - family-names: Alnaimi given-names: Alhamza contact: - family-names: Arnold given-names: Naomi A. orcid: "https://orcid.org/0000-0001-6396-4788" doi: 10.5281/zenodo.10530613 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Steer given-names: Ben orcid: "https://orcid.org/0000-0001-9446-5690" - family-names: Arnold given-names: Naomi A. orcid: "https://orcid.org/0000-0001-6396-4788" - family-names: Ba given-names: Cheick Tidiane orcid: "https://orcid.org/0000-0002-4035-7464" - family-names: Lambiotte given-names: Renaud orcid: "https://orcid.org/0000-0002-0583-4595" - family-names: Yousaf given-names: Haaroon orcid: "https://orcid.org/0000-0001-5098-5811" - family-names: Jeub given-names: Lucas orcid: "https://orcid.org/0000-0001-8941-9227" - family-names: Murariu given-names: Fabian - family-names: Kapoor given-names: Shivam - family-names: Rico given-names: Pedro orcid: "https://orcid.org/0000-0002-4698-8435" - family-names: Chan given-names: Rachel - family-names: Chan given-names: Louis - family-names: Alford given-names: James - family-names: Clegg given-names: Richard G. orcid: "https://orcid.org/0000-0001-7241-6679" - family-names: Cuadrado given-names: Felix orcid: "https://orcid.org/0000-0002-5745-1609" - family-names: Barnes given-names: Matthew Russell - family-names: Zhong given-names: Peijie - family-names: Pougué-Biyong given-names: John orcid: "https://orcid.org/0000-0002-6582-193X" - family-names: Alnaimi given-names: Alhamza date-published: 2024-03-27 doi: 10.21105/joss.05940 issn: 2475-9066 issue: 95 journal: Journal of Open Source Software publisher: name: Open Journals start: 5940 title: "Raphtory: The temporal graph engine for Rust and Python" type: article url: "https://joss.theoj.org/papers/10.21105/joss.05940" volume: 9 title: "Raphtory: The temporal graph engine for Rust and Python" ```

If the repository is not hosted on GitHub, a .cff file can still be uploaded to set your preferred citation. Users will be able to manually copy and paste the citation.

Find more information on .cff files here and here.

[editorialbot]

🐘🐘🐘 👉 Toot for this paper 👈 🐘🐘🐘

[editorialbot]

🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨

Here's what you must now do:

0. Check final PDF and Crossref metadata that was deposited :point_right: https://github.com/openjournals/joss-papers/pull/5185
1. Wait five minutes, then verify that the paper DOI resolves https://doi.org/10.21105/joss.05940
2. If everything looks good, then close this review issue.
3. Party like you just published a paper! 🎉🌈🦄💃👻🤘

Any issues? Notify your editorial technical team...

[narnolddd]

Yay, thank you @arfon and @luizirber very much! And thanks again to @arashbm and @abhishektiwari for the really helpful reviews! 🥳

[arfon]

@abhishektiwari, @arashbm – many thanks for your reviews here and to @luizirber for editing this submission! JOSS relies upon the volunteer effort of people like you and we simply wouldn't be able to do this without you ✨

@narnolddd – your paper is now accepted and published in JOSS :zap::rocket::boom:

[editorialbot]

:tada::tada::tada: Congratulations on your paper acceptance! :tada::tada::tada:

If you would like to include a link to your paper from your README use the following code snippets:

Markdown:
[![DOI](https://joss.theoj.org/papers/10.21105/joss.05940/status.svg)](https://doi.org/10.21105/joss.05940)

HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.05940">
  <img src="https://joss.theoj.org/papers/10.21105/joss.05940/status.svg" alt="DOI badge" >
</a>

reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.05940/status.svg
   :target: https://doi.org/10.21105/joss.05940

This is how it will look in your documentation:

We need your help!

The Journal of Open Source Software is a community-run journal and relies upon volunteer effort. If you'd like to support us please consider doing either one (or both) of the the following:

• Volunteering to review for us sometime in the future. You can add your name to the reviewer list here: https://reviewers.joss.theoj.org/join
• Making a small donation to support our running costs here: https://numfocus.org/donate-to-joss