Alongside a bunch of bug fixes, we've got a few new features on chive.pub we're excited about. Most of them involve connecting a paper to other things that relate to it on the Atmosphere and beyond.
Post
Papers on chive.pub now have an Atmosphere tab, which collects up records elsewhere on the network that refer to it.
@leaflet.pub documents and comments that reference an eprint now show up on it. Chive picks up the reference whether it's an inline link in the prose, a website block, or the subject of a comment.
Records from Semble (@cosmik.network) and @margin.at reach chive as well. Adding a paper to a Semble collection, connecting two works, or annotating one on Margin now shows on the paper.
New eprints publish a site.standard.document record, so @standard.site readers can pick them up. Sharing an eprint to bluesky also records the post on that document, which makes the reply thread findable from the paper.
You can now post an event with @smokesignal.events or anything else using community.lexicon.calendar.event, list the eprint among its URIs, and the paper shows where it was presented.
You can also point a paper at a @layers.pub dataset it introduces or uses. A dataset is named by at-uri rather than by a URL at some host, so the reference is to the record and doesn't depend on a particular page staying up.
1 repost1 like
Relatedly, check out @layers.pub's recent announcement about the repo.layers.pub data PDS and lairs (layers.pub/lairs) toolkit.
layers.pub now has an official data PDS at repo.layers.pub as well as a python client and CLI that you can read about at layers.pub/lairs/!
Chive now reads your @sifa.id profile if you have one and populates your public profile with current and previous affiliations automatically.
Submitting an eprint can also optionally record it on your @sifa.id profile in the same step, so you don't have to enter a paper twice.
Finally, papers on chive.pub now show which other papers cite them, as a graph you can move around in. We extract references from each PDF with grobid (github.com/grobidOrg/grobid) and match them against what's indexed.
That post is talking specifically about layers.pub datasets, which are collections of ATProto records. Papers can point to DOIs (inside the publishedVersion field). We don’t mint DOIs however, so they need to come from some other source.
Re: bioRxiv, do you just mean an indexed import source? If so, there are some challenges with the way the bioRxiv API is set up, but we can look into workarounds if there’s interest. A simple “enter the DOI to get started” should be straightforward, it’s automated import suggestions that are harder.