@wibeasley let me know if you need anything else on this (no particular rush on my end, but FWIW, I've been running this successfully from my fork)

thanks @adam3smith for the nudge.I like your fix and love that you included a test. Do you mind adding a few more tests, such as

• 3+ different search terms (by themselves)
• an fq that returns zero hits

- [ ] 3+ different search terms (in one url request)

I was planning to add them, but think you're a better fit. I've never used this parameter --and didn't even know what it was when I read your PR.

I am anxious to incorporate your PR and other son, before changes to the master require the PRs to merge the master's changes into the branches before they can be merged back into the master.

Will do -- might take me a couple of days, but shouldn't be a problem.

@wibeasley working on this -- I've added the zero hits test but I'm actually not quite clear what you're referring to with the two 3+ queries.
Am I understanding correctly that those test are general search tests, unrelated to fq? By "in one url request" you just mean a single search for author: King, type: dataset, title: replication ?
Not sure what you mean by "by themselves".

(Note that the dataverse API actually allows for multiple fq parameters in a single query, but the package (or maybe even R?) balks at having a parameter repeated. iIf that's OK I'd like to not address that for now since it may require more substantial code changes)

@adam3smith, (I'm looking at Advanced Search Example docs now. I've never used this, so feel free to tell me that I not making sense.)

Not sure what you mean by "by themselves".

maybe:

1. fq = dateSort (which is already in your PR)
2. fq = publicationDate
3. fq = description?

Note that the Dataverse API actually allows for multiple fq parameters in a single query, but the package (or maybe even R?) balks at having a parameter repeated.

ahh, I didn't know that, so scratch that 2nd checkbox. Thanks for correcting me.

If that's OK I'd like to not address that for now since it may require more substantial code changes)

Sure. And thanks for adding the zero-hits test.

got it, done -- please take a look & let me know if anything else is missing.

The way I understand fq, it's mostly used for the facets available on the left, but there are some additional options such as the dateSort. I have no idea where/whether those are even documented.

@adam3smith, looks great. Thanks again.

If it helps, "fq" is for "filter query".

The idea is that first you do a query with "q". Under the covers we pass a "*" (wildcard) as "q" when you are browsing Dataverse.

Then you use "fq" to refine or limit or narrow down your original "q". That is to say, there is always a "q" but the "fq" is optional. And as you have observed, you can have as many "fq"s as you want. You can only have one "q".

I hope this makes sense. You can also use boolean operators and such in both "q" and "fq" if you want. And operators like "TO" that @adam3smith is using with dateSort.