Custom Query (40 matches)
Results (10 - 12 of 40)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10 | fixed | Export sample-tag file for exported sequences | robert@… | robert@… |
| Description |
Should be tab delimited, with two columns and column headers 'Sequence' and 'Samplename' |
|||
| #11 | fixed | Export excel file with metadata about samples | robert@… | robert@… |
| Description |
With samples in columns, and data about samples in rows |
|||
| #12 | fixed | Improve synchronization | robert@… | robert@… |
| Description |
Synchronization with GSCF now works by retrieving all data always (since we don't know whether anything has changed). This takes a lot of REST calls, and could be improved. If GSCF would notice the modules of changes in studies or assays, the module wouldn't have to do so much rest calls. It could be done like this: GSCF calls module/rest/invalidate?studyToken=ABC when study ABC is changed. The module now knows that the study should be synchronized. The module can decide to synchronize immediately or wait until the given study is asked asked for (e.g. by marking the study as dirty). This also works for new and deleted studies: when the module synchronizes, it will notice whether a study is new, changed or deleted. |
|||
