Do editing in a non-indexed draft space and then move the articles into an indexed mainspace after passing peer review.
I guess a "WikiJournal" should be CC-ND by default. Authors should be able to relax the license. If others are allowed to edit then the license should be forced to CC-by-SA. Authors should be explicitly listed, and if authors allow other to edit, then they must explicitly say so. A "front matter" like in Jekyll should be sufficient for declaring the authors. There must also be a process for verifying the identity for authors. That can be really fun! And btw, Mediawiki has a field for real names, but lacks methods for verifying those names. On Mon, Jun 3, 2019 at 4:36 PM James Heilman <jmh...@gmail.com> wrote: > > The peer review process and the editors of the journals in question. This > is the same mechanism that prevents gibberish from getting into all peer > reviewed literature. > > J > > On Mon, Jun 3, 2019 at 6:30 AM Vi to <vituzzu.w...@gmail.com> wrote: > > > In years I've seen countless attempts to put gibberish on our projects > > which were eventually defeated by the "no original research" principle. > > Even en.wikiversity struggled with a now banned user (and his > > friends/enablers) pushing lots of gibberish about cold fusion, paranormal > > and Wikimedia user themselves. So I ask, what will prevent this kind of > > gibberish from slowing infiltrating such project? > > > > Don't get me wrong but I think this is the first question in order to > > define a "business model" for the project: why would a "serious" research > > group choose to publish there instead of already existing OA journals or > > classical PR journals? > > > > Vito > > > > Il giorno lun 3 giu 2019 alle ore 04:16 Thomas Shafee < > > thomas.sha...@gmail.com> ha scritto: > > > > > Yes, we put together a little checklist back in round one (*link* > > > < > > > > > https://en.wikiversity.org/wiki/Talk:WikiJournal_User_Group#Notes_on_Plan_S_compliance_criteria > > > > > > > ). > > > > > > Initially there were a few items that are currently not achieved (e.g. > > > JATS-compliant XML formatting). The revised Plan_S has reduced stringency > > > and all the items that weren't hit happen to be optional. That being > > said, > > > things like JATS-compliant XML and citation metadata would be valuable to > > > implement anyway for machine readability. > > > > > > Thomas > > > > > > On Mon, 3 Jun 2019 at 04:53, James Heilman <jmh...@gmail.com> wrote: > > > > > > > It already is Plan-S compliant :-) > > > > > > > > https://en.wikipedia.org/wiki/Plan_S#Licensing_and_rights > > > > > > > > Plan-S unfortunately is looking at allowing ND content. > > > > > > > > James > > > > > > > > On Sun, Jun 2, 2019 at 8:14 AM Mister Thrapostibongles < > > > > thrapostibong...@gmail.com> wrote: > > > > > > > > > Thomas > > > > > > > > > > Is it intended that the journals should be Plan-S compliant? > > > > > > > > > > Thrapostibongles > > > > > > > > > > On Sun, Jun 2, 2019 at 9:01 AM Thomas Shafee < > > thomas.sha...@gmail.com> > > > > > wrote: > > > > > > > > > > > Hello Wikipedians, > > > > > > > > > > > > Over the last few years, the WikiJournal User Group > > > > > > <https://en.wikiversity.org/wiki/WikiJournal_User_Group> has been > > > > > building > > > > > > and testing a set of peer reviewed academic journals on a mediawiki > > > > > > platform. The main types of articles are: > > > > > > > > > > > > - Existing Wikipedia articles submitted for external review and > > > > > feedback > > > > > > (example <https://doi.org/10.15347/wjs/2018.006>) > > > > > > - From-scratch articles that, after review, are imported to > > > > Wikipedia > > > > > ( > > > > > > example <https://doi.org/10.15347/wjm/2018.001>) > > > > > > - Original research articles that are not imported to Wikipedia > > > > > (example > > > > > > < > > > > > > > > > > > > > > > > > > > > https://en.wikiversity.org/wiki/WikiJournal_of_Medicine/Acute_gastrointestinal_bleeding_from_a_chronic_cause:_a_teaching_case_report > > > > > > > > > > > > > ) > > > > > > > > > > > > *Proposal: WikiJournals as a new sister project > > > > > > <https://meta.wikimedia.org/wiki/WikiJournal>* > > > > > > > > > > > > From a Wikipedian point of view, this is a complementary system to > > > > > Featured > > > > > > article review, but bridging the gap with external experts > > > > > > < > > > https://en.wikiversity.org/wiki/WikiJournal_User_Group/Peer_reviewers > > > > >, > > > > > > implementing established scholarly practices > > > > > > < > > > > > > https://en.wikiversity.org/wiki/WikiJournal_User_Group/Ethics_statement > > > > > >, > > > > > > and generating citable, doi-linked publications > > > > > > <https://en.wikiversity.org/wiki/WikiJournal_User_Group/Publishing > > >. > > > > > > > > > > > > Please take a look and support/oppose/comment! > > > > > > All the best, > > > > > > Thomas Shafee > > > > > > > > > > > > ps, We are attempting to improve awareness within the existing > > > > wikimedia > > > > > > community, so feel free to share with others. > > > > > > _______________________________________________ > > > > > > Wikimedia-l mailing list, guidelines at: > > > > > > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and > > > > > > https://meta.wikimedia.org/wiki/Wikimedia-l > > > > > > New messages to: Wikimedia-l@lists.wikimedia.org > > > > > > Unsubscribe: > > > https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > > > > > > <mailto:wikimedia-l-requ...@lists.wikimedia.org > > ?subject=unsubscribe> > > > > > _______________________________________________ > > > > > Wikimedia-l mailing list, guidelines at: > > > > > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and > > > > > https://meta.wikimedia.org/wiki/Wikimedia-l > > > > > New messages to: Wikimedia-l@lists.wikimedia.org > > > > > Unsubscribe: > > https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > > > > > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe> > > > > > > > > > > > > > > > > -- > > > > James Heilman > > > > MD, CCFP-EM, Wikipedian > > > > _______________________________________________ > > > > Wikimedia-l mailing list, guidelines at: > > > > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and > > > > https://meta.wikimedia.org/wiki/Wikimedia-l > > > > New messages to: Wikimedia-l@lists.wikimedia.org > > > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > > > > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe> > > > _______________________________________________ > > > Wikimedia-l mailing list, guidelines at: > > > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and > > > https://meta.wikimedia.org/wiki/Wikimedia-l > > > New messages to: Wikimedia-l@lists.wikimedia.org > > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > > > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe> > > _______________________________________________ > > Wikimedia-l mailing list, guidelines at: > > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and > > https://meta.wikimedia.org/wiki/Wikimedia-l > > New messages to: Wikimedia-l@lists.wikimedia.org > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe> > > > > -- > James Heilman > MD, CCFP-EM, Wikipedian > _______________________________________________ > Wikimedia-l mailing list, guidelines at: > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and > https://meta.wikimedia.org/wiki/Wikimedia-l > New messages to: Wikimedia-l@lists.wikimedia.org > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe> _______________________________________________ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l New messages to: Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
