For those following Known’s bleeding edge repo should be interested in a number of changes recently merged in.
First is tentative support for the new PHP 8, released at the end of last month. At the time of writing, we’re still waiting for Travis CI to catch up, but it seems to be working ok.
Second, is a fairly large set of data model changes which sets the stage for some work we hope to do next year.
First, I’ve switched away from the Mongo inspired md5s (on MySQL at least) to using v4 UUIDs for object addressing. This is more industry standard, and is wider supported.
Second, I’ve introduced a
site collection. This identifies the site’s host, and gives us a nice entity to hang site specific information off of in the future. Crucially, entities will now be tagged with the site they were created on in a persistent way.
One immediate thing this gives us is a much more robust way for doing multi-tenant in a modern cloud environment.
My intention is to build on this concept going forward, and possibly even use it as an addressing mechanism for reader functionality.
Anyway, heads up if you’re following
master. Take a backup before updating!
Last week I gave a talk at the FREYA project wrap up meeting, part of the EOSC life symposium, on PIDs and how we (as part of my day job) were looking at using them to reproduce scientific research.
The basic concept is as follows:
- When a researcher visits an institution we create a PID identifying their “session”
- As an experiment is performed, we mint PIDs for each relevant asset, and “cite” the session identifier. Assets should include everything relevant for reproducing the science (this includes things you might not think of such as beam line or microscope configuration settings)
- When a research output is produced (research paper, protein in the protein database), all these sessions are tied together with another PID and a link is established between that bundle and the final output
- Using the PID Graph it is possible to unpack this.
If you’re interested, you can watch the presentation, or read more in the paper below.
This is just a quick one to say that I’ve spun out the Postgres database support out of Known core and into a community supported plugin.
The reason for this is basically that I want to put in some significant data model changes into Known core in the next few months, and due to my other commitments (and lack of Postgres expertise), I don’t have the resources to maintain this myself.
Anyone who’s interested in picking up Postgres support, please reach out in the comments or by email. I’ll also do my best to keep things up to date, but I’m unfortunately spread pretty thin these days!
» Visit the project on Github...