Here's the URL from Data Views (gives default view): There appears to be an error in the URL that is generated by the Data Views. When we click on the custom view name in the Data Views webpart, we get the default view of the query instead. We have a query with a saved custom view. Primary specimen aliquoted into an unexpectedly large number of vials, based on protocol expectations for specimen volume (indicating a possibly incorrect participantID, visit, or type for one or more subset of vials). Examples of QC problems that could be detected with this method include: A saliva specimen present in a protocol that only collects blood (indicating a possibly incorrect protocol or primary type). Vials or primary specimens that meet user-specified protocol-specific criteria are flagged. Could someone point me in the right direction? The excerpt below (from the help documentation) implies that this might be possible, but I can't figure out how to do it. I would like to be able to flag certain specimens upon import, either by explicitly setting the flags in the tsv file, or via a query that identifies vials and flags them (similar to the way I can set up queries that determine "Requestability Rules" and mark vials accordingly). Second, the Ext.Loader will work you just have to ensure to configure it before use. First, I'd recommend trying to use our dependency loading structure implemented in 12.2. In the case of the Ext4Store I'd recommend using our JavaScript Query API and populating data stores directly.ģ. Currently, the classes found in internal/webapp/extWidgets are not considered part of our publicly supported API and as such I would not recommend using them for production environment apps. When we do have public API wrapped for ExtJS 4+ components we will expose these docs publicly.Ģ. It's not available in production environments but you can access it by turning it on under "Admin Console" > "Experimental Features" > "JavaScript Documentation" in your local instance. We've implemented an experimental feature for ExtJS documentation moving forward that uses JSDuck (thanks to your recommendation). Thanks, Brianįirefox 3.5 now supported for Selenium testing of LabKeyġ. What's the proper way to do this programatically? I'd rather not hand users a list of manual steps for restarting a cluster (or for that matter for building an initial LabKey AMI). If you have set up SSL on your FTP server, check the box. In the Configure File System Server section, fill in the server name and the port for the FTP server. Go to the Site Settings (Manage Site->Admin Console->site settings). Thus there are things like this: (from ) Configuring LabKey Server to use the FTP Server Finally, you need to tell LabKey Server that there is a FTP server that it should tell users about. An important thing about AWS, as you point out, is the fact that IP addresses and FQDNs shift whenever you take an instance down and replace it with another (well, there are elastic IPs etc, but set that aside for now).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |