Another quick one, here is a small library I wrote as part of the Day Job that makes it (slightly) easier to parse web hooks from Mailgun.
Pretty much a stub right now, but we use it daily.
Hopefully it is of use to some folks.
Just a quick one to make people aware of some potentially useful things I’ve done as part of the day job.
Here is a wrapper around symfony routing that makes it behave, more or less, like Toro. This lets you create simple REST pages, which understand HTTP Verbs.
Additionally you can bind in understanding for access grants and bearer tokens.
We use this to build out a lot of our services at the day job, so hopefully it’ll be of some use to you.
Just a quick one; first of all as a sign of life, I know I’ve been quiet of late, and second of all, to put out something that might be of use (albeit to a niche audience).
DOIs, or Digital Object Identifiers, are persistent identifiers for digital object for all sorts of things on the internet. Typically these are published documents, but they may also be things like datasets, workflows, images, etc.
I deal with these a fair amount at The Day Job, and often need to resolve these strings into something that returns metadata (title, author etc). Nice to be able to do this over an API.
Datacite, Crossref etc, who deal in DOIs, do provide their own resolution APIs, but only for items minted in their own namespaces, not the canonical set. DOI.org do provide a proxy, in order to resolve a doi to a location, but no obvious way of extracting metadata.
As it happens, there is a way of getting this data, with a little bit of Accept header witchcraft.
Anyway, to make it easier for you (and me), I wrote a library. Enjoy!
