Use of Non-Standard Study APIs | trent | 2012-05-20 20:08 |
Status: Closed | ||
Hi, You previously mentioned that if we use un-documented APIs to let you know, so you can make a note not to modify, or to provide fall-back functionality. Hope there is no issue with using these? 1. createParticipantCategory of the participant-group module. e.g. LABKEY.ActionURL.buildURL("participant-group", "createParticipantCategory", LABKEY.ActionURL.getContainer()); Reasoning - each specimen request really translates to sub study (Ancillary), so wanted an easy way to create a participant group based on any participants involved in a specimen request. Build a grid view with participants involved in each request (can be filtered by request id), and posting the selected rows (participantId) to this API to create the group with the listed participants. (^^already mentioned this via e-mail, but just duplicating here^^) 2. handleUpdateRequestInputs.post of the study-samples module. e.g. LABKEY.ActionURL.buildURL("study-samples", "handleUpdateRequestInputs.post", LABKEY.ActionURL.getContainer()) Reasoning - We have a standard concept sheet/request form that includes approx. 25 input fields, that would be used for all studies imported into LabKey - with possible slight variations amongst studies. Possibly in-efficient and error prone to have a labkey admin manually enter all those fields for each study. Cheers |
||