Skip to content

[REVIEW]: discourseGT: An R package to analyze discourse networks in educational contexts #5143

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
editorialbot opened this issue Feb 10, 2023 · 83 comments
Assignees
Labels
accepted published Papers published in JOSS R recommend-accept Papers recommended for acceptance in JOSS. review TeX Track: 4 (SBCS) Social, Behavioral, and Cognitive Sciences

Comments

@editorialbot
Copy link
Collaborator

editorialbot commented Feb 10, 2023

Submitting author: @q1cui (Qi Cui)
Repository: https://github.com/q1cui/discourseGT
Branch with paper.md (empty if default branch):
Version: 1.2.0
Editor: @marcosvital
Reviewers: @schochastics, @zoometh
Archive: 10.5281/zenodo.8164950

Status

status

Status badge code:

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

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

@schochastics & @zoometh & @lebebr01, 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 @marcosvital 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 @schochastics

📝 Checklist for @zoometh

@editorialbot editorialbot added R review Track: 4 (SBCS) Social, Behavioral, and Cognitive Sciences labels Feb 10, 2023
@editorialbot
Copy link
Collaborator Author

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
Copy link
Collaborator Author

Software report:

github.com/AlDanial/cloc v 1.88  T=0.02 s (891.8 files/s, 120868.5 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
R                               14            173            475            714
TeX                              1             66              0            676
Markdown                         2             48              0            152
-------------------------------------------------------------------------------
SUM:                            17            287            475           1542
-------------------------------------------------------------------------------


gitinspector failed to run statistical information for the repository

@editorialbot
Copy link
Collaborator Author

Wordcount for paper.md is 1104

@editorialbot
Copy link
Collaborator Author

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

@marcosvital
Copy link

Dear @schochastics, @zoometh and @lebebr01, thank you again for accepting review this submission for JOSS. The reviewing process is checklist based, and instructions were already posted above by the editorial bot - but let me know if you need any assistance, ok? Also, you can tag @q1cui if you have specific questions about the manuscript.

@q1cui, you can tag any of your co-authors GitHub accounts if you want, so they will be able to follow this issue.

@marcosvital
Copy link

@editorialbot check references

@editorialbot
Copy link
Collaborator Author

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

OK DOIs

- 10.1073/pnas.1319030111 is OK
- 10.1119/1.17117 is OK
- 10.3102/00346543052003421 is OK
- 10.21061/jte.v7i1.a.2 is OK
- 10.3102/00028312031002369 is OK
- 10.1007/s11409-006-6893-0 is OK
- 10.1007/s11409-009-9053-5 is OK
- 10.1037/0022-0663.85.4.571 is OK
- 10.1080/00221546.2016.1243942 is OK
- 10.1187/cbe.18-11-0222 is OK
- 10.1371/journal.pone.0173851 is OK
- 10.1073/pnas.1605554113 is OK
- 10.3102/00346543071003449 is OK
- 10.1073/pnas.122653799 is OK
- 10.1002/spe.4380211102 is OK
- 10.1039/D0RP00031K is OK
- 10.3102/0013189X18777741 is OK
- 10.3102/00028312031002338 is OK
- 10.3102/00028312037004911 is OK
- 10.1023/A:1014097416157 is OK
- 10.1177/1046496416689710 is OK
- 10.1016/j.cedpsych.2008.05.001 is OK
- 10.1080/10508400802224830 is OK
- 10.1016/j.ijer.2009.01.001 is OK
- 10.1207/s15327809jls1503_3 is OK
- 10.1187/cbe.17-08-0176 is OK
- 10.1207/S15326950DP3502_3 is OK
- 10.1598/RT.60.7.5 is OK
- 10.1016/j.obhdp.2005.03.002 is OK
- 10.1016/j.learninstruc.2016.05.002 is OK
- 10.5951/jresematheduc.43.1.0034 is OK
- 10.5951/jresematheduc.44.5.0775 is OK
- 10.3102/00346543071003449 is OK

MISSING DOIs

- 10.2307/2959965 may be a valid DOI for title: Classrooms as Communities: Exploring the Educational Character of Student Persistence
- 10.1002/9781119008989.ch8 may be a valid DOI for title: Algebraic Graph Theory
- 10.1109/tse.1981.234519 may be a valid DOI for title: Tidier Drawings of Trees
- 10.1101/gr.1239303 may be a valid DOI for title: Cytoscape: a software environment for integrated models of biomolecular interaction networks
- 10.3998/mpub.7106945 may be a valid DOI for title: Undertaking Discourse Analysis for Social Research
- 10.1177/0170840603024006005 may be a valid DOI for title: The professional partnership: Relic or exemplary form of governance?
- 10.1037/e648122011-001 may be a valid DOI for title: Productive Helping in Cooperative Groups

INVALID DOIs

- 10.1207/s1532690xci2104\_2 URL is INVALID
- 10.1207/S15326985EP3502\_4 URL is INVALID
- https://doi.org/10.1016/0020-0190(89)90102-6 is INVALID because of 'https://doi.org/' prefix
- https://doi.org/10.1002/j.1538-7305.1948.tb01338.x is INVALID because of 'https://doi.org/' prefix
- https://doi.org/10.1016/0022-5193(66)90013-0 is INVALID because of 'https://doi.org/' prefix
- https://doi.org/10.1002/tea.20003 is INVALID because of 'https://doi.org/' prefix
- 10.1207/s15327809jls1501\_8 URL is INVALID
- 10.1207/S1532690XCI1901\_1 URL is INVALID
- https://doi.org/10.1016/S0732-3123(03)00003-8 is INVALID because of 'https://doi.org/' prefix

1 similar comment
@editorialbot
Copy link
Collaborator Author

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

OK DOIs

- 10.1073/pnas.1319030111 is OK
- 10.1119/1.17117 is OK
- 10.3102/00346543052003421 is OK
- 10.21061/jte.v7i1.a.2 is OK
- 10.3102/00028312031002369 is OK
- 10.1007/s11409-006-6893-0 is OK
- 10.1007/s11409-009-9053-5 is OK
- 10.1037/0022-0663.85.4.571 is OK
- 10.1080/00221546.2016.1243942 is OK
- 10.1187/cbe.18-11-0222 is OK
- 10.1371/journal.pone.0173851 is OK
- 10.1073/pnas.1605554113 is OK
- 10.3102/00346543071003449 is OK
- 10.1073/pnas.122653799 is OK
- 10.1002/spe.4380211102 is OK
- 10.1039/D0RP00031K is OK
- 10.3102/0013189X18777741 is OK
- 10.3102/00028312031002338 is OK
- 10.3102/00028312037004911 is OK
- 10.1023/A:1014097416157 is OK
- 10.1177/1046496416689710 is OK
- 10.1016/j.cedpsych.2008.05.001 is OK
- 10.1080/10508400802224830 is OK
- 10.1016/j.ijer.2009.01.001 is OK
- 10.1207/s15327809jls1503_3 is OK
- 10.1187/cbe.17-08-0176 is OK
- 10.1207/S15326950DP3502_3 is OK
- 10.1598/RT.60.7.5 is OK
- 10.1016/j.obhdp.2005.03.002 is OK
- 10.1016/j.learninstruc.2016.05.002 is OK
- 10.5951/jresematheduc.43.1.0034 is OK
- 10.5951/jresematheduc.44.5.0775 is OK
- 10.3102/00346543071003449 is OK

MISSING DOIs

- 10.2307/2959965 may be a valid DOI for title: Classrooms as Communities: Exploring the Educational Character of Student Persistence
- 10.1002/9781119008989.ch8 may be a valid DOI for title: Algebraic Graph Theory
- 10.1109/tse.1981.234519 may be a valid DOI for title: Tidier Drawings of Trees
- 10.1101/gr.1239303 may be a valid DOI for title: Cytoscape: a software environment for integrated models of biomolecular interaction networks
- 10.3998/mpub.7106945 may be a valid DOI for title: Undertaking Discourse Analysis for Social Research
- 10.1177/0170840603024006005 may be a valid DOI for title: The professional partnership: Relic or exemplary form of governance?
- 10.1037/e648122011-001 may be a valid DOI for title: Productive Helping in Cooperative Groups

INVALID DOIs

- 10.1207/s1532690xci2104\_2 URL is INVALID
- 10.1207/S15326985EP3502\_4 URL is INVALID
- https://doi.org/10.1016/0020-0190(89)90102-6 is INVALID because of 'https://doi.org/' prefix
- https://doi.org/10.1002/j.1538-7305.1948.tb01338.x is INVALID because of 'https://doi.org/' prefix
- https://doi.org/10.1016/0022-5193(66)90013-0 is INVALID because of 'https://doi.org/' prefix
- https://doi.org/10.1002/tea.20003 is INVALID because of 'https://doi.org/' prefix
- 10.1207/s15327809jls1501\_8 URL is INVALID
- 10.1207/S1532690XCI1901\_1 URL is INVALID
- https://doi.org/10.1016/S0732-3123(03)00003-8 is INVALID because of 'https://doi.org/' prefix

@marcosvital
Copy link

@q1cui, please check the missing and invalid DOIs above when you can, and let me know if you need any assistance, ok?

@schochastics
Copy link

schochastics commented Feb 10, 2023

Review checklist for @schochastics

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

General checks

  • Repository: Is the source code for this software available at the https://github.com/q1cui/discourseGT?
  • License: Does the repository contain a plain-text LICENSE file with the contents of an OSI approved software license? Please add a LICENSE.md file for the MIT license e.g. as described here
  • Contribution and authorship: Has the submitting author (@q1cui) 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. (see paper not reproducible q1cui/discourseGT#1)
  • 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. (see paper not reproducible q1cui/discourseGT#1)
  • 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)? (see improve pkg docs q1cui/discourseGT#5)
  • Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified? (see add tests q1cui/discourseGT#3)
  • 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 (see add info on contributing to the package q1cui/discourseGT#4)

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?

@zoometh
Copy link

zoometh commented Feb 12, 2023

Review checklist for @zoometh

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

General checks

  • Repository: Is the source code for this software available at the https://github.com/q1cui/discourseGT?
  • License: Does the repository contain a plain-text LICENSE file with the contents of an OSI approved software license?
  • Contribution and authorship: Has the submitting author (@q1cui) 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?

@schochastics
Copy link

I have added a few issues to the repository which I would like to authors to address. Especially the test part is crucial to me. Please take some time and effort to add some tests to the package.

Overall this is a very nice package which just lacks a bit of good practice but that should be fixable. I am happy with the submission once my issues are addressed adequately. (cc @q1cui)

@zoometh
Copy link

zoometh commented Feb 20, 2023

Sorry for the delay, I will start my review at the end of the week.

@q1cui
Copy link

q1cui commented Feb 23, 2023

@editorialbot check references

@editorialbot
Copy link
Collaborator Author

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

OK DOIs

- 10.1073/pnas.1319030111 is OK
- 10.1119/1.17117 is OK
- 10.3102/00346543052003421 is OK
- 10.21061/jte.v7i1.a.2 is OK
- 10.3102/00028312031002369 is OK
- 10.1207/s1532690xci2104_2 is OK
- 10.1007/s11409-006-6893-0 is OK
- 10.1007/s11409-009-9053-5 is OK
- 10.1037/0022-0663.85.4.571 is OK
- 10.1207/S15326985EP3502_4 is OK
- 10.1080/00221546.1997.11779003 is OK
- 10.1080/00221546.2016.1243942 is OK
- 10.1187/cbe.18-11-0222 is OK
- 10.1371/journal.pone.0173851 is OK
- 10.1073/pnas.1605554113 is OK
- 10.3102/00346543071003449 is OK
- 10.1007/978-1-4613-0163-9 is OK
- 10.1073/pnas.122653799 is OK
- 10.1002/spe.4380211102 is OK
- 10.1016/0020-0190(89)90102-6 is OK
- 10.1109/TSE.1981.234519 is OK
- 10.1101/gr.1239303 is OK
- 10.3998/mpub.7106945 is OK
- 10.1039/D0RP00031K is OK
- 10.3102/0013189X18777741 is OK
- 10.1002/j.1538-7305.1948.tb01338.x is OK
- 10.1016/0022-5193(66)90013-0 is OK
- 10.3102/00028312031002338 is OK
- 10.3102/00028312037004911 is OK
- 10.1023/A:1014097416157 is OK
- 10.1002/tea.20003 is OK
- 10.1207/s15327809jls1501_8 is OK
- 10.1177/1046496416689710 is OK
- 10.1016/j.cedpsych.2008.05.001 is OK
- 10.1080/10508400802224830 is OK
- 10.1016/j.ijer.2009.01.001 is OK
- 10.1177/0170840603024006005 is OK
- 10.1207/s15430421tip4101_3 is OK
- 10.1207/s15327809jls1503_3 is OK
- 10.1187/cbe.17-08-0176 is OK
- 10.1207/S15326950DP3502_3 is OK
- 10.1598/RT.60.7.5 is OK
- 10.1016/j.obhdp.2005.03.002 is OK
- 10.1016/j.learninstruc.2016.05.002 is OK
- 10.1207/S1532690XCI1901_1 is OK
- 10.1016/S0732-3123(03)00003-8 is OK
- 10.5951/jresematheduc.43.1.0034 is OK
- 10.5951/jresematheduc.44.5.0775 is OK
- 10.3102/00346543071003449 is OK

MISSING DOIs

- None

INVALID DOIs

- None

@zoometh
Copy link

zoometh commented Feb 26, 2023

@editorialbot generate pdf

@editorialbot
Copy link
Collaborator Author

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

@zoometh
Copy link

zoometh commented Feb 26, 2023

👋 @q1cui

License:
change https://github.com/q1cui/discourseGT/blob/main/LICENSE to something like https://github.com/eamena-project/eamenaR/blob/main/LICENSE.md

Some minor errors:

  • missing ORCID | typos:

image

  • one missing reference:

image

  • change null to uppercase (NULL) since R is case sensitive:

image

  • No clear Community guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support. Please add them in GH

@editorialbot
Copy link
Collaborator Author

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

OK DOIs

- 10.1073/pnas.1319030111 is OK
- 10.1119/1.17117 is OK
- 10.3102/00346543052003421 is OK
- 10.21061/jte.v7i1.a.2 is OK
- 10.3102/00028312031002369 is OK
- 10.1207/s1532690xci2104_2 is OK
- 10.1007/s11409-006-6893-0 is OK
- 10.1007/s11409-009-9053-5 is OK
- 10.1037/0022-0663.85.4.571 is OK
- 10.1207/S15326985EP3502_4 is OK
- 10.1080/00221546.1997.11779003 is OK
- 10.1080/00221546.2016.1243942 is OK
- 10.1187/cbe.18-11-0222 is OK
- 10.1371/journal.pone.0173851 is OK
- 10.1073/pnas.1605554113 is OK
- 10.3102/00346543071003449 is OK
- 10.1007/978-1-4613-0163-9 is OK
- 10.1073/pnas.122653799 is OK
- 10.1002/spe.4380211102 is OK
- 10.1016/0020-0190(89)90102-6 is OK
- 10.1109/TSE.1981.234519 is OK
- 10.1101/gr.1239303 is OK
- 10.3998/mpub.7106945 is OK
- 10.1039/D0RP00031K is OK
- 10.3102/0013189X18777741 is OK
- 10.1002/j.1538-7305.1948.tb01338.x is OK
- 10.1016/0022-5193(66)90013-0 is OK
- 10.3102/00028312031002338 is OK
- 10.3102/00028312037004911 is OK
- 10.1023/A:1014097416157 is OK
- 10.1002/tea.20003 is OK
- 10.1207/s15327809jls1501_8 is OK
- 10.1177/1046496416689710 is OK
- 10.1016/j.cedpsych.2008.05.001 is OK
- 10.1080/10508400802224830 is OK
- 10.1016/j.ijer.2009.01.001 is OK
- 10.1177/0170840603024006005 is OK
- 10.1207/s15430421tip4101_3 is OK
- 10.1207/s15327809jls1503_3 is OK
- 10.1187/cbe.17-08-0176 is OK
- 10.1207/S15326950DP3502_3 is OK
- 10.1598/RT.60.7.5 is OK
- 10.1016/j.obhdp.2005.03.002 is OK
- 10.1016/j.learninstruc.2016.05.002 is OK
- 10.1207/S1532690XCI1901_1 is OK
- 10.1016/S0732-3123(03)00003-8 is OK
- 10.5951/jresematheduc.43.1.0034 is OK
- 10.5951/jresematheduc.44.5.0775 is OK
- 10.3102/00346543071003449 is OK

MISSING DOIs

- None

INVALID DOIs

- None

@marcosvital
Copy link

@editorialbot generate pdf

@editorialbot
Copy link
Collaborator Author

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

@marcosvital
Copy link

@editorialbot recommend-accept

@editorialbot
Copy link
Collaborator Author

Attempting dry run of processing paper acceptance...

@editorialbot
Copy link
Collaborator Author

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

OK DOIs

- 10.1073/pnas.1319030111 is OK
- 10.1119/1.17117 is OK
- 10.3102/00346543052003421 is OK
- 10.21061/jte.v7i1.a.2 is OK
- 10.3102/00028312031002369 is OK
- 10.1207/s1532690xci2104_2 is OK
- 10.1007/s11409-006-6893-0 is OK
- 10.1007/s11409-009-9053-5 is OK
- 10.1037/0022-0663.85.4.571 is OK
- 10.1207/S15326985EP3502_4 is OK
- 10.1080/00221546.1997.11779003 is OK
- 10.1080/00221546.2016.1243942 is OK
- 10.1187/cbe.18-11-0222 is OK
- 10.1371/journal.pone.0173851 is OK
- 10.1073/pnas.1605554113 is OK
- 10.3102/00346543071003449 is OK
- 10.1007/978-1-4613-0163-9 is OK
- 10.1073/pnas.122653799 is OK
- 10.1002/spe.4380211102 is OK
- 10.1016/0020-0190(89)90102-6 is OK
- 10.1109/TSE.1981.234519 is OK
- 10.1101/gr.1239303 is OK
- 10.3998/mpub.7106945 is OK
- 10.1039/D0RP00031K is OK
- 10.3102/0013189X18777741 is OK
- 10.1002/j.1538-7305.1948.tb01338.x is OK
- 10.1016/0022-5193(66)90013-0 is OK
- 10.3102/00028312031002338 is OK
- 10.3102/00028312037004911 is OK
- 10.1023/A:1014097416157 is OK
- 10.1002/tea.20003 is OK
- 10.1207/s15327809jls1501_8 is OK
- 10.1177/1046496416689710 is OK
- 10.1016/j.cedpsych.2008.05.001 is OK
- 10.1080/10508400802224830 is OK
- 10.1016/j.ijer.2009.01.001 is OK
- 10.1177/0170840603024006005 is OK
- 10.1207/s15430421tip4101_3 is OK
- 10.1207/s15327809jls1503_3 is OK
- 10.1187/cbe.17-08-0176 is OK
- 10.1207/S15326950DP3502_3 is OK
- 10.1598/RT.60.7.5 is OK
- 10.1016/j.obhdp.2005.03.002 is OK
- 10.1016/j.learninstruc.2016.05.002 is OK
- 10.1207/S1532690XCI1901_1 is OK
- 10.1016/S0732-3123(03)00003-8 is OK
- 10.5951/jresematheduc.43.1.0034 is OK
- 10.5951/jresematheduc.44.5.0775 is OK
- 10.3102/00346543071003449 is OK

MISSING DOIs

- None

INVALID DOIs

- None

@editorialbot
Copy link
Collaborator Author

The paper's PDF and metadata files generation produced some warnings that could prevent the final paper from being published. Please fix them before the end of the review process.

replacing image with description

@editorialbot
Copy link
Collaborator Author

⚠️ Error preparing paper acceptance. The generated XML metadata file is invalid.

ID ref-Lou_2001 already defined

@q1cui
Copy link

q1cui commented Aug 2, 2023

⚠️ Error preparing paper acceptance. The generated XML metadata file is invalid.

ID ref-Lou_2001 already defined

We have deleted the duplicate reference.

@q1cui
Copy link

q1cui commented Aug 2, 2023

@marcosvital We have fixed the image and reference issues.

@marcosvital
Copy link

@editorialbot recommend-accept

@editorialbot
Copy link
Collaborator Author

Attempting dry run of processing paper acceptance...

@editorialbot
Copy link
Collaborator Author

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

OK DOIs

- 10.1073/pnas.1319030111 is OK
- 10.1119/1.17117 is OK
- 10.3102/00346543052003421 is OK
- 10.21061/jte.v7i1.a.2 is OK
- 10.3102/00028312031002369 is OK
- 10.1207/s1532690xci2104_2 is OK
- 10.1007/s11409-006-6893-0 is OK
- 10.1007/s11409-009-9053-5 is OK
- 10.1037/0022-0663.85.4.571 is OK
- 10.1207/S15326985EP3502_4 is OK
- 10.1080/00221546.1997.11779003 is OK
- 10.1080/00221546.2016.1243942 is OK
- 10.1187/cbe.18-11-0222 is OK
- 10.1371/journal.pone.0173851 is OK
- 10.1073/pnas.1605554113 is OK
- 10.3102/00346543071003449 is OK
- 10.1007/978-1-4613-0163-9 is OK
- 10.1073/pnas.122653799 is OK
- 10.1002/spe.4380211102 is OK
- 10.1016/0020-0190(89)90102-6 is OK
- 10.1109/TSE.1981.234519 is OK
- 10.1101/gr.1239303 is OK
- 10.3998/mpub.7106945 is OK
- 10.1039/D0RP00031K is OK
- 10.3102/0013189X18777741 is OK
- 10.1002/j.1538-7305.1948.tb01338.x is OK
- 10.1016/0022-5193(66)90013-0 is OK
- 10.3102/00028312031002338 is OK
- 10.3102/00028312037004911 is OK
- 10.1023/A:1014097416157 is OK
- 10.1002/tea.20003 is OK
- 10.1207/s15327809jls1501_8 is OK
- 10.1177/1046496416689710 is OK
- 10.1016/j.cedpsych.2008.05.001 is OK
- 10.1080/10508400802224830 is OK
- 10.1016/j.ijer.2009.01.001 is OK
- 10.1177/0170840603024006005 is OK
- 10.1207/s15430421tip4101_3 is OK
- 10.1207/s15327809jls1503_3 is OK
- 10.1187/cbe.17-08-0176 is OK
- 10.1207/S15326950DP3502_3 is OK
- 10.1598/RT.60.7.5 is OK
- 10.1016/j.obhdp.2005.03.002 is OK
- 10.1016/j.learninstruc.2016.05.002 is OK
- 10.1207/S1532690XCI1901_1 is OK
- 10.1016/S0732-3123(03)00003-8 is OK
- 10.5951/jresematheduc.43.1.0034 is OK
- 10.5951/jresematheduc.44.5.0775 is OK

MISSING DOIs

- None

INVALID DOIs

- None

@editorialbot
Copy link
Collaborator Author

👋 @openjournals/sbcs-eics, this paper is ready to be accepted and published.

Check final proof 👉📄 Download article

If the paper PDF and the deposit XML files look good in openjournals/joss-papers#4451, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept

@editorialbot editorialbot added the recommend-accept Papers recommended for acceptance in JOSS. label Aug 2, 2023
@oliviaguest
Copy link
Member

@editorialbot accept

1 similar comment
@oliviaguest
Copy link
Member

@editorialbot accept

@editorialbot
Copy link
Collaborator Author

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

@editorialbot
Copy link
Collaborator Author

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: Cui
  given-names: Qi
  orcid: "https://orcid.org/0000-0002-3034-1143"
- family-names: Le
  given-names: Joshua P.
  orcid: "https://orcid.org/0000-0003-0872-7098"
- family-names: Chai
  given-names: Albert
  orcid: "https://orcid.org/0000-0002-2340-7044"
- family-names: ORCID
  given-names: Andrew S. Lee Without
- family-names: ORCID
  given-names: Jitarth Sheth Without
- family-names: ORCID
  given-names: Kevin Banh Without
- family-names: ORCID
  given-names: Priya Pahal Without
- family-names: ORCID
  given-names: Katherine Ly Without
- family-names: Lo
  given-names: Stanley M.
  orcid: "https://orcid.org/0000-0003-3574-2197"
contact:
- family-names: Cui
  given-names: Qi
  orcid: "https://orcid.org/0000-0002-3034-1143"
- family-names: Lo
  given-names: Stanley M.
  orcid: "https://orcid.org/0000-0003-3574-2197"
doi: 10.5281/zenodo.8164950
message: If you use this software, please cite our article in the
  Journal of Open Source Software.
preferred-citation:
  authors:
  - family-names: Cui
    given-names: Qi
    orcid: "https://orcid.org/0000-0002-3034-1143"
  - family-names: Le
    given-names: Joshua P.
    orcid: "https://orcid.org/0000-0003-0872-7098"
  - family-names: Chai
    given-names: Albert
    orcid: "https://orcid.org/0000-0002-2340-7044"
  - family-names: ORCID
    given-names: Andrew S. Lee Without
  - family-names: ORCID
    given-names: Jitarth Sheth Without
  - family-names: ORCID
    given-names: Kevin Banh Without
  - family-names: ORCID
    given-names: Priya Pahal Without
  - family-names: ORCID
    given-names: Katherine Ly Without
  - family-names: Lo
    given-names: Stanley M.
    orcid: "https://orcid.org/0000-0003-3574-2197"
  date-published: 2023-08-14
  doi: 10.21105/joss.05143
  issn: 2475-9066
  issue: 88
  journal: Journal of Open Source Software
  publisher:
    name: Open Journals
  start: 5143
  title: "discourseGT: An R package to analyze discourse networks in
    educational contexts"
  type: article
  url: "https://joss.theoj.org/papers/10.21105/joss.05143"
  volume: 8
title: "discourseGT: An R package to analyze discourse networks in
  educational contexts"

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
Copy link
Collaborator Author

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

@editorialbot
Copy link
Collaborator Author

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

Here's what you must now do:

  1. Check final PDF and Crossref metadata that was deposited 👉 Creating pull request for 10.21105.joss.05143 joss-papers#4490
  2. Wait a couple of minutes, then verify that the paper DOI resolves https://doi.org/10.21105/joss.05143
  3. If everything looks good, then close this review issue.
  4. Party like you just published a paper! 🎉🌈🦄💃👻🤘

Any issues? Notify your editorial technical team...

@editorialbot editorialbot added accepted published Papers published in JOSS labels Aug 14, 2023
@oliviaguest
Copy link
Member

Congratulations! @q1cui! Bit thanks to @marcosvital and the reviewers @schochastics, @zoometh! 🥳

@editorialbot
Copy link
Collaborator Author

🎉🎉🎉 Congratulations on your paper acceptance! 🎉🎉🎉

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.05143/status.svg)](https://doi.org/10.21105/joss.05143)

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

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

This is how it will look in your documentation:

DOI

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:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted published Papers published in JOSS R recommend-accept Papers recommended for acceptance in JOSS. review TeX Track: 4 (SBCS) Social, Behavioral, and Cognitive Sciences
Projects
None yet
Development

No branches or pull requests

6 participants