Opened 17 years ago
Closed 17 years ago
#721 closed task (fixed)
Store data in files instead of in the database
Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
---|---|---|---|
Priority: | critical | Milestone: | BASE 2.5 |
Component: | core | Version: | |
Keywords: | Cc: |
Description (last modified by )
As I see it there are four basic problems:
- Make it possible to select files in the GUI in a flexible way. For example, if we are doing Affymetrix experiments, we should be able to select CEL and CDF files. If we are doing other experiments there are other types of files. We need the concept of a "platform" and some information about what types of files are used. Platforms can be managed by server adminitrators.
- We must of course be able to store the selected files and link them to the items the relate to. For example: the CEL file to a raw bioassay and the CDF file to an array design. Are there other item types that may need files?
- Read metadata from the files. We want file storage to be equivalent to database storage, so we need a way to extract metadata from the files. For example the number of features for an array design and the number of spots and file headers for a raw bioassay. Should the extraction of metadata be required or optional? It will be easier for users to start with a new platform if it is optional. Downstream features must be aware of this and handle three cases: no files at all, files are present but no metadata, both files and metadata is present.
- Import data to the database. Actually, I don't know if this is a problem or not. The existing import plug-ins could be used in this case. A slight modification is probably needed since they should use the file the user selected in step 1. It should be possible to have the data both in the database and in the file(s).
For more information:
- Database/UML schema
- Core API : Using files to store data
- Default platforms installed with BASE
- The older draft may still have some relevant information.
- The discussion on the mailing list
Change History (36)
comment:1 by , 17 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 17 years ago
Description: | modified (diff) |
---|
comment:3 by , 17 years ago
comment:4 by , 17 years ago
Description: | modified (diff) |
---|
comment:5 by , 17 years ago
Description: | modified (diff) |
---|
comment:6 by , 17 years ago
comment:7 by , 17 years ago
Description: | modified (diff) |
---|
comment:8 by , 17 years ago
Description: | modified (diff) |
---|
comment:9 by , 17 years ago
comment:10 by , 17 years ago
comment:11 by , 17 years ago
comment:13 by , 17 years ago
comment:15 by , 17 years ago
comment:16 by , 17 years ago
comment:17 by , 17 years ago
comment:18 by , 17 years ago
(In [3804]) References #721: Most things for attaching files to array designs are now in place.
- Added update script for updating existing installations
- Re-coded parts of the code that depended on depracated methods
- Changed depracated methods to be backwards compatible
- Plugins that import to or use array designs can now use the attached files
comment:19 by , 17 years ago
comment:20 by , 17 years ago
comment:21 by , 17 years ago
comment:22 by , 17 years ago
comment:23 by , 17 years ago
comment:25 by , 17 years ago
comment:26 by , 17 years ago
comment:27 by , 17 years ago
(In [3852]) References #721: Auto-detect function is now aware of FileStoreEnabled items and automatically selects a default file for import.
comment:28 by , 17 years ago
comment:29 by , 17 years ago
comment:30 by , 17 years ago
comment:31 by , 17 years ago
comment:32 by , 17 years ago
comment:33 by , 17 years ago
comment:34 by , 17 years ago
comment:35 by , 17 years ago
comment:36 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
(In [3681]) References #721: Store data in files instead of in the database
First draft of a specification/implementation design