This is intended to be an editable and versioned catalog of papers and other written research documents, with a focus on identifying and linking specific files (agnostic of location/URL). We have a need for such a database the Archive (existing software and databases didn’t meet our needs), but it feels like many organizations are building such databases and it would be nice to collaborate instead of duplicating work.
I’m posting here to see if anybody had feedback on the data model (sort of git-inspired) or planned editing workflow (simple central database with an API, most policy and behavior implemented by bots; edits are grouped and require approval to be “accepted”). If you could re-implement musicbrainz with all the lessons you’ve learned, how would you do it? What sort of social/community/commentary features do you think are crucial, and which could be left to other side-sites that build on the same API/database?
Hi @bnewbold2, and welcome to the metadata hippie home.
Maybe the @BookBrainz team might be interested in directly collaborating with your project; the #bookbrainz project is also intended for academic papers and articles etc., in my understanding.
About “If you could re-implement musicbrainz with all the lessons you’ve learned, how would you do it? What sort of social/community/commentary features do you think are crucial, and which could be left to other side-sites that build on the same API/database?” I think maybe that’s something for @rob and @bitmap to answer, if they have the time.
PS. fatcat.wiki just shows blank page with JavaScript turned off, and https://qa.fatcat.wiki/ ’s SSL certificate doesn’t actually cover the “qa.fatcat.wiki” (sub)domain. May want to fix that.
Thanks for the poke on the SSL/javascript issues. I removed the javascript junk from https://fatcat.wiki, and updated the link to https://www.qa.fatcat.wiki for the example. I’m using an off-the-shelf framework (Semantic UI) that includes javascript, but I guess if i’m actually committed to supporting no/little javascript I should be testing that from the start.
