This will basically lock out people in the developing world from publishing in these journals.
This will basically lock out people in the developing world from publishing in these journals.
On balance, open access helps the developing world far more and costs less: Because access to journal and conference articles is now possible. Before open access, article fees around $50 for reading a single article meant, that to write an article you had to spend the $500 on the roughly 10 (usually more) related articles you needed to research and reference. To even get to the stage of writing an article, you need to read quite a few, impossible with the sky-high subscription fees that even rich western institutions balk at. And as everywhere, university libraries reimburse publishing fees out of the subscription cost they saved.
Open Access is cheaper, fairer and especially beneficial to education in the developing world.
Of course reading articles costs nothing on SciHub, but I guess the people you are working for don't want that to be known, eh?
All that's changed for researchers now is they have to fork over a factor or two or more to publish in the same journals as a few years ago.
Pretending that things are fine now is dishonest imho. Business practices of the IP industry aren't suddenly a-ok just because you can pirate your way around it and pretend that therefore they aren't harming anyone.
So part of it is the university just needs to figure out how to appropriately reallocate it's resources?
I wonder how often the university employers of article authors pay these publication fees, and if those budgets are going up? (If university library subscription fees are not going down, then that's another sort of mystery to look into).
“submission in some electronic formats qualifies for a publication charge discount (Physical Review Letters) or waiver (Physical Review A, B, C, D, E, Applied, Fluids). Acceptable formats for the discount or waiver are currently REVTeX (preferred), LaTeX, Harvmac, or MSWord”: https://journals.aps.org/pre/authors/submission-faq#discount
How do you define exactly "predatory publishing" ? Every journal that is not one of the major monopolistic journal that profits from the work and money of others ?
To name and shame: Elsevier, Springer, deGruyter, Wiley, Nature and lots of other smaller ones.
This does not affect the open access business model: Only a small fraction of papers is submitted by researchers in developing countries.
I've forked out >$4k for a high-quality journal to make my research open-access. Or I could have paid $0 and it would be behind a paywall.
Some like Nature, publish largely open-access but it can cost >$8k to be published there.
There's a charge comparison table[0]. Prices are going up, but they'll be lower than the previous AAS Journals Open Access premium. Their sample paper prices are $60-225 per page (because AAS journals have "quanta" charges, where a quanta is a set number of words, a figure, etc.).
>> Assuming a publication rate of 200 papers per year this works out at ~$4.75 per paper
> [joss_costs]: https://joss.theoj.org/about#costs
^^ from https://news.ycombinator.com/item?id=24517711 & this log of my non- markdown non- W3C Web Annotation threaded comments with URIs: https://westurner.github.io/hnlog/#comment-24517711
Referees work for free. Submitting authors pay through the nose for presumably typesetting and proofs whose true cost is closer to $1/page rather than hundreds. Editors are overworked.
Sci-Hub was supposed to disrupt that industry, but it seems all it's done is shift burden to authors and created pay-for publishing.
Additional ScholarlaryArticle "Journal" costs: moderation, BinderHub / JupyterLite white label SaaS?, hosting data and archived reproducible container images on IPFS and academictorrents and Git LFS, hosting {SQL, SPARQL, GraphQL,} queries and/or a SOLID HTTPS REST API and/or RSS feeds with dynamic content but static feed item URIs and/or ActivityStreams and/or https://schema.org/Action & InteractAction & https://schema.org/ReviewAction & ClaimReview fact check reviews, W3C Web Notifications, CRM + emailing list, keeping a legit cohort of impactful peer reviewers,
#LinkedData for #LinkedResearch: Dokieli, parsing https://schema.org/ScholarlyArticle citation styles,
"Ask HN: How are online communities established?" https://news.ycombinator.com/item?id=24443965 re: building community, MCOS Marginal Cost of Service, CLV Customer Lifetime Value, etc
> Income: JOSS has an experimental collaboration with AAS publishing where authors submitting to one of the AAS journals can also publish a companion software paper in JOSS, thereby receiving a review of their software. For this service, JOSS receives a small donation from AAS publishing. In 2019, JOSS received $200 as a result of this collaboration.
Firstly, encouraging and structuring code review in academia. My own code is almost entirely solo (and messy), so a venue for structured review and an incentive to robustify public code is good. Secondly, the culture in some disciplines is that code is not citable, only papers - and JOSS is an end-run around this. I hope this second situation is changing, but we're not there yet so JOSS has a valuable role for the moment in simply being a 'journal' assigning DOIs basically for code packages.
Does JOSS specify e.g. ReviewBoard, GitHub Pull Request reviews, or Gerrit for code reviews?
I don't want to oversell the depth of the code review possible; not all of the reviewers will be fully expert in whatever tiny cutting-edge area the package is for (making correctness checks difficult beyond the test suite), and most of us are academics-who-code rather than research software engineers. But the fact it's happening at all is a great step forward.
[0]: https://github.com/openjournals/joss-reviews/issues [1]: https://joss.readthedocs.io/en/latest/review_criteria.html
https://en.wikipedia.org/wiki/Software_review
https://en.wikipedia.org/wiki/Software_peer_review
I'd add "Antipatterns" > "Software" https://en.wikipedia.org/wiki/Anti-pattern#Software_design
and "Code smells" > "Common code smells" https://en.wikipedia.org/wiki/Code_smell#Common_code_smells
and "Design smells" for advanced reviewers: https://en.wikipedia.org/wiki/Design_smell
and the CWE "Common Weakness Enumeration" numbers and thus URLs for Issues from the CWE Top 25 and beyond: https://cwe.mitre.org/top25/
FWIW, many or most scientists are not even trying to be software engineers: they just write slow code without reusing already-tested components and expect someone else to review Pull Requests after their PDF is considered impactful. They know enough coding to push the bar for their domain a bit higher each time.
Are there points for at least in-writing planing for the complete lifecycle and governance of an ongoing thesis defense of open source software for science; after we publish, what becomes of this code?