clarification on validation script and 10.3: /home/Support/LabKey Support Forum

clarification on validation script and 10.3

LabKey Support Forum (Inactive)

View Message

clarification on validation script and 10.3

Ben Bimber

2010-11-15 10:38

Status: Closed

hello,

I am hoping I can clarify the expected behavior of when/where validation scripts will be run, as of 10.3:

there are 4 categories of tables I'm inserted in:
Datasets
Lists
Assays
Hard tables in an external schema

There are several questions I have for each type of table:

1. should validation scripts work at all
2. are there any potential import scenarios under which the validation script will not run? the import types I know about are:
-single sample 'Insert New'
-excel batch upload 'Import Data'
-http APIs. includes JS, R, perl
-pipeline import for lists or datasets

I would like to figure out all above scenarios where the validation script would NOT run. the ones I know about are:

1. validation scripts will not run at all for assays. this has probably not changed.
2. pre-10.3, it would not run for any sort of excel-based import on any table type
3. pre-10.3, it was not hooked up to hard tables in external schemas
4. pre-10.3, i didnt think they worked on lists either

Are the above accurate in 10.3?

kevink responded:	2010-11-15 12:13
Hi Ben, Here is a table showing the current availability of the validation/transformation scripts: https://www.labkey.org/wiki/home/Documentation/page.view?name=transformScriptAvailability From that chart you can see assays are not supported yet anywhere and the bulk html import (pasting into the html textarea) is also not supported. For the other data types, the support isn't across the board yet. We plan to address the issue in 11.1.

Ben Bimber responded:	2010-11-15 12:16
ok, that's helpful. one more question: for datasets, the file name of the script is picky. It needs to use the dataset label (not name) and spaces need to be replaced with underscores. should i expect the same rules to apply to other table types? most other tables only have one name (as opposed to label+name), so this quirk would not apply to all.

kevink responded:	2010-11-15 12:28
I fixed the naming issues recently for script files. You should be able to name the script using the same conventions used with the .qview.xml and other query files.