This is just an idea, but what about, instead of tracking entries, sources, and syllabi in the current method, with org-roam, we use Turtle, the terse RDF triple syntax?
This would mean using a bibliographic ontology, and a curriculum/syllabus ontology. Here are some I dug up:
<info:doi/10.1134/S0003683806040089> a bibo:Article ;
dc:title "Effect of argillaceous minerals on the growth of phosphate-mobilizing bacteria Bacillus subtilis"@en ;
dc:date "2006-01-01" ;
dc:isPartOf <urn:issn:23346587> ;
bibo:volume "42" ;
bibo:issue "4" ;
bibo:pageStart "388" ;
bibo:pageEnd "391" ;
dc:creator <http://examples.net/contributors/2> ;
dc:creator <http://examples.net/contributors/1> ;
bibo:authorList ( <http://examples.net/contributors/2> <http://examples.net/contributors/1>) .
<urn:issn:23346587> a bibo:Journal ;
dc:title "Applied Biochemistry and Microbiology"@en ;
bibo:shortTitle "App Biochem and Biol"@en .
There are tools out there for converting from BibTex to RDF, which can then easily be converted to Turtle, but it might be just as well to script up something that does this.
This is just an idea, but what about, instead of tracking entries, sources, and syllabi in the current method, with org-roam, we use Turtle, the terse RDF triple syntax?
This would mean using a bibliographic ontology, and a curriculum/syllabus ontology. Here are some I dug up:
Here's an example bibliographic entry from the bibliographic ontology:
There are tools out there for converting from BibTex to RDF, which can then easily be converted to Turtle, but it might be just as well to script up something that does this.