Return both ISSNs #54
Comments
|
Hi @ciakovx 👋 , Indeed, sometimes several ISSNs are associated with the same journal for electronic and paper versions. The first version of SHERPA/RoMEO API was not really clear about this. But it should be fairly easy to add a column that uses the ISSNs provided by the user. By the way, SHERPA/RoMEO is deeply changing and a version 2 is currently accessible to developers. More data will be accessible through it and we are currently working on a way to organize and convey all these data to users with the easiest interface possible. The package will undergo major changes to account for these changes in the data structure. |
|
Thank you Matthias. The fact that you configured it to search across the
different ISSNs is impressive and incredibly helpful. I really appreciate
your work with this; it has been incredibly helpful in my work as a
Scholarly Services Librarian. If it would help you if I wrote up a
statement on what I use it for and how it has improved my work, I would be
happy to do so; just let me know.
Thanks also for the information about V2 of SHERPA/RoMEO. This looks to be
much clearer that V1, and I am very pleased to hear you'll be updating the
package to account for the changes. I will keep in touch as I continue to
use the package.
Thank you again,
Clarke Iakovakis
…On Fri, Sep 27, 2019 at 4:54 AM Matthias Grenié ***@***.***> wrote:
Hi @ciakovx <https://github.com/ciakovx> 👋 ,
Thank you for your interest in the package!
Indeed, sometimes several ISSNs are associated with the same journal for
electronic and paper versions. The first version of SHERPA/RoMEO API was
not really clear about this. But it should be fairly easy to add a column
that uses the ISSNs provided by the user.
I'll be fixing this in the coming days.
By the way, SHERPA/RoMEO is deeply changing and a version 2 is currently
accessible to developers <https://v2.sherpa.ac.uk/romeo>. More data will
be accessible through it and we are currently working on a way to organize
and convey all these data to users with the easiest interface possible. The
package will undergo major changes to account for these changes in the data
structure.
So if you would like to access specific data, please do open new issues to
suggest new features !
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#54>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABTDILR4KFOG2SVVB27N3RDQLXJ4ZANCNFSM4I2S7UNA>
.
|
|
By the way Clarke, I forgot to mention that rOpenSci is collecting use cases on the packages that are part of it. We would be really interested if you would like to write a short post in the dedicated section of the forum on the way you use Thank you so much for your interest! |
|
Hi Clarke @ciakovx, if you install the last development version of |
|
Hi Matthias,
Thank you again for your assistance. I will add my use case to the rOpenSci
forum and post my script. Thank you!
Clarke
…On Mon, Sep 30, 2019 at 7:05 AM Matthias Grenié ***@***.***> wrote:
Hi Clarke @ciakovx <https://github.com/ciakovx>, if you install the last
development version of rromeo through
remotes::install_github("ropensci/rromeo") there will be a new column
called provided_issn that should let you merge your dataset properly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#54>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABTDILVFY42EX4V372RAKILQMHTRRANCNFSM4I2S7UNA>
.
|
Session Info
Hi, thanks for your great work on this package, I'm finding it immensely helpful.
The data returned from the
rr_journal_issnonly includes a single ISSN field. Sometimes the returned ISSN does not match the ISSN used in the query. It would be helpful to include the ISSN used in the initial query, or both ISSNs, as I am joining the results to my original dataset according to the issn used in the query. An example:The text was updated successfully, but these errors were encountered: