New topic for our Results BPG -- Required Fields. One of the CSMs asked if we could make a resource on this and we happily obliged 😊 Do you use required fields on your Results Schemas? Why or why not?
@Melissa DiTucci , I’d love to hear more about successful cases for version control of Benchling results, and creating team-based results, implementing tighter permissions around results. These are both topics of interest to Novozymes at this time. Could there be an expanded conversation and/or blog post with examples?
@Chantelle
Absolutely! I’ll put something together sometime in August. I’m excited to hear how other folks think about this but I definitely have some opinions. Like many answers to questions about Benchling “it depends” but I can absolutely show pros, cons, and considerations for different methods 🙃
How do I export results? For instance, there’s a results table that we use for every single project in our company, that up until now one of the fields has always had the same units, so we never bothered to capture that information. Now we want to include a different units option. My plan is to just add a column where users can capture this data, but I will also need to retroactively update existing results. While I could easily do this with entities, I have no idea how to do this for results. TIA
@LauraTRondoTX I’ve brought this idea up in the past , and currently there’s no nice way to achieve this. Depending on the number of existing results that need updating, I would suggest either:
Low-medium number of results - archive and resubmit via the Benchling UI (Entries) where the results are submitted. large number of results - bulk archive and bulk submit via the API/SDK.
@kyleweise thanks for the response and the link to your previous post (helpful!).
In this instance, I’d be dealing with a rather large number of results (thousands to possibly tens of thousands - I’m not entirely sure, since I also still haven’t figured out how to get a visual on/export these data), so I’ll have to go the second route… but I am a bench scientist who still can’t remember (regardless of looking it up multiple times) what API stands for, let alone how to use it.
After reading your post, I think I’m better off just implementing a “from this point on, add this extra set of info” tact.