naustica / Pitaya

A Julia interface to the Crossref REST API
MIT License
7 stars 0 forks source link

New Crossref REST API coming soon #2

Open ppolischuk opened 3 years ago

ppolischuk commented 3 years ago

Hi,

Thank you for maintaining one of the documented libraries for using the Crossref REST API.

We’ve been working on a new version of the REST API, replacing the Solr backend with Elasticsearch and moving from our own hardware in a datacenter to a cloud platform.

We plan to cutover to the new version shortly (expect an official announcement on our blog in the next few days with more details), and wanted to invite you to test it out before the official cutover.

Please check it out at https://api.production.crossref.org/

During the cutover phase (expected to last a few weeks), traffic will be redirected to the above domain on a pool by pool basis. Once all traffic is using the new service, we will continue to use the api.crossref.org domain, so please do not update anything to use the temporary domain.

Let me know if you have any questions. Issues can be filed into our GitLab issue repository, or I’ll keep an eye on this thread.

Thanks again, Patrick

adigitoleo commented 2 years ago

I am considering contributing to this library, in particular I would like to suggest more granular search with e.g. query.bibliographic, query.author, etc. as is recommended in your tips page. @ppolischuk Is the new API released (if so could you link the blog page)? Does it come with any semantic changes or is it only a backend improvement?

Thank you for working on crossref.

naustica commented 2 years ago

@adigitoleo Hi, you are welcome to contribute to this library :D

ppolischuk commented 2 years ago

The new API is released, and featured mostly backend improvements. There are a few other changes outlined in the blog post here: https://www.crossref.org/blog/behind-the-scenes-improvements-to-the-rest-api/

adigitoleo commented 1 year ago

@naustica After playing around some more with Juila and learning its ways, I have found that it is too slow for command line apps in my opinion, which was my intended use case. I may be able to help out with maintaining this library if I find time, but no promises unfortunately. I have instead been querying the new API using a simple python script which is not very flexible but was all I had time for at the moment. It doesn't make use of the fine grained query controls yet, I wanted to add article searching, but for now I just use the web UI for that.

Something I have learned from attempting to add abstract querying is that the abstract metadata is still quite poor, quite often lacking completely and usually polluted with all sorts of MathML or XML tags, encoded HTLM entities, raw LaTeX and other stuff. Just a heads up.

My script also doesn't do any caching of course, which is not ideal, so I don't recommend it for heavy use (for any readers at home). But maybe it is useful for some inspiration.