File formats

Files can be saved into binary and text format. The text format is intended to help communication with other applications and combining of data from several sources. Mimosa also uses two text file formats (.ini and .cfw) to store templates and settings.

Mimosa binary files (.mfw)

Mimosa utilises its own sophisticated database system, which is not record-based. The reason is that all elements in this database are dependent on each other (courses, components, timetable items and so on), and therefore a traditional record-based approach cannot be applied, since it violates the integrity of the items. This means that you cannot edit or extract any item of the database without endangering to break its structure.

Mimosa uses the extension .mfw for its own binary file format, which is normally very efficient to read into the application and write back on disc. Modification of this file is not possible with text editors or other applications. Mimosa can manage only one binary file at the time, and when users want to import or add other files, they have to be first stored in text format. This can be done in selection File|File Export or using a specially designed application to create this file.

Mimosa text files (.mxt)

Commands like File|Network, File|File Import, File|File Export, File|File Add and File|File Split use the text format with the extension .mxt instead. Files with this format are easy to manipulate with other applications and they can be saved into the binary format with commands File|Save as and File|Save after they have been read into Mimosa. After storing a Mimosa file in text format, its structure can be viewed by all text editor applications. Note that it is also possible to import data into Mimosa easily via Clipboard.

Structure of the text files:

The text file consists of lines divided into sections, such as in the Windows .INI files. The best way to study it is to save the data into text format (File|File Export) and load the file into a text editor. Lines beginning with a semicolon (;) are interpreted as comments. Otherwise, the semicolon (;) is used as a separator between fields. It is recommended not to use this character in codes or names.

[Header]

Version=...
Created=...
Customer=...
Department=...
Copyright=[C] Mimosa Software Ltd.
Comment=...
Description=...

[Time]

MaxWeeks=1...255
MaxDays=1...7
MaxLectures=1...30
Date=36031
YYYYMMDD=19980824
FirstWeek=1...MaxWeeks
Days=Mon$Tue$Wed$Thu$Fri$Sat$Sun$

[Timeperiods]

1=(Time1)
2=(Time2)
3=(Time3)
...

[Weeks]

1=(length1);(Name1)
2=(length2);(Name2)
3=(length3);(Name3)
...

[Blocks]

1=(BlockPattern1)
2=(BlockPattern2)
3=(BlockPattern3)
...

[Courses]

Categories=1:Small groups$2:Big groups$3:Voluntary$ $ $ $ $
Bookings=/////$//2//$//3//$
Default=1

[Components]

Categories=C:Classes$T:Teachers$R:Rooms$S:Students$ $ $ $
Bookings=/////$//2//$//3//$
Default=1
NoTimetables=0/1;0/1;0/1;0/1;0/1;0/1;0/1;
NoGaps=0/1;0/1;0/1;0/1;0/1;0/1;0/1;
Rooms=3

[Coursedata]

1=(Course1);(Name1);(Category1);(MAX1);(Locked1:0/1);(Colour1)
2=(Course2);(Name2);(Category2);(MAX2);(Locked2:0/1);(Colour2)
3=(Course3);(Name3);(Category3);(MAX3);(Locked3:0/1);(Colour3)
...

[Componentdata]

1=(Component1);(Name1);(Category1);(MAX1);(Colour1)
2=(Component2);(Name2);(Category2);(MAX2);(Colour2)
3=(Component3);(Name3);(Category3);(MAX3);(Colour3)
...

[Collections]

1=(Course1);(Component1)
2=(Course2);(Component2)
3=(Course3);(Component3)
...

[Weeklectures]

1=(Course1);(Minw1);(Maxw1);(Lectures1)
2=(Course2);(Minw2);(Maxw2);(Lectures2)
3=(Course3);(Minw3);(Maxw3);(Lectures3)
...

[Weekbookings]

1=(Course1);(Minw1);(Maxw1);(Type1)
2=(Course2);(Minw2);(Maxw2);(Type2)
3=(Course3);(Minw3);(Maxw3);(Type3)
...

[Tablelectures]

1=(Course1);(Minw1);(Maxw1);(Mind1);(Maxd1);(Minh1);(Maxh1)
2=(Course2);(Minw2);(Maxw2);(Mind2);(Maxd2);(Minh2);(Maxh2)
3=(Course3);(Minw3);(Maxw3);(Mind3);(Maxd3);(Minh3);(Maxh3)
...

[Tablebookings]

1=(Course1);(Minw1);(Maxw1);(Mind1);(Maxd1);(Minh1);(Maxh1);(Type1)
2=(Course2);(Minw2);(Maxw2);(Mind2);(Maxd2);(Minh2);(Maxh2);(Type2)
3=(Course3);(Minw3);(Maxw3);(Mind3);(Maxd3);(Minh3);(Maxh3);(Type3)
...

[Manualrooms]

1=(Course1);(Room1);(Week1);(Day1);(Hour1)
2=(Course2);(Room2);(Week2);(Day2);(Hour2)
3=(Course3);(Room3);(Week3);(Day3);(Hour3)
...

[Coursedates]

1=(Course1);(MinYYYYMMDD1);(MaxYYYYMMDD1);(Lectures1)
2=(Course2);(MinYYYYMMDD2);(MaxYYYYMMDD2);(Lectures2)
3=(Course3);(MinYYYYMMDD3);(MaxYYYYMMDD3);(Lectures3)
...

After using the selections File|File Import, File|File Add or File|Network|Read from Network to add data from another text file, the possible timetable conflicts are automatically checked and removed.

Sample file (.mxt)

[Header]
Version=4001
Created=3/25/2006 11:36 AM
Customer=Mimosa Scheduling School
Department=Timetable Department
Copyright=[C] Mimosa Software Ltd.
Comment=
Description=MIMOSA SCHOOL

[Time]
MaxWeeks=1
MaxDays=5
MaxLectures=10
Date=38942
YYYYMMDD=20060813
FirstWeek=1
WeekSum=42
Days=Monday$Tuesday$Wednesday$Thursday$Friday$Saturday$Sunday$

[Timeperiods]
1=8 am
2=9 am
3=10 am
4=11 am
5=12 pm
6=1 pm
7=2 pm
8=3 pm
9=4 pm
10=5 pm

[Weeks]
1=1;

[Blocks]
1=

[Courses]
Categories=b:Basic$m:Middle$a:Advanced$f:Free choice$$$$
Bookings=/////$Free$Other$
Default=2

[Components]
Categories=C:Classes$T:Teachers$R:Rooms$S:Subjects$P:Students$E:Equipment$O:Other$
Bookings=/////$Meeting$Other$
Default=3
NoTimetables=0;0;0;1;0;0;0;
NoGaps=0;0;1;1;0;1;1;
Rooms=3

[Coursedata]
1=BAS358;Basics of Logistics;1;9;0;12632256
2=MET95;Methods of the Aged;1;10;0;12632256
3=NAV97;Navigation;1;16;0;12632256
4=PRI860;Principles of Project Work;1;8;0;12632256
5=SPH109;Spherical Trigonometry;1;14;0;12632256
6=THE66;Thermodynamics;1;15;0;12632256
7=YOU280;Youth Education and Guidance;1;12;0;12632256

[Componentdata]
1=Form-A;Form-A;1;23;8454143
2=Form-B;Form-B;1;20;8454143
3=Form-C;Form-C;1;50;8454143
4=BEATTY;Beatty, W.;2;36;16750079
5=HARRISON;Harrison, R.;2;31;16750079
6=SPATT;Spatt, E.;2;25;16750079
7=R206;ROOM 206;3;43;11665252
8=R307;ROOM 307;3;23;11665252
9=R329;ROOM 329;3;26;11665252

[Collections]
1=BAS358;Form-A
2=BAS358;Form-C
3=BAS358;HARRISON
4=BAS358;R206
5=MET95;Form-C
6=MET95;SPATT
7=MET95;R329
8=NAV97;Form-C
9=NAV97;BEATTY
10=NAV97;R329
11=PRI860;Form-B
12=PRI860;BEATTY
13=PRI860;HARRISON
14=PRI860;R206
15=PRI860;R307
16=SPH109;Form-A
17=SPH109;HARRISON
18=SPH109;R206
19=THE66;Form-C
20=THE66;SPATT
21=THE66;R307
22=YOU280;Form-B
23=YOU280;BEATTY
24=YOU280;R206

[Weeklectures]
1=BAS358;1;1;9
2=MET95;1;1;10
3=NAV97;1;1;16
4=PRI860;1;1;8
5=SPH109;1;1;14
6=THE66;1;1;15
7=YOU280;1;1;12

[Weekbookings]

[Tablelectures]
1=BAS358;1;1;1;1;1;3
2=BAS358;1;1;2;2;1;3
3=BAS358;1;1;3;3;1;2
4=BAS358;1;1;4;4;9;9
5=MET95;1;1;1;1;4;5
6=MET95;1;1;3;3;3;4
7=MET95;1;1;4;4;1;3
8=MET95;1;1;5;5;1;3
9=NAV97;1;1;1;1;6;7
10=NAV97;1;1;2;2;4;5
11=NAV97;1;1;2;2;9;10
12=NAV97;1;1;3;3;5;6
13=NAV97;1;1;4;4;4;6
14=NAV97;1;1;5;5;4;6
15=NAV97;1;1;5;5;9;10
16=PRI860;1;1;3;3;3;4
17=PRI860;1;1;4;4;1;3
18=PRI860;1;1;5;5;1;3
19=SPH109;1;1;1;1;4;6
20=SPH109;1;1;2;2;4;5
21=SPH109;1;1;3;3;5;6
22=SPH109;1;1;4;4;4;5
23=SPH109;1;1;5;5;4;6
24=SPH109;1;1;5;5;9;10
25=THE66;1;1;1;1;8;10
26=THE66;1;1;2;2;6;8
27=THE66;1;1;3;3;7;10
28=THE66;1;1;4;4;7;8
29=THE66;1;1;4;4;10;10
30=THE66;1;1;5;5;7;8
31=YOU280;1;1;1;1;8;10
32=YOU280;1;1;2;2;6;8
33=YOU280;1;1;3;3;7;8
34=YOU280;1;1;4;4;7;8
35=YOU280;1;1;5;5;7;8

[Tablebookings]

[Manualrooms]

[Coursedates]
1=BAS358;20060813;20060814;9
2=MET95;20060813;20060813;10
3=NAV97;20060813;20060813;16
4=PRI860;20060815;20060813;8
5=SPH109;20060813;20060813;14
6=THE66;20060813;20060813;15
7=YOU280;20060813;20060813;12

Mimosa profile files (.mpf)

In selection File|Profile you can save the current Mimosa settings in a separate files with extension .mpf and read them again into the application, if you want to use them later on. These profile files are copies of the settings.ini file, which is automatically read into Mimosa when it is invoked and where settings are stored when it is exited. This file contains, for instance, the printing and colour selections of users.

Mimosa template files (.cfw)

Mimosa provides several template files that containing the localized names for reports, default categories, days of week, slots and so on. When creating a new Mimosa file, you can select the closest version from the list and also edit and save the files in File|Language selection.

[Weeks]
   1   1 [1]
[Days]
Monday$Tuesday$Wednesday$Thursday$Friday$Saturday$Sunday$
[Bells]
   1 08:00
   2 09:00
   3 10:00
   4 11:00
   5 12:00
   6 13:00
   7 14:00
   8 15:00
   9 16:00
  10 17:00
[Attributes]
   1 n:Normal courses$e:Courses elsewhere$v:Voluntary$m:Meetings$t:Tests$s:Special occasions$$
   2 C:Classes$T:Teachers$R:Rooms$S:Subjects$P:Students$E:Equipment$$
   3 /////$Holiday$Other$/////$Meeting$Other$
   4 216
   5 16
   6 110
[Limits]
   1   8
   2   3
   3   5
   4 255
   5   7
   6  30
   7   1
   8   5
   9  10
[Reports]
   1 List of courses
   2 List of components
   3 Schedules
   4 Courses by components
   5 Components by courses
   6 Compact schedules 
[Months]
[Base]
37004
[Mode]
0
[Words]
   1 COURSES$COMPONENTS$#:$CODE$NAME$*$MAX$WEEKS$OK$LINKS$LEFT$