[REVIEW]: Cost-Effective Big Data Orchestration Using Dagster: A Multi-Platform Approach

[editorialbot]

Submitting author: @HPicatto (Hernan Picatto)
Repository: https://github.com/ascii-supply-networks/ascii-hydra
Branch with paper.md (empty if default branch): main
Version: v1.0.0
Editor: @HaoZeke
Reviewers: @abhishektiwari, @Midnighter
Archive: Pending

Status

Status badge code:

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

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 & @Midnighter, 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 @HaoZeke 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 @Midnighter

📝 Checklist for @abhishektiwari

[editorialbot]

Hello humans, I'm @editorialbot, a robot that can help you with some common editorial tasks.

For a list of things I can do to help you, just type:

@editorialbot commands

For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:

@editorialbot generate pdf

[editorialbot]

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

✅ OK DOIs

- 10.1016/j.future.2023.12.026 is OK
- 10.1145/2934664 is OK
- 10.1145/3472883.3486982 is OK
- 10.1145/3514221.3526054 is OK
- 10.1007/s11192-020-03726-9 is OK
- 10.5281/zenodo.7196590 is OK

🟡 SKIP DOIs

- No DOI given, and none found for title: Dagster | Cloud-native Orchestration of Data Pipel...
- No DOI given, and none found for title: Cost efficient alternative to databricks lock-in

❌ MISSING DOIs

- None

❌ INVALID DOIs

- None

[editorialbot]

Software report:

github.com/AlDanial/cloc v 1.98  T=0.04 s (981.6 files/s, 133751.5 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
Python                          27            523            342           3383
Text                             1            121              0            553
Markdown                         5            133              0            463
TOML                             4             27              1            124
TeX                              1              1              0            103
make                             1              6             21             51
JSON                             4              0              0              7
-------------------------------------------------------------------------------
SUM:                            43            811            364           4684
-------------------------------------------------------------------------------

Commit count by author:

    27	geoHeil
    10	Georg Heiler
     9	HPicatto
     5	CI Hotfix
     2	Hernan

[editorialbot]

Paper file info:

📄 Wordcount for paper.md is 1300

✅ The paper includes a Statement of need section

[editorialbot]

License info:

🟡 License found: GNU General Public License v3.0 (Check here for OSI approval)

[editorialbot]

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

[Midnighter]

Review checklist for @Midnighter

Conflict of interest

• I confirm that I have read the JOSS conflict of interest (COI) policy and that: I have no COIs with reviewing this work or that any perceived COIs have been waived by JOSS for the purpose of this review.

Code of Conduct

• I confirm that I read and will adhere to the JOSS code of conduct.

General checks

• Repository: Is the source code for this software available at the https://github.com/ascii-supply-networks/ascii-hydra?
• License: Does the repository contain a plain-text LICENSE or COPYING file with the contents of an OSI approved software license?
• Contribution and authorship: Has the submitting author (@HPicatto) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?
• Substantial scholarly effort: Does this submission meet the scope eligibility described in the JOSS guidelines
• Data sharing: If the paper contains original data, data are accessible to the reviewers. If the paper contains no original data, please check this item.
• Reproducibility: If the paper contains original results, results are entirely reproducible by reviewers. If the paper contains no original results, please check this item.
• Human and animal research: If the paper contains original data research on humans subjects or animals, does it comply with JOSS's human participants research policy and/or animal research policy? If the paper contains no such data, please check this item.

Functionality

• Installation: Does installation proceed as outlined in the documentation?
• Functionality: Have the functional claims of the software been confirmed?
• Performance: If there are any performance claims of the software, have they been confirmed? (If there are no claims, please check off this item.)

Documentation

• A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
• Installation instructions: Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.
• Example usage: Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).
• Functionality documentation: Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?
• Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?
• Community guidelines: Are there clear guidelines for third parties wishing to 1. Contribute to the software 2. Report issues or problems with the software 3. Seek support

Software paper

• Summary: Has a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience been provided?
• A statement of need: Does the paper have a section titled 'Statement of need' that clearly states what problems the software is designed to solve, who the target audience is, and its relation to other work?
• State of the field: Do the authors describe how this software compares to other commonly-used packages?
• Quality of writing: Is the paper well written (i.e., it does not require editing for structure, language, or writing quality)?
• References: Is the list of references complete, and is everything cited appropriately that should be cited (e.g., papers, datasets, software)? Do references in the text use the proper citation syntax?

[abhishektiwari]

Review checklist for @abhishektiwari

Conflict of interest

• I confirm that I have read the JOSS conflict of interest (COI) policy and that: I have no COIs with reviewing this work or that any perceived COIs have been waived by JOSS for the purpose of this review.

Code of Conduct

• I confirm that I read and will adhere to the JOSS code of conduct.

General checks

• Repository: Is the source code for this software available at the https://github.com/ascii-supply-networks/ascii-hydra?
• License: Does the repository contain a plain-text LICENSE or COPYING file with the contents of an OSI approved software license?
• Contribution and authorship: Has the submitting author (@HPicatto) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?
• Substantial scholarly effort: Does this submission meet the scope eligibility described in the JOSS guidelines
• Data sharing: If the paper contains original data, data are accessible to the reviewers. If the paper contains no original data, please check this item.
• Reproducibility: If the paper contains original results, results are entirely reproducible by reviewers. If the paper contains no original results, please check this item.
• Human and animal research: If the paper contains original data research on humans subjects or animals, does it comply with JOSS's human participants research policy and/or animal research policy? If the paper contains no such data, please check this item.

Functionality

• Installation: Does installation proceed as outlined in the documentation?
• Functionality: Have the functional claims of the software been confirmed?
• Performance: If there are any performance claims of the software, have they been confirmed? (If there are no claims, please check off this item.)

Documentation

• A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
• Installation instructions: Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.
• Example usage: Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).
• Functionality documentation: Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?
• Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?
• Community guidelines: Are there clear guidelines for third parties wishing to 1. Contribute to the software 2. Report issues or problems with the software 3. Seek support

Software paper

• Summary: Has a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience been provided?
• A statement of need: Does the paper have a section titled 'Statement of need' that clearly states what problems the software is designed to solve, who the target audience is, and its relation to other work?
• State of the field: Do the authors describe how this software compares to other commonly-used packages?
• Quality of writing: Is the paper well written (i.e., it does not require editing for structure, language, or writing quality)?
• References: Is the list of references complete, and is everything cited appropriately that should be cited (e.g., papers, datasets, software)? Do references in the text use the proper citation syntax?

[abhishektiwari]

@HPicatto - Added a few tickets to improve the documentation and usability of the ASCII Hydra. Appreciate if some of these issues are fixed before I take any further review of this package.

@HPicatto - I see multiple people contributing to project but they are not included as authors? Can you clarify if other contributors are aware of this paper? @HaoZeke worth confirming with EiC guideline here.

[HPicatto]

This paper is part of an institution, for releasing it we are using a github action using gitexporter. It was mentioned in this issue of JOSS. The other collaborators are users of this software and are aware of the existance and submission of the paper. They only collaborated with research that is not published/publishable. They also did not contribute in any meaningful way to the software or the paper, the coding was done by Georg and myself.

[HaoZeke]

Thanks for the clarifications @HPicatto and for flagging @abhishektiwari. I think the explanation makes sense and we can continue to move forward with the reviews :)

[abhishektiwari]

@HaoZeke Ack.

@HPicatto thanks for responding to my tickets. I will review your response and remaining review checklist items in next few days and revert back if any new further questions.