Changes between Version 6 and Version 7 of Modules/Batches


Ignore:
Timestamp:
2011-01-24T12:48:30+01:00 (14 years ago)
Author:
JLundberg
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Modules/Batches

    v6 v7  
    1515
    1616>MS: do you want to make batch available in the standard screens?
     17>> Eventually yes, but not for the first version.
    1718
    1819== Technical Implementation ==
    … …  
    2021
    2122>MS: The batches should be stored in the database, then inside the core model you could add an entity 'MolgenisBatch' to describe the batches (optionally, including a query) and an entity 'MolgenisBatchElement' with three fields 'batchId, entityType, objectId' to hold manually selected elements.
    22 
     23>> We don't agree - at least for the first version we want to keep it simple and not involve the database. If a record is needed from the batch, we agreed that a shared protocolApplication could be made which links back to the entities that were in a batch. Furthermore, if a user logins out and then logs back in, the batch will still be there, assuming the application is still running (which is the idea of a web application).
    2324If we were to support multiple Batches, we could make the map consist of User ID as the key and a list of lists of Batches as values. But how can we then find the right Batch, i.e. the Batch the user wants to work with at that moment?
    2425