- MongoDB document database for flexible data storage
- Flexible schemas for various JWST data types
- Support for metadata and processing results
- Proper indexing for performance
Primary document model for all JWST data records.
Core Fields:
id: MongoDB ObjectIdfileName,filePath,fileSize,fileFormatdataType: image, sensor, spectral, metadata, calibration, rawprocessingStatus: pending, processing, completed, faileduploadDate,tags,description
Lineage Fields:
processingLevel: L1, L2a, L2b, L3, unknownobservationBaseId: Groups related files (e.g., "jw02733-o001_t001_nircam")exposureId: Fine-grained lineage trackingparentId,derivedFrom: Parent-child relationships
Access Control Fields:
userId: Owner of the record (null for MAST scan imports)isPublic: true for MAST-imported data, false for user uploads (controls anonymous visibility)
MAST Import Fields:
metadata: Dictionary withmast_*prefixed fields from MASTisViewable: true for image files, false for tables/catalogs
Storage Fields:
filePath: Relative storage key (e.g.,mast/{obs_id}/file.fits), not an absolute filesystem path. Resolved at runtime by the active storage provider (local or S3).
Image-specific metadata attached to JwstDataModel.
Astronomical Fields:
targetName: Object name (e.g., "NGC-3132")instrument,filter,exposureTimeobservationDate: Converted from MAST MJD formatcoordinateSystem,wcs: World coordinate system
MAST-Specific Fields:
wavelengthRange: "INFRARED", "OPTICAL", "UV"calibrationLevel: MAST calib_level (0-4)proposalId,proposalPi: JWST program infoobservationTitle: Program title
instrument,wavelength,dataPointssamplingRate,integrationTime,detectorType
algorithm,processedDate,statusparameters,results,outputFilePath
- Connection string: mongodb://admin:password@mongodb:27017
- Database name: jwst_data_analysis
- Collection: jwst_data
- image: Astronomical images (FITS, JPG, PNG, TIFF)
- sensor: Raw sensor data
- spectral: Spectral analysis data
- metadata: Descriptive information
- Use flexible document structure for metadata
- Implement proper validation
- Support for file paths and processing status
- Include user and timestamp information
- Implement proper indexing for search operations
- Use efficient queries for large datasets
- Consider data archiving strategies
- Implement proper error handling for database operations
- Current credentials are development-only
- Implement proper access control in production
- Use connection string encryption
- Implement proper backup strategies