DARKS and FLATS will not create entries in DB. If I will ever hold something in the database, this will be only master dark and flats.

I'll drop epoch from RTS2 - whole idea was in my recent point of view wrong and just create added complexity for already very complex system, and do not bring significant benefits. Instrument changes (for which epoch was originally though) can be written to FITS keywords (e.g. in INSTRUME, which is configurable from rts2.ini).

New default expected image path will be:

/<base>/YYYY/MM/NN/OBSID/CC_hhmmss_sss.fits

So for example we will have:

/images/2008/08/12/012345/C0_033545_123.fits

All other image informations (dark, flat, ..) will be located only in header.

rts2-image tool can be used for movement of the images to other locations.

If needed, imagebase can be used for epochs, although that use will create mess in database → path calculation and is not recommended.

This change will be done for 0.8.0 release, and will be coded (and then tested) in separated branch, before it will enter trunk.