Oh, I am so weary of this nonsense.

mays.tamu.edu/wp-content/u...

My draft function starts with this:

months <- "Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec|January|February|March|April|June|July|August|September|October|November|December"

pattern <- paste0(
"(", months, "|\\d{1,4})",
"[- /\\.](", months, "|\\d{1,2}),?",
"[- /\\.]\\d{2,4}"
)

I am 100% with you! I'm having a nightmare trying to parse the random-ass formats that journals use for date of submission and publication. Grobid identifies them OK, but doesn't process them at all, so I'm working on a function to make a best guess, but no idea what to do with dates like 01-02-03.

I would like to join the Department of Full Luxury Galactic MetaScience, please

We are changing our name to metacheck in order to more accurately reflect the goals of our software and to not be associated with your software.

Haha, I have the same feeling, but also don't want to make my decision entirely based on an aesthetic preference :)

Not a bad name in general, but we want to move away from it just being about manuscript and also just being an R package. It may eventually evolve to something mainly web-based and running with more python code than R.

(with an R package version mainly aimed at metascientists)

Yeah, at 84K downloads, I know I can't just change defaults and function/argument names to something more sensible without breaking a bunch of people's code.

It's one of my top tips when I teach people how to write R packages: workshop your names and defaults a lot before you first submit to CRAN!

I've been thinking how to address this in my 70-person MSc coding class. Maybe take-home projects where part of the assessment is 15 minutes talking me through their code? But this adds a potential source of bias and will take ~20 hours (on top of already being well over my teaching allocation)

Haha, feels a bit egotistic :)

Very cute :) but hard to search for the right thing

We're working on a web app version that doesn't require R expertise, and it is not aimed specifically at coders, so we don't want to use an R-typical name.

CheckMate was one favourite possibility, but seems very difficult to google and is the name of a bunch of other apps

It's in the same universe as StatCheck and RegCheck (and can actually contain them) so MetaCheck seems like a natural name, but there is already a project in the same domain with that name (although it might be inactive, the last update was 3 years ago).

subugoe.github.io/metacheck/

Yeah, that's what I ended up doing. I looked into adding them as non-exported internal data, but those are always lazyloaded, regardless of settings, so it didn't help.

r-pkgs.org/data.html#se...

devtools::install_github("debruine/reprex.lazyload")

reprex.lazyload::mydata # works
reprex.lazyload::myfunc() # fails

library(reprex.lazyload)
myfunc() # works