-
-
Notifications
You must be signed in to change notification settings - Fork 41
[PRE REVIEW]: FreeStylo: An easy-to-use stylistic device detection tool for stylometry #7443
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
Comments
Hello human, 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:
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
|
Software report:
Commit count by author:
|
Paper file info: 📄 Wordcount for ✅ The paper includes a |
License info: 🟡 License found: |
|
Five most similar historical JOSS papers: TRUNAJOD: A text complexity library to enhance natural language processing Arabica: A Python package for exploratory analysis of text data Augmenty: A Python Library for Structured Text Augmentation Fast, Consistent Tokenization of Natural Language Text textnets: A Python package for text analysis with networks |
👋 @fschncvg - You mention the following previous publications: Please clearly state how / if the current submission is different from the above. Thanks. |
The previous publications are the base forms of the chiasmus and metaphor detector. While both have code to replicate the experiments and could with some work probably used by someone proficient in programming to also detect those stylistic devices in other texts, this software provides a new implementation of the concept that can be either used as a python library in other programs or be used directly by e.g. literary scholars with no programming knowledge. The additional stylistic devices that can be detected (polysyndeton, epiphora, alliterative verse) do not rely on machine learning and have not been previously published by me, but since this software provides a growing general stylistic device detector collection, it makes sense to include them, especially since they are interesting for various stylometric analysis tasks. So the main difference is: Two of the previously published papers provide methods that are implemented in this software package. Additionally this package provides three more methods to find other stylistic devices. About the similarity to those previously published papers the bot linked: My software package detect stylistic devices. Those linked do not. @dpalsman published a software that analyzes other aspects of text (e.g. discourse markers, emotions...) and could be used together with my software to gain information the other does not address. We both use spaCy for preprocessing, which makes the interoperability easy. However, my package also provides a cltk backend for Middle High German which can be easily be extended for other classical languages supported by cltk. @PetrKorab published a software that analyzes various parts of time-series structured text (e.g. news artices, social media posts) for various things, but no stylistic devices. However, my software could be integrated into theirs to also support stylistic devices. @KennethEnvoldsen provides a software that augments text by e.g. standardising spelling and grammar. It does not compute stylometric information like the choice of words - or of stylistic devices. This could maybe be used as a preprocessing step for my software, however it may destroy the stylistic devices that my software searches for. @lmullen provides an R package for various tokenization tasks, but no stylistic device detection. It could be used as a preprocessing step, but since it is written in R, the interoperability to my python package is limited. @jboynyc uses network analysis on collections of text to find out which words are used by different authors and how this connects and groups the authors. While it would be interesting to also do network analysis to find out how different authors use stylistic devices and how they are connected and grouped by that, their software does not use or find stylistic devices and provides a different service than mine. |
@editorialbot query scope Thank you @fschncvg, I am going to run this through scope review with our larger editorial board as well. I'll get back to you ASAP. Thanks! |
Submission flagged for editorial review. |
@editorialbot invite @logological as editor 👋 @logological - are you available to edit this one? I am going to pull it from scope query. |
Invitation to edit this submission sent! |
@crvernon Yes, I'm free to edit this submission starting next week. |
@editorialbot assign @logological as editor Sounds great @logological! Thank you! |
Assigned! @logological is now the editor |
@logological I will be happy to help in reviewing this package, I am availbel to help post mid dec. |
@sara-02 Thanks for volunteering to review! I'd be glad to have you on board. I'll try to find one or two further reviewers now. |
@editorialbot add @sara-02 as reviewer |
@sara-02 added to the reviewers list! |
@mikekestemont @SamHames @rlskoeser Would you be willing and able to review this submission on stylistic device detection for the Journal of Open Source Software? |
@logological Unfortunately I have too much on my plate right now to review this. |
@beinborn @SteffenEger Would you be willing and able to review this submission on stylistic device detection for the Journal of Open Source Software? |
@logological I'm willing to take this on and interested in learning more about the software package, but will need a bit more time than usual given the holidays just around the corner. Thanks for inviting me to review. |
@rlskoeser That's fine; it's great to have you on board. We now have enough reviewers to begin the review process; if a third volunteers, we can add them later. I'll set up a separate issue for the review. @sara-02 and @rlskoeser, you can begin reviewing there right away, or as soon as it's convenient for you. |
@editorialbot add @rlskoeser as reviewer |
@rlskoeser added to the reviewers list! |
@editorialbot start review |
OK, I've started the review over in #7596. |
@logological seems you have reviewers already - apologies, there are too many things these days |
Submitting author: @fschncvg (Felix Schneider)
Repository: https://github.com/cvjena/freestylo
Branch with paper.md (empty if default branch):
Version: v0.5.0
Editor: @logological
Reviewers: @sara-02, @rlskoeser
Managing EiC: Chris Vernon
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @fschncvg. Currently, there isn't a JOSS editor assigned to your paper.
@fschncvg if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). You can search the list of people that have already agreed to review and may be suitable for this submission.
Editor instructions
The JOSS submission bot @editorialbot is here to help you find and assign reviewers and start the main review. To find out what @editorialbot can do for you type:
The text was updated successfully, but these errors were encountered: