before I worked at Bluesky, I worked with scholarly metadata and infrastructure.
that field has had it's chain jerked around a lot w/r/t funding and sustainability of infra: maintenance, enclosure, M&A / consolidation, enshittification, grants, collective action, etc.
not dissimilar to web!
that field has had it's chain jerked around a lot w/r/t funding and sustainability of infra: maintenance, enclosure, M&A / consolidation, enshittification, grants, collective action, etc.
not dissimilar to web!
Comments
it was called Zingku and got acquired by Google afterwards.
my techbro creds are stronger than I remembered
no orgs/projects meet all these, but a bunch to mull on around funding / goals / governance. helpful for framing trust conversations
they have interesting graduated API limits/norms:
https://www.crossref.org/documentation/retrieve-metadata/rest-api/tips-for-using-the-crossref-rest-api/
https://github.com/CrossRef/rest-api-doc?tab=readme-ov-file#etiquette
@bmann.ca @chadkoh.com interested in funding models and sustainability
@hdevalence.bsky.social maybe we are speed-running this history instead of speed-running blockchain
http://www.aaronsw.com/weblog/oclcreply
https://youtu.be/zQuIjwcEPv8?t=592
but there are quieter tensions in library world.
book metadata in wikidata and Harvard Libraries dumping metadata are more recent events/movements
founding of https://datacite.org as more accessible/cheap alternative to crossref
governance and cost model of https://doi.org system overall, some similarities to DNS
google scholar dominating but closed metadata (and locked closed by early publisher contracts)
https://openalex.org good support for loading and updates:
https://docs.openalex.org/download-all-data/openalex-snapshot
open "event stream" APIs: https://www.crossref.org/services/event-data/
ResourceSync as a more sophisticated sitemap.xml for doing both bulk transfer and updates
https://www.dlib.org/dlib/january13/klein/01klein.html