Health data terminologist - https://careers.veeva.com/job/1ca2b0ee-842f-45c4-a71e-a62e3de04c9e/health-data-terminologist-compass-boston-ma Senior Bioinformaticist - https://job-boards.greenhouse.io/honehealth/jobs/4781839008 Data / Information Architect - https://navaide.breezy.hr/p/f256a7999bf6-data-information-architect-navy-data-model-mdm-ontology-hybrid-role Senior Manager, GPS Knowledge Systems - https://jobs.bms.com/careers?query=knowledge%20graph&pid=137469655829&domain=bms.com Ontology Integration Specialist - https://recruit.hirebridge.com/v3/CareerCenter/v2/details.aspx?cid=8427&jid=889286&bid= Taxonomist - https://recruiting.paylocity.com/recruiting/jobs/Details/2776458/Library-Systems-Services-LLC/Taxonomist LAC - Biomedical Curator/Indexer - https://recruiting.paylocity.com/recruiting/jobs/Details/2916055/Library-Systems-Services-LLC/LAC---Biomedical-CuratorIndexer Senior Data Scientist (NLP) - https://careers.clarivate.com/job/JREQ133644/Senior-Data-Scientist-NLP AI Data Engineer β Data and Knowledge Graphs - https://www.dpr.com/company/careers/current-positions/JR-12219 Senior Software Engineer, Discovery - Semantic Search & RAG - https://job-boards.greenhouse.io/harmonic/jobs/4590189005
Now Hiring: Data Harmonization Specialist / Expert (Remote) Remote β Must reside in Seattle, Boston, Philadelphia, or San Francisco Pay range: $78hr-$85hr/Contract Life Sciences | Bioinformatics | Product Org | Project Management (must be eligible to work on a W2 without sponsorship/NO C2C options) Weβre looking for a Data Harmonization Specialist / Expert to join a growing product team working at the intersection of biology, data, and technology. If you have a strong background in semantic data modeling, bioinformatics, and project management, weβd love to hear from you. π‘ What Youβll Do: β’ Define schemas, ontologies, and controlled vocabularies β’ Harmonize complex scientific data from sources like GEO, ArrayExpress, and single-cell datasets β’ Work closely with product managers and business users to translate requirements into scalable data models β’ Drive projects in an Agile environment and ensure quality, FAIR-aligned data is ready for platform integration β What Weβre Looking For: β’ 5+ years of experience in scientific data modeling or harmonization β’ Strong Python, SQL, and Jupyter skills β’ Familiarity with LinkML, OWL, RDF, and public biomedical ontologies β’ Hands-on project management experience in a product or R&D environment β’ Background in life sciences, bioinformatics, or related field (Bachelorβs required) π» 100% Remote β No onsite requirement π Candidates must be located in: Seattle, Boston, Philadelphia, or San Francisco Reach out to -> https://www.linkedin.com/in/tracey-washburn-250395228 <-------
GSK has several opening for senior knowledge engineers. If you're interested, check them out on their careers portal. I don't believe that these positions are remote.
OGM (assuming object-graph mapper) is the last thing you need when building applications on top of RDF. It requires to keep the object model in sync and basically cancels all the flexibility of the RDF data model
I think that it's entirely product depend! If the schema changes, bit of the UI will most likely change. Maybe a new tab for different analytics, etc. In this case, a new schema can be versioned and the frontend team onboarded. If we're talking generic interfaces that are just showing things in the db (linked data browsers), sure.
In fact the leanest architecture
True, but this feels like a strawman. I like using the power of abstraction that comes from ORM to manage the spaghetti mess that you get when you have a bunch of SPARQL in the UI code. Relational db people aren't forced to write SQL any time they want data for the UI - to me that's a feature not a bug. It's been widely more successful than graph-backed-ui even with impedance mismatch and the world continues to spin.
It's also a proof that RDF-based UI applications do not need to use TypeScript or JavaScript
Proofs are nice. But I don't want to go off proof of concepts for my production products. I want industry standard tools and techniques
Renato I. - do you have any suggestions for GraphQL over RDF? The following writeup is a bit old, and the open source options listed haven't been touched in years https://www.w3.org/Data/events/data-ws-2019/assets/position/Ruben%20Taelman.pdf
+1 for GraphQL. The introspection tools are great
What are the advantages of building applications on top of RDF rather than API endpoints? I've built more than one on top of RDF and found it difficult to keep up with ontology changes. And then it doesn't scale when you have a second webapp doing similar things. Since then, I've sort of convinced myself that no one builds UI apps on top of relational databases (no one says "here's my sql endpoint and my table structure") and caved with API based dev. Unfortunately, the RDF space is behind LPG when it comes to OGM libraries though... I've seen some cool stuff with building widgets based on SHACL, there might be a way for you to incorporate that into your framework ^_^. Pros/cons that you've run across with your work with building UI directly on top of SPARQL endpoints?
https://gnis-ld.org/sparql A linked data version of the USGS GNIS dataset. Check out the example queries here