Changes between Version 7 and Version 8 of CaTissue


Ignore:
Timestamp:
11/26/10 09:49:25 (13 years ago)
Author:
jeff.lusted
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • CaTissue

    v7 v8  
    1 
     1=== Overview ===
    22From the CaTissue home page:
    33"caTissue Suite is caBIG's biorepository tool for biospecimen inventory management, tracking, and annotation."
    … …  
    55https://cabig.nci.nih.gov/tools/catissuesuite
    66
     7=== BRICCS Needs ===
    78We need to learn how to use the caTissue API. In particular:
    89
    … …  
    1112   * what would it take to be able to process more than one participant at a time through the collection protocol? Currently the submission process includes checking for empty data in form elements which presumably have the same ID in each open tab or window, thus throwing an error.
    1213
    13  = = =
     14While we work with 1.1.2p5, it might be useful to know that there is a pre-built VM with caTissue 1.2 (the next version) available here:
    1415
     16https://cabig-kc.nci.nih.gov/Biospecimen/KC/index.php/2010_User_Meeting_VM
     17
     18This was used during the Houston User Meeting. I know it works on Ubuntu host, using !VirtualBox. YMMV.
     19
     20Demo files for using the caTissue API are here: https://cabig-kc.nci.nih.gov/Biospecimen/uploaded_files/4/4c/APIDemo1.1.zip
     21
     22And files demonstrating the bulk operations feature of caTissue are here: https://cabig-kc.nci.nih.gov/Biospecimen/uploaded_files/1/19/BO_-_Loading_Data_Session.zip
     23
     24The following pages are working notes:
     25* [wiki:CaTissueClientAPI Client API]
     26* [wiki:CaTissueBulkOperations Bulk Operations]
     27
     28=== User Privileges ===
    1529A note on user privileges in caTissue from Jeff. It is not our favoured model of privileges, but probably defined in the caBIG CSM (Common Security Model). We'd like more fine-grain privileges, but in the meantime this is how it works:
    1630
    … …  
    1933"I (naively) thought that setting up privileges for each individual user would suffice. Seems reasonable. Then the penny dropped. What if I were doing admin on the protocol and wanted to stop people using it whilst changes were underway? If I were relying upon individual user privileges alone, I would have to go into each user and change their privilege, then do the protocol admin, then go back into each user again to re-enable their use. Very tedious. The way it is set up in caTissue, I can disable / enable wholesale privileges for one protocol with one admin action. Quite clever?"
    2034
    21  = = =
    2235
    23 Storage location structure:
     36=== Storage location structure: ===
    2437
    2538
    26 BRICCS Collection Protocol:
     39=== BRICCS Collection Protocol: ===
    2740
    2841A BRICCS 'initial db' dump was taken during system set-up, after creating the storage hierarchy and CP but before populating with any specimen, and submitted to svn using the following command:
    … …  
    3043
    3144
    32  = = =
    33 
    34 While we work with 1.1.2p5, it might be useful to know that there is a pre-built VM with caTissue 1.2 (the next version) available here:
    35 
    36 https://cabig-kc.nci.nih.gov/Biospecimen/KC/index.php/2010_User_Meeting_VM
    37 
    38 This was used during the Houston User Meeting. I know it works on Ubuntu host, using VirtualBox. YMMV.
    39 
    40 Demo files for using the caTissue API are here: https://cabig-kc.nci.nih.gov/Biospecimen/uploaded_files/4/4c/APIDemo1.1.zip
    41 
    42 And files demonstrating the bulk operations feature of caTissue are here: https://cabig-kc.nci.nih.gov/Biospecimen/uploaded_files/1/19/BO_-_Loading_Data_Session.zip