Skip to content
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

[REVIEW]: SIRITVIS: Social Interaction Research Insights Topic Visualisation #6243

Closed
editorialbot opened this issue Jan 19, 2024 · 75 comments
Closed
Assignees
Labels
accepted published Papers published in JOSS Python 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 Jan 19, 2024

Submitting author: @CodeEagle22 (Sagar Narwade)
Repository: https://github.com/CodeEagle22/SIRITVIS/
Branch with paper.md (empty if default branch):
Version: v2.0.0
Editor: @oliviaguest
Reviewers: @n3mo, @cjbarrie
Archive: 10.6084/m9.figshare.26298487

Status

status

Status badge code:

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

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

@n3mo & @cjbarrie, 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 @oliviaguest 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 @cjbarrie

📝 Checklist for @n3mo

@editorialbot editorialbot added Python review TeX Track: 4 (SBCS) Social, Behavioral, and Cognitive Sciences labels Jan 19, 2024
@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.06 s (338.8 files/s, 54937.1 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
Python                           9            391            369           1437
XML                              1              0              0            450
JSON                             7              0              0            303
Markdown                         2             92              0            183
TeX                              1             28              4            122
YAML                             1              8              0             18
-------------------------------------------------------------------------------
SUM:                            21            519            373           2513
-------------------------------------------------------------------------------


gitinspector failed to run statistical information for the repository

@editorialbot
Copy link
Collaborator Author

Wordcount for paper.md is 1165

@editorialbot
Copy link
Collaborator Author

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

OK DOIs

- 10.18653/v1/2021.eacl-demos.31 is OK
- 10.1145/2484028.2484166 is OK
- 10.21105/joss.02507 is OK
- 10.3115/v1/W14-3110 is OK
- 10.18653/v1/2021.eacl-main.143 is OK
- 10.3389/frai.2020.00042 is OK
- 10.1609/icwsm.v8i1.14550 is OK

MISSING DOIs

- None

INVALID DOIs

- None

@oliviaguest
Copy link
Member

👋 Hi @n3mo @cjbarrie, thank you so much for helping out at JOSS. If you need any pointers, please feel free to look at previous reviews (which can be found by looking at published papers) and the documentation. If you need to comment on the code itself, opening an issue at the repo and then linking to it from here (to help me/others keep track) is the way to go. For comments on the paper, you can also open issues or PRs (say for typos), but those can be directly posted as replies in this issue. Thanks, and feel free to reach out if you need me. ☺️

@oliviaguest
Copy link
Member

@editorialbot generate pdf

@editorialbot
Copy link
Collaborator Author

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

1 similar comment
@editorialbot
Copy link
Collaborator Author

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

@cjbarrie
Copy link

cjbarrie commented Jan 26, 2024

Review checklist for @cjbarrie

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/CodeEagle22/SIRITVIS/?
  • 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 (@CodeEagle22) 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?

@cjbarrie
Copy link

cjbarrie commented Feb 1, 2024

Hi All,

I've been going through this and am bumping up against quite a few errors. I detail these in commented lines below:

from SIRITVIS import twitter_streamer, insta_streamer, reddit_streamer, cleaner, topic_model, topic_visualise, topic_mapper
import ssl
import nltk
try:
    _create_unverified_https_context = ssl._create_unverified_context
except AttributeError:
    pass
else:
    ssl._create_default_https_context = _create_unverified_https_context
nltk.download('stopwords')

# Run the streaming process to retrieve raw data based on the specified keywords
client_id = "******************"
client_secret = "**********************"
user_agent = "**************"
keywords = ['and'] # just to get random data
save_path = 'data/'
raw_data = reddit_streamer.RedditStreamer(client_id,client_secret,user_agent,save_path,keywords).run()

cleaner_obj = cleaner.Cleaner(data_source='data/',data_source_type='reddit')
cleaned_file = cleaner_obj.saving('data_cleaned/',data_save_name='reddit_cleaned')

cleaned_file.to_csv('corpus.csv', index=False, header=True)

# gives error if you pass cleaned_file to dataset_source
model = topic_model.TopicModeling(num_topics=10, dataset_source='corpus.csv',
learning_rate=0.001, batch_size=32, activation='softplus', num_layers=3, num_neurons=100,
dropout=0.2, num_epochs=100, save_model=False, model_path=None, train_model='NeuralLDA',
evaluation=['topicdiversity','invertedrbo','jaccardsimilarity'])

saved_model = model.run()
# gives nltk install error unless you use SSL routine above

# gives following error: An error occurred: max_df corresponds to < documents than min_df
vis_model = topic_visualise.PyLDAvis(data_source='corpus.csv',num_topics=5,text_column='text')
vis_model.visualize()

vis_model = topic_visualise.Wordcloud(data_source='corpus.csv',text_column='text')
vis_model.visualize() #nothing happens when trying to visualize

@CodeEagle22
Copy link

Hello @cjbarrie,

Thank you for providing your feedback. I'm pleased to inform you that the issues you mentioned have been addressed in the latest version (1.1.6). To ensure optimal plotting, I suggest utilizing an Integrated Development Environment (IDE) as some plots may encounter difficulties saving as image or HTML files when executing code via command line or terminal. Additionally, for optimal results or visualization appearance, it is recommended to maintain a minimum csv file size of 500KB to 1MB.

@cjbarrie
Copy link

cjbarrie commented Feb 7, 2024

Thank you for this @CodeEagle22. I'll review again with the latest version. It may be worth adding some of these pointers to the README too.

@CodeEagle22
Copy link

Hello @cjbarrie,

I have updated the README.md file on Git to ensure it reflects the latest information. Please inform me if there are any additional requirements needed to finalize the review process.

@cjbarrie
Copy link

Hi @CodeEagle22, this version now allows the cleaned_file object to be passed to the model specification function. But every time I run this, I get the following error:

model = topic_model.TopicModeling(num_topics=10, dataset_source=cleaned_file,
learning_rate=0.001, batch_size=32, activation='softplus', num_layers=3, num_neurons=100,
dropout=0.2, num_epochs=100, save_model=False, model_path=None, train_model='NeuralLDA',
evaluation=['topicdiversity','invertedrbo','jaccardsimilarity'])
ValueError: With n_samples=0, test_size=0.15 and train_size=None, the resulting train set will be empty. Adjust any of the aforementioned parameters.

I think this is because the actual reddit data I've collected is not sufficiently large. But the raw data I collected is >2GB in size. When I generate the cleaned file with:

cleaner_obj = cleaner.Cleaner(data_source='data/',data_source_type='reddit')
cleaned_file = cleaner_obj.saving('data_cleaned/',data_save_name='reddit_cleaned')

I get a .csv file with just 15 rows every time. Is there an argument I need to add to make sure that all of the data is combined with this function? It would be helpful to have more documentation so I could answer this myself.

@CodeEagle22
Copy link

Hey @cjbarrie,

Regarding the issue you're facing with the cleaned_file object in the model specification function, it seems that the error is due to an empty training set. This could be because the cleaned file generated from the raw Reddit data only contains 15 rows, which might not be sufficient for training the model effectively.

Multiple filters have been applied during the cleaning process to remove spam posts. While this ensures data quality, it might result in a reduced number of rows in the cleaned file. If you use given sample raw data of reddit you will find it generates thousands of lines in clean file which means in your raw streaming data there might be very less ham posts (15 rows).

To address this, I suggest considering the following points:

  1. Diversify Keywords: When collecting streaming data, employing a broader range of keywords can help diversify the dataset. For instance, incorporating terms like 'and', 'oil', and 'energy' could broaden the scope of the collected data, potentially yielding a larger pool of usable content for cleaning and analysis.

  2. Ensure Adequate File Size: The cleaned file's size is notably small, which is problematic for effective training. It's advisable to aim for a more substantial file size, ideally exceeding 500 KB.

By addressing these points, you can mitigate the issue of an empty training set and ensure that the model specification function receives a sufficiently large and diverse dataset for effective training.

@cjbarrie
Copy link

Thanks a lot for this, @CodeEagle22. This is helpful. I can use the sample data for tests... One thing: none of this seems to have been documented anywhere. It's hard for us to review when we don't know exactly what a function is doing without documentation (absent going into all of the source code etc.). And this would also make the library a lot more useful for applied users. I strongly recommend that you consider providing documentation for the functions, detailing the different variables and parameters. My apologies if this exists and I just haven't found it

@cjbarrie
Copy link

Hi @CodeEagle22, I've returned to this I'm now using the sample_dataset rather than collecting my own data. When I do this (in VS Code). I get the following error:

# gives following error: The visualisation is based on Latent Dirichlet Allocation (LDA) model.
# An error occurred: 'NoneType' object has no attribute 'display_formatter'
vis_model = topic_visualise.PyLDAvis(data_source=cleaned_file,num_topics=5,text_column='text')
vis_model.visualize()

# gives following error: The visualisation is based on Latent Dirichlet Allocation (LDA) model.
# An error occurred: 'NoneType' object has no attribute 'display_formatter'
vis_model = topic_visualise.Wordcloud(data_source=cleaned_file,text_column='text')
vis_model.visualize() 

I therefore decided to try out a different IDE and used a Google Colab notebook. When I did this, I got an import error related to pyLDAvis:

from SIRITVIS import twitter_streamer, insta_streamer, reddit_streamer, cleaner, topic_model, topic_visualise, topic_mapper
import nltk
nltk.download('stopwords')
/usr/local/lib/python3.10/dist-packages/ipykernel/ipkernel.py:283: DeprecationWarning: `should_run_async` will not call `transform_cell` automatically in the future. Please pass the result to `transformed_cell` argument and any exception that happen during thetransform in `preprocessing_exc_tuple` in IPython 7.17 and above.
  and should_run_async(code)
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
[<ipython-input-5-4aab91ff331f>](https://localhost:8080/#) in <cell line: 1>()
----> 1 from SIRITVIS import twitter_streamer, insta_streamer, reddit_streamer, cleaner, topic_model, topic_visualise, topic_mapper
      2 import nltk
      3 nltk.download('stopwords')

1 frames
[/usr/local/lib/python3.10/dist-packages/SIRITVIS/topic_visualise.py](https://localhost:8080/#) in <module>
     15 from IPython.core.display import display, HTML
     16 import pyLDAvis
---> 17 from pyLDAvis.lda_model import LDA
     18 import warnings
     19 from wordcloud import WordCloud

ImportError: cannot import name 'LDA' from 'pyLDAvis.lda_model' (/usr/local/lib/python3.10/dist-packages/pyLDAvis/lda_model.py)

So I decided to try jupyter lab. When I did this, all of the code ran but there was again no visualization output.

I think at this stage what I need is a notebook that I can open and run. All of these errors make me a bit nervous and will also mean it is unlikely that your end user is going to have much luck either.

@CodeEagle22
Copy link

Hey @cjbarrie,

Sorry for inconvenience. I've updated the issue and provided the latest documentation in pip installing SIRITVIS==1.1.7.1. This should address all the issues and make it more robust for end users.

@n3mo
Copy link

n3mo commented Mar 7, 2024

Review checklist for @n3mo

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/CodeEagle22/SIRITVIS/?
  • 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 (@CodeEagle22) 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?

@oliviaguest
Copy link
Member

@n3mo what is the status of your review now? 😊

@cjbarrie
Copy link

Hiya. I just went back to test with the new version of the library that @CodeEagle22 mentioned. I'm still bumping into a lot of errors, unfortunately. As I said above, it would really help if the authors could provide a Colab runthrough of the working library. As written, I just don't have the time to keep testing code that is not functioning as described. This is the fourth or fifth time I've been back to it.

I appreciate a lot of work has gone into this software. But realistically, the take-up by any end user will be minimal without further guidance on functionality and without resolving the errors I keep encountering.

Here is my code, with annotations of the errors this routine throws:

from SIRITVIS import twitter_streamer, insta_streamer, reddit_streamer, cleaner, topic_model, topic_visualise, topic_mapper

import ssl
try:
    _create_unverified_https_context = ssl._create_unverified_context
except AttributeError:
    pass
else:
    ssl._create_default_https_context = _create_unverified_https_context

import nltk
nltk.download('stopwords')

# using the Github sample_dataset data
cleaner_obj = cleaner.Cleaner(data_source='data/',data_source_type='reddit')
cleaned_file = cleaner_obj.saving('data_cleaned/',data_save_name='reddit_cleaned')

cleaned_file.to_csv('corpus.csv', index=False, header=True)

# This no longer takes "cleaned_file" object as parameter
model = topic_model.TopicModeling(num_topics=10, dataset_source='data_cleaned/reddit_cleaned_part_1.csv',
learning_rate=0.001, batch_size=32, activation='softplus', num_layers=3, num_neurons=100,
dropout=0.2, num_epochs=100, save_model=False, model_path=None, train_model='NeuralLDA',
evaluation=['topicdiversity','invertedrbo','jaccardsimilarity'])

saved_model = model.run()

# gives following error: The visualisation is based on Latent Dirichlet Allocation (LDA) model.
# An error occurred: 'NoneType' object has no attribute 'display_formatter'
vis_model = topic_visualise.PyLDAvis(data_source=cleaned_file,num_topics=5,text_column='text')
vis_model.visualize()

# gives following error: An error occurred: 'ImageDraw' object has no attribute 'textsize'
vis_model = topic_visualise.Wordcloud(data_source=cleaned_file,text_column='text')
vis_model.visualize() 

@n3mo
Copy link

n3mo commented Mar 19, 2024

I'm running into similar errors as @cjbarrie. The documentation suggests that the package is optimized for python notebooks, but it seems more accurate to say that it currently depends on it. I encountered the same two errors shared by @cjbarrie. The 'display_formatter' error associated with topic_visualize.PyLDAvis() does go away when model results are visualized in a Jupyter notebook. I am able to successfully create the intertopic distance map visualization.

It seems that the PyLDAvis package that does the heavy lifting here offers a pyLDAvis.save_html() method, which I believe allows visualization support outside of notebook contexts (by saving directly to file). However, SIRITVIS either doesn't make this available to it's visualizer, or I cannot figure out how to find it. Either way, @cjbarrie's observation is accurate: this is a significant barrier to new user take-up.

Aside from the above, the 'textsize' error associated with topic_visualise.Wordcloud() persists in both notebooks and interactive python shells, so I have been unable to generate this figure.

@n3mo
Copy link

n3mo commented Mar 19, 2024

I can confirm that the TopicMapper visualization also works for me, but also only in a notebook context. There is no error in an interactive python shell context--instead, an IPython.core.display.HTML object is returned. I believe this can be saved to file for display in a browser. But clearly, a notebook context is preferred here as well.

@oliviaguest
Copy link
Member

@CodeEagle22 what is the current situation? ☺️

@samhforbes
Copy link

@editorialbot generate pdf

@editorialbot
Copy link
Collaborator Author

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

@CodeEagle22
Copy link

Hello @samhforbes,

The latest version of the paper is more accurate, as you requested. I urge you if you can generate the PDF again.

Thank you!

@xillig
Copy link

xillig commented Aug 2, 2024

Dear @samhforbes, @oliviaguest, @samhforbes,

we rebuild the paper from scratch and now it shoud have the expected form. We should be able to move forward now. Sorry for the delay and thank you for your patience!

@samhforbes
Copy link

@editorialbot generate pdf

@editorialbot
Copy link
Collaborator Author

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

@samhforbes
Copy link

@editorialbot check references

@editorialbot
Copy link
Collaborator Author

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

OK DOIs

- 10.3115/v1/W14-3110 is OK
- 10.18653/v1/2021.eacl-demos.31 is OK
- 10.18653/v1/2021.eacl-main.143 is OK
- 10.1145/2484028.2484166 is OK
- 10.21105/joss.02507 is OK
- 10.3389/frai.2020.00042 is OK
- 10.1609/icwsm.v8i1.14550 is OK

MISSING DOIs

- No DOI given, and none found for title: Autoencoding Variational Inference for Topic Model...
- No DOI given, and none found for title: Tweetviz: Twitter Data Visualization
- No DOI given, and none found for title: Latent Dirichlet Allocation
- No DOI given, and none found for title: Wordcloud
- No DOI given, and none found for title: Twitmo: A twitter data topic modeling and visualiz...

INVALID DOIs

- None

@samhforbes
Copy link

@xillig @CodeEagle22 the PDF looks good thanks.
Can I just check the GitHub states a MIT licence, but on Figshare it's CC-BY. Can this be fixed to match please?
Likewise, we require the archive to list authors matching the paper.

@CodeEagle22
Copy link

Hey @samhforbes, I've updated the LICENSE file in the Git repo to CC-BY with correct all authors. Looking forward to any feedback you might have!

@xillig
Copy link

xillig commented Aug 7, 2024

Dear @samhforbes, @oliviaguest, @samhforbes,

we adjusted all the demanded parts - I think we are ready for release!

@samhforbes
Copy link

Hi both @CodeEagle22 and @xillig I just wanted to double check - but please note in submission requirements that JOSS needs OSI approved licences - see here: https://opensource.org/license
CC-BY is not OSI approved, but switching both to MIT or something else that is approved would work.
Otherwise agreed, I think all is looking good!

@CodeEagle22
Copy link

Hi @samhforbes, the license has been updated to MIT on both GitHub and Figshare.

@samhforbes
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.3115/v1/W14-3110 is OK
- 10.18653/v1/2021.eacl-demos.31 is OK
- 10.18653/v1/2021.eacl-main.143 is OK
- 10.1145/2484028.2484166 is OK
- 10.21105/joss.02507 is OK
- 10.3389/frai.2020.00042 is OK
- 10.1609/icwsm.v8i1.14550 is OK

MISSING DOIs

- No DOI given, and none found for title: Autoencoding Variational Inference for Topic Model...
- No DOI given, and none found for title: Tweetviz: Twitter Data Visualization
- No DOI given, and none found for title: Latent Dirichlet Allocation
- No DOI given, and none found for title: Wordcloud
- No DOI given, and none found for title: Twitmo: A twitter data topic modeling and visualiz...

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#5739, 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 8, 2024
@samhforbes
Copy link

@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: Narwade
  given-names: Sagar
  orcid: "https://orcid.org/0009-0004-9636-3611"
- family-names: Kant
  given-names: Gillian
  orcid: "https://orcid.org/0000-0003-2346-2841"
- family-names: Säfken
  given-names: Benjamin
  orcid: "https://orcid.org/0000-0003-4702-3333"
- family-names: Leiding
  given-names: Benjamin
doi: 10.6084/m9.figshare.26298487
message: If you use this software, please cite our article in the
  Journal of Open Source Software.
preferred-citation:
  authors:
  - family-names: Narwade
    given-names: Sagar
    orcid: "https://orcid.org/0009-0004-9636-3611"
  - family-names: Kant
    given-names: Gillian
    orcid: "https://orcid.org/0000-0003-2346-2841"
  - family-names: Säfken
    given-names: Benjamin
    orcid: "https://orcid.org/0000-0003-4702-3333"
  - family-names: Leiding
    given-names: Benjamin
  date-published: 2024-08-08
  doi: 10.21105/joss.06243
  issn: 2475-9066
  issue: 100
  journal: Journal of Open Source Software
  publisher:
    name: Open Journals
  start: 6243
  title: "SIRITVIS: Social Interaction Research Insights Topic
    Visualisation"
  type: article
  url: "https://joss.theoj.org/papers/10.21105/joss.06243"
  volume: 9
title: "SIRITVIS: Social Interaction Research Insights Topic
  Visualisation"

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.06243 joss-papers#5740
  2. Wait five minutes, then verify that the paper DOI resolves https://doi.org/10.21105/joss.06243
  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 8, 2024
@xillig
Copy link

xillig commented Aug 8, 2024

Dear @arfon, @n3mo, @oliviaguest, @samhforbes, @cjbarrie,

Thank you all for your contribution in making this publishing possible 😄

All the Best

@CodeEagle22
Copy link

Many thanks to @arfon, @n3mo, @oliviaguest, @samhforbes, and @cjbarrie for your valuable contributions and support in making this release possible 🎉

@samhforbes
Copy link

Congrats @CodeEagle22 @xillig!
Many thanks to @n3mo and @cjbarrie for reviewing, and also @oliviaguest for editing!

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

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

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

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 Python 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

8 participants