1. First of all, thank you
2. Yes, we do. I'd first look at:
(a) data set: Biotech is a broad area. We'd love to understand the specific use case. We have 50M entities in Doqume today, but we constantly work to integrate or build new sets.
(b) work with the content resource: some journals are open, some not. If the abstract has enough information that's usually a good place to start. Otherwise we look at each journal and evaluate next steps.
(c) build the engine. There can be very different needs there. I've covered some of it in the article, but let me know if you have any questions I'll be happy to tell you more.
3. Yes, we do.
Feel free to write me: vaidotas [at] doqume [dot] com. And congrats for your startup project!
I have a bit different approach in the way I structure the information, which is both limiting, but also useful to a set of problems.
Essentially, I built a content ranking system, which is a fair amount different than Google or your system. It's also patent pending, but I don't think necessary for what you're building at the moment.
Thank you, davePlug! A bit of both. We offer APIs that help integrate Doqume's semantic technology into enterprise use cases. But the Research Engine and Query Tool piece of it is a SaaS.
We built a very similar product (I think). We took a fundamentally different approach, but I'd be happy to share what did / didn't work for me. Take it for what it's worth though, I'm still bootstrapping myself.
My contact info should be discoverable from my profile.
This helps a ton. Thanks. Is there any reason you can think of why you don't go back to old posts, maybe a UI/UX issue or too much content to read?
Also, can you maybe tell more about those subfields? Examples that would give a better sense of how those readings help with your work would help.
1. First of all, thank you 2. Yes, we do. I'd first look at: (a) data set: Biotech is a broad area. We'd love to understand the specific use case. We have 50M entities in Doqume today, but we constantly work to integrate or build new sets. (b) work with the content resource: some journals are open, some not. If the abstract has enough information that's usually a good place to start. Otherwise we look at each journal and evaluate next steps. (c) build the engine. There can be very different needs there. I've covered some of it in the article, but let me know if you have any questions I'll be happy to tell you more. 3. Yes, we do.
Feel free to write me: vaidotas [at] doqume [dot] com. And congrats for your startup project!
Cheers, Vai.