Changes between Initial Version and Version 5 of Ticket #979


Ignore:
Timestamp:
Nov 17, 2008, 1:18:34 PM (16 years ago)
Author:
Nicklas Nordborg
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #979

    • Property MilestoneBASE 2.10
    • Property Owner everyone removed
    • Property Priority majorcritical
  • Ticket #979 – Description

    initial v5  
    33'''Main features:'''
    44 * Create !BioPlates with wells that can hold Biomaterial items.[[br]]
    5  * !BioPlates will have Plate type that in turn will have Geometry.[[br]]
     5 * !BioPlates have a Geometry (re-use from Array LIMS).[[br]]
    66 * Organize Biomaterials in !BioPlates by moving/removing them to/from a well of a !BioPlate, i.e., a biomaterial item can exist outside of a well or in a well. NOTE: in the regular table views of biomaterials all items should be viewable (both those in and outside of !BioPlate wells). !BioPlate and !BioPlateWell could be columns in the view tables.[[br]]
    77 * Create new biomaterial directly into a !BioPlate well. For example, from an existing biomaterial, pointing to a !BioPlate well can create a child biomaterial in that well. Thus, a user has the option to move a biomaterial into a well or to create a child biomaterial in a well.[[br]]
    8  * Manage biomaterial by !BioPlate, i.e., mapping an entire !BioPlate to a daughter !BioPlate and in the process evoke processing events applied to biomaterials in the wells. The processing events should include regular transformations applicable to biomaterials, e.g., samples can be processed into new samples or into extracts. When a transformation is performed, the user can specify properties, e.g., Protocol, Original quantity, and Created date, which are then applied to all well biomaterials (child name can follow current naming procedures). NOTE: when processing biomaterials by !BioPlate a limitation could be set that only a !BioPlates holding a single biomaterial type, e.g., samples or extracts, can be transformed (or defaults/parameters would have to be set per biomaterial type).[[br]]
    9  * Mapping of labeled extracts in !BioPlate to array indices of Hybridization. One or more wells form a !BioPlate holding labeled extracts could be mapped to a specified Hybridization. By specifying the source wells, the destination hybridization, and how mapping should be performed, labeled extracts could be associated to hybridizations. For example, from a 96-well !BioPlate, all labeled extracts could be mapped to a Hybridization having 96 arrays. Correspondingly, from a 96-well !BioPlate, labeled extracts from wells 1-6 could be mapped to array indices 1-6 of a Hybridization having 6 arrays.[[br]]
    108
    11 '''Creating geometries, plate types, plates and mappings:'''[[br]]
    12 From a BioLIMS menu one would access functionality to create !BioPlate types, !BioPlate geometries, and corresponding !BioPlates that can hold biomaterials. Essentially, for these functions one would have the same interface as for ArrayLIMS with the exception that users should be able to create individual plates by clicking  a “New…”  button (for Array LIMS plates are always uploaded from file). Possibly, functions from ArrayLIMS could be reused to a certain extent.[[br]]
     9'''Creating plates:'''[[br]]
     10From a BioLIMS menu one would access functionality to create   !BioPlates that can hold biomaterials. Essentially, for these functions one would have the same interface as for ArrayLIMS with the exception that users should be able to create individual plates by clicking  a “New…”  button (for Array LIMS plates are always uploaded from file). [[br]]
    1311
    1412'''Managing BioPlates:'''[[br]]
    15 Table views for !BioPlates should be available and can basically have the same layout as table view for ArrayLIMS plates. !BioPlate view table can be available from the BioLIMS menu or from the regular view menu. Single !BioPlate view could share layout with single ArrayLIMS plate view with tabs for properties, annotations, events, and wells. Additional action button (!BioPlateAct) to remove/add biomaterials would be needed. This interface could perhaps be similar to that of how items are shared to other users/groups/projects (in that biomaterials could be considered members of a well). A similar !BioPlateAct button could be placed in the biomaterial table views.
     13Table views for !BioPlates should be available and can basically have the same layout as table view for ArrayLIMS plates. !BioPlate view table can be available from the BioLIMS menu or from the regular view menu. Single !BioPlate view could share layout with single ArrayLIMS plate view with tabs for properties, annotations,  and wells. Additional action button (!BioPlateAct) to remove/add biomaterials would be needed.
    1614Importantly, in the regular table views of biomaterials all items should be viewable (both those in and outside of !BioPlate wells). !BioPlate and !BioPlateWell could be columns in the view tables.[[br]]
    1715
    18 '''Track tab - tracking biomaterial lineage:'''[[br]]
    19 Currently, the single biomaterial item view holds a tab with events. The events tab list events for the appropriate single item. An additional tab “Track” could be added. This tab would hold an overview, presenting the lineage for the item, i.e., the chain of items backwards starting with parents and downwards starting with children. In this overview, the BioLIMS should be included and for lineage items harbored in !BioPlates the !BioPlates and !BioPlateWells should be indicated.[[br]]
    2016
    21 '''Experimental overview:'''[[br]]
    22 As BioLIMS mearly constitutes optional biomaterial management functionality, !BioPlates should not appear or affect the current experimental overview. Naturally, biomaterials are tracked trough the experiment overview irrespectively of whether they exist in !BioPlates or not, and irrespectively of whether they were created by !BioPlate. Thus, biomaterial properties are not linked to !BioPlate transformations, rather !BioPlate transformations set biomaterial properties.
    23