This error message has been seen in the web after trying to update a barcode using that action. This has been forwarded on to Progeny. They are looking into it, but said that you should be able to log back in after a few minutes and the lock will be released.
If you get an error message like the one below in Progeny web when you edit information in a sample data sheet, try clicking on the datasheet outside of the field you are editing before closing out and that should take care of it. (more…)
Where do you usually go for help when you have a problem with Progeny?
The prematurity database is now set up with actions for LIMS. Please start using them when processing and storing samples!
This post is only important to those who create computed fields in progeny. That should really just be study coordinators and possibly a very few highly responsible individuals who communicate such field making/changing with the study coordinators.
If you need to change an existing field into a computed field in progeny, please start the computed field as a completely new field and delete the old one rather than changing the field type on an existing field. When you change the field type of an existing field to a computed field it will cause a database error. The field won’t work and it will interfere with things like how the individual or sample data sheets are displayed or how LIMS actions/reactions that utilize that field work. If it happens, we just need to delete the field everywhere that it is referenced, so it isn’t the end of the world, but it is better if we just avoid the problem all together! Thanks.
I have gotten some questions recently about problems people are having with genotype imports and thought this would be a good time to send a reminder out about some of the basics of genotype importing into progeny since there are a lot of new people and the details don’t always get passed on or are forgotten.
Anyone can come to me with additional questions, but the thing I wanted to remind everyone about is performing error checks. When you select to check for mendelian errors, or discrepancies you should check the corresponding tab for those types of errors at the end of the import to see if you have any errors and to resolve them if possible. (See screen shot below)
You should always check for:
1) Rejected genotypes: This will tell you if some of your genotypes were not entered. (examples of possible reasons include a typo in the sample or marker name or your marker is not in the set you selected to import into)
2) Discrepancies: If someone else has already typed the marker you are typing or if you re-run a plate or re-process a plate and re-import, there may be differences in what was in progeny and what you are trying to put in. When you select to check for discrepancies Progeny will keep the original data unless you resolve the discrepancy. I am telling you this because someone recently incorrectly processed plates and imported, then re-processed and re-imported, but was still getting the original (wrong) genotypes out for analysis. The reason was that the original genotypes were still in the database and the new (discrepant) genotypes were being held, waiting for confirmation of whether or not they should overwrite the existing genotypes. In order to overwrite existing genotypes, you must either a) resolve discrepancies, or b) not select to check for discrepancies (new genotypes will automatically overwrite what is in progeny).
Here is an example of the genotype import page. Notice the tabs across the bottom with the different types of error checks that you should review. The Progeny user manual also has more in depth information about this. Feel free to ask me any questions about this.
Jamie
Subscribe