Import, merge and export data with text files

Files can be saved into binary and text format. The Mimosa text format (.mxt) is intended to help communication with other applications and combining or merging of data between several Mimosa users. This simple text file format - or its subsets - serves also as API (Application Programming Interface), enabling other applications to communicate with Mimosa, either directly or with slight modifications.

Mimosa supports also well-known standard file formats Comma Separated Values (.csv), iCalendar (.ics) and vCalendar (.vcs) enabling to convert and migrate Mimosa timetables to several other applications, web-based appointment sites and mobile phones. Use the selection File|File Export|Other file formats to convert your Mimosa timetables to any of these file formats.

Applications supporting the file formats above include for example the following: Apple iCal, Facebook, Google Calendar, Lotus Notes, Mobile devices, Microsoft Entourage, Microsoft Exchange Server, Microsoft Office Outlook, Microsoft Works Calendar, Mozilla Thunderbird, Moodle, Novell Groupwise, Windows Calendar, Windows Live Calendar and Yahoo Calendar. Also several mobile devices can read/write files using at least one of these formats.

Summary of supported file formats
DescriptionSelectionsExtensionExportImportInternalDescription
Mimosa binary files File|New, File|Open, File|Save,
File|Save as, File|Extract week
.mfwNoNoYes Files accessed only by Mimosa (Site and Single User Licence), Mimosa Free and Mimosa Trial versions
Mimosa Pro binary files File|New, File|Open, File|Save,
File|Save as, File|Extract week
.mfzNoNoYes Files accessed only by Mimosa Pro
Mimosa text files File|File Import, File|File Export, File|File Add,
File|File Split, File|Network
.mxtYesYesNo Contains all contents of .mfw and .mfz files in text format, used to
1) merge two or more Mimosa files
2) export/import/add data with other applications
Mimosa template files File|Language .cfwNoNoYes Files accessed only by Mimosa (Site and Single User Licence), Mimosa Free and Mimosa Trial versions to store user interface selections
Mimosa profile files File|Profile .mpfNoNoYes
Comma Separated Values File|File Export|Other file formats .csvYesNoNo Export schedules to MS Outlook Calendar,
several other calendar applications
and mobile devices using standard formats
iCalendar File|File Export|Other file formats .icsYesNoNo
vCalendar File|File Export|Other file formats .vcsYesNoNo

You can also import and export data via Clipboard, typically from and to spreadsheet applications. See the chapter Import and export with Clipboard.

You can merge the contents of several Mimosa files in many ways. But if you just want to merge the contents of two Mimosa files (A.mfw and B.mfw) into one Mimosa file (C.mfw), do as follows:

1. Invoke Mimosa and open the file "B.mfw" with File|Open.
2. Export the file into text format "B.mxt" with File|File Export.
3. Open the file "A.mfw" with File|Open.
4. Add the contents of the file "B.mxt" to "A.mfw" with File|File Add (select "1. Add everything").
5. Save the results to file "C.mfw" with File|Save As.

Note that all possible conflicting activities of the two merged files were automatically removed.

Mimosa binary files (.mfw)

Mimosa utilises its own sophisticated database system which is specifically designed for demanding scheduling requirements. This means that users cannot edit or extract any item of the database without endangering to break its structure. Users can access the data base with the help of the text format (.mxt), defined in Mimosa text files (.mxt).

Mimosa proprietary binary database is based on fast integer arithmetic and it does not access any third-party databases. The architecture of the database for this special purpose was designed to achieve good performance, reliability and integrity. Mimosa files are also efficiently compressed. Due to high performance requirements, all Mimosa data is accessed in computer memory. When a file is opened in Mimosa, all data is copied to computer memory and when a file is saved, it is copied back to disk.

Mimosa uses the file extension .mfw for its own file format and 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, export or add other files, they have to be first converted to (.mxt) text format with the selection File|File Export. The resulting text file format syntax is simple and it can be easily converted to other file formats and back, in case users want to connect Mimosa to other applications.

Mimosa database system has a good performance, enabling over 100,000 accesses of events and timetables per second. Mimosa file sizes typically range from 10 kilobytes to 100 kilobytes - the maximum Mimosa file size ever seen is 580 kilobytes. Due to efficient compression, each resource plus event timetable stored in a Mimosa file requires on average only 4.3 bytes of disk, based on a sample of 500 real Mimosa files.

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. Files with this format are easy to manipulate with other applications and they can be saved into the Mimosa binary format with commands File|Save As and File|Save. After storing a Mimosa file in text format, its structure can be viewed and edited by all text editor applications.

How to import content from a text file to Mimosa:

  • Create a text file with the file extension .mxt, containing the contents to be imported or added to Mimosa
  • Select the command File|File Export or File|File Add to import or add the contents of the file

How to export the Mimosa file to a text file:

  • Select the command File|File Export ... to save the contents of the Mimosa file to a text file

The text file to be imported or added does not have to contain all contents of a Mimosa file. You can create a text file which contains just one section or some elements of it and create the Mimosa file incrementally by using the selection File|File Add. You can add or edit the contents also manually and add new contents also with the Clipboard.

With File|File Add it is possible to add files one by one and merge unlimited number of Mimosa files into one file in any order.

Note that it is also possible to import all or partial data into Mimosa and export it from Mimosa easily with the help of Clipboard. In this case users typically utilise a spreadsheet application as an external data storage.

You can use this format to create an API (Application Programming Interface) to import or add all or partial data into Mimosa and export data from Mimosa to other applications. Note that when you add the text file to a Mimosa file with File|File Add, you need to create only those sections and/or their items that you want to edit or add.

If you have checked in selection Options|Other "Open the last accessed Mimosa file upon start-up" and also "Add the contents of the selected text file (.mxt) at start-up to your Mimosa file at start-up", Mimosa automatically merges the contents of the selected text file to the Mimosa file which was opened.

Using command line parameters

Command line parameters help you to perform file import, export and add automatically and when the commands are written to batch file, they can be easily repeated in a similar way each time. Note that the filenames in the examples below may also contain their folder names, like the Mimosa application name (mfw.exe). The first command line parameter is always a Mimosa file name (.mfw) and the second parameter the text file name (.mxt). If the next parameters contain the switch /T, conversion is made from the Mimosa file to the text file, and if it is missing, from the text file to the Mimosa file.

Mimosa binary file (.mfw) must always exist, but it can be empty (no resources or events). After a text file is added to the Mimosa file, all possible conflicts between the two files are automatically removed. The syntax of the command line has the following format - the optional folders [folder1], [folder2] and [folder3] refer to the locations of the Mimosa application (mfw.exe), the binary files and the text files, respectively:

[folder1]mfw.exe [folder2]filename.mfw [folder3]addfile.mxt [/W][/T]

Example: c:\MimosaFolder\mfw.exe c:\MimosaFolder\Data\filename.mfw c:\MimosaFolder\Text\filename.mxt /W

[folder1]=c:\MimosaFolder\ --- (Mimosa installation folder)
[folder2]=c:\MimosaFolder\Data\ --- (Folder containing Mimosa .mfw files)
[folder3]=c:\MimosaFolder\Text\ --- (Folder containing Mimosa .mxt files)

    1. Add the contents of a text file (addfile.mxt) to a Mimosa file (filename.mfw):

    [folder1]mfw.exe [folder2]filename.mfw [folder3]addfile.mxt

    After adding the text file (addfile.mxt) to the Mimosa file (filename.mfw), it is automatically written to disk and Mimosa is closed, if you also include the parameter /W to the command line:

    [folder1]mfw.exe [folder2]filename.mfw [folder3]addfile.mxt /W

    What happened:

    1. Mimosa invoked
    2. File|Open... [folder2]filename.mfw
    3. File|File Add... [folder3]addfile.mxt
    4. File|Save As... [folder2]filename.mfw
    5. File|Exit

    2. Export the contents of a Mimosa file (filename.mxt) to a text file (exported.mxt):

    [folder1]mfw.exe [folder2]filename.mfw [folder3]exported.mxt /T

    After converting the Mimosa file (filename.mfw) to the text file (exported.mxt), it is automatically written to disk and Mimosa is closed, if you also include the parameter /W to the command line:

    [folder1]mfw.exe [folder2]filename.mfw [folder3]exported.mxt /T /W

    What happened:

    1. Mimosa invoked
    2. File|Open... [folder2]filename.mfw
    3. File|File Export... [folder3]exported.mxt
    4. File|Exit

You may want to create a batch file (such as combine.bat) that automatically performs several task in succession and merges the Mimosa files of three other users, Peter (peter.mfw), Paul (paul.mfw) and Mary (mary.mfw) to my Mimosa file (myfile.mfw) and finally exports the result to a text file (exported.mfw). In this example the preceding folder names have been omitted for simplicity.

First, convert the Mimosa files of each user to text format so that they can be added, then add each file in turn to my Mimosa file myfile.mfw. Finally, convert this file to text format (exported.mfw):

Batch file lines (without folders):

mfw.exe peter.mfw peter.mxt /T /W
mfw.exe paul.mfw paul.mxt /T /W
mfw.exe mary.mfw mary.mxt /T /W

mfw.exe myfile.mfw peter.mxt /W
mfw.exe myfile.mfw paul.mxt /W
mfw.exe myfile.mfw mary.mxt /W

mfw.exe myfile.mfw exported.mxt /T /W

Adding the third parameter /W automatically writes the results to disk and closes Mimosa so that this sequence can be run each time in the same manner and without any interaction. Remember to use folder paths in front of the file names, if they are located elsewhere than in Mimosa installation folder.

Structure and use of text files:

The text file consists of lines divided into sections, following the convention of 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. To avoid confusions, it is recommended not to use this character in codes or names. Note that all sections do not need exist. If they are missing, Mimosa replaces them with the default values, and when a text file is added (File|File Add), the contents of the current Mimosa file and added file are merged.

Note that when importing or adding a text file to Mimosa, the numbers preceding the lines, such as "3=" in

3=DIS639;Distribution Rights;1

do not need to be different or in increasing or decreasing order, but when the text file is exported from Mimosa, it automatically renumbers each line within each section (to ease checking of users).

Text file format is forgiving when importing or adding data into Mimosa; lines within each section can appear in any order and they can be replicated. All sections do not need to exist when adding data to a Mimosa file. If some of the sections is missing, Mimosa defaults are used instead.

The section names are presented in brackets, for example [Coursedata] or [Componentdata]. Note that in the section names the word "Course" corresponds to "Event", "Component" to "Resource" and lectures correspond periods according to the current Mimosa terminology.

For instance, if you like add new or update existing five events (with File|File Add), it is sufficient to have only the following lines in the .mxt file which is going to be added, and you can omit the last two numbers (event lock status and colour code):

[Coursedata]
1=ACQ747;Information retrieval;4;240
2=ADU171;Adult Education;2;76
3=ADV225;Advanced English;2;63
4=ADV383;Advanced Intaclid Printing;4;90
5=ADV476;Advertising Graphics;2;138

When exporting data to .mxt files, Mimosa adds extra fields at the end to the lines in [Componentdata] and [Coursedata] sections, but when adding data to Mimosa, they are not relevant.

In most cases, text file conversions are used incrementally, by using File|File Add repeatedly and entering and modifying the data also manually. This feature can easily be tested by adding a .mxt file consisting of the following lines:

[Coursedata]
1=MATHS;MATHEMATICS;1;3
2=HINDI;HINDI;2;3
3=GYM;GYMNASTICS;3;3
4=ENGLISH;ENGLISH BASICS;4;6

[Componentdata]
1=KG-B;KG-B;1
2=KG-D;KG-D;1
3=KG-E;KG-E;1
4=ADUTTA;A DUTTA;2
5=APINTO;A PINTO;2
6=GHOSALNUPU;GHOSAL NUPUR;2
7=KDUBEY;K DUBEY;2
8=MCHATURVED;M CHATURVEDI;2
9=RDASS;R DASS;2
10=RPARKASH;R PARKASH;2
11=KG-B-ROOM;KG-B ROOM;3
12=KG-D-ROOM;KG-D ROOM;3
13=KG-E-ROOM;KG-E ROOM;3

[Collections]
1=MATHS;KG-D
2=MATHS;KG-D-ROOM
3=MATHS;GHOSALNUPU
4=MATHS;RDASS
5=MATHS;RPARKASH
6=HINDI;KG-B
7=HINDI;KG-B-ROOM
8=HINDI;GHOSALNUPU
9=HINDI;ADUTTA
10=HINDI;MCHATURVED
11=GYM;KG-E
12=GYM;KG-E-ROOM
13=GYM;APINTO
14=GYM;KDUBEY
15=ENGLISH;KG-E
16=ENGLISH;GHOSALNUPU
17=ENGLISH;KG-B-ROOM

When this file has been added, Mimosa creates a file of 4 events and 13 resources and attaches the relevant resources to events. If the current Mimosa file already has resources and events with matching codes, their names are replaced accordingly and the events resource lists are modified accordingly.

Note that you can also remove existing events and resources from your Mimosa file by adding their codes to [Remove] section.

[Remove]
1=HINDI
2=KG-E
3=ADUTTA

Sections in text files:

[Header]

Fields in [Header] section have no effect on Mimosa file content and they are created by Mimosa when File|File Export is invoked. The values in tags "OriginalFile", "SourceFile" and "FileId" are received from third-party applications. When Mimosa file is next time converted to .mxt format, they are restored from disk and added to respective tags.

Other applications which create .mxt file(s) which are to be imported or added to Mimosa do not need to include a [Header] section and Mimosa does not use any of the information it contains.

[Header]
Version=7.1.5
OriginalFile=
SourceFile=
FileId=
Created=20111124 21:07:26
Customer=Mimosa Scheduling School
Department=Timetabling Department
Copyright=[C] Mimosa Software Ltd.
Comment=
Description=

[Time]

[Time] section consists of the maximum number of Weeks, Days and time periods as set in Options|Limits. If you want to align Mimosa weeks with the calendar, set the serial date of the first date to Date. This serial date is a whole number used in most spreadsheet applications (serial date number 1 corresponds to 1.1.1900, serial date 2 the next day and so on). The tag YYYYMMDD is provided to set the serial date using a simpler format (20180116=1.16.2018), and when it exists, its value replaces the serial date number value in Date. For instance, if YYYYMMDD=20180116, the value of the spreadsheet function Datevalue("16/1/2018")=43117=Date.

If these date fields (Date, YYYYMMDD) are missing, Mimosa weeks are not assumed to be aligned with the calendar, the selection [x] Align Mimosa weeks with calendar is not checked (in Options|Time).

The field Firstweek defines the first permissible week (default=1) set in Weeks view, WeekSum contains the number of all weeks (which are not imported to Mimosa) and Days consists of the list of days in week, separated by "$".

If this section or its fields are missing, they are replaced with the current default values in Mimosa.

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

In the subsequent sections, the tags containing (Week) and (Day) are expressed for brevity and accuracy in integers rather than in text format. If you have aligned Mimosa weeks with the calendar, you can use your spreadsheet application to convert these numbers with real dates and back as follows. For simplicity, we assume that all weeks have the length of one week.

1. Converting from real dates to Mimosa .mxt: Suppose the first day of the first week has the value of Date=43332 (YYYYMMDD=20180820). If you want to get the value for Week and Day for the date 22/11/2018, calculate first its serial value: DATEVALUE("22/11/2018")=43426. You can then calculate the valus for Week and Day: Week=TRUNC(43426-43332)+1=14 and Day=MOD(43426-43332,7)+1=4, applying the functions of your spreadsheet application.

2. Converting from Mimosa .mxt to real dates: Suppose the first day of the first week has the value of Date=43332 (YYYYMMDD=20180820). If you want to calculate the serial date (and date) of the Wednesday (=3) of the sixth Week (=6), you can use the formula: Date + 7x(Week - 1) + (Day-1) = 43332 + 7x(6-1) + (3-1) = 43369, which is 26/09/2018 (after formatting the serial number to the date format).

[Timeperiods]

[Timeperiods] contains the names of the time periods, such as 09:00-09:45, 10:00-10:45 and so on, as set in Options|Time. Time periods are free form text tags, but if you are about to export data to other calendar applications in File|File Export..., it is recommended to use the format hh:mm-hh:mm to enable sychronising timetables correctly.

[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

If this section or its fields are missing, they are replaced with the current default values in Mimosa.

[Weeks]

[Weeks] contains the lengths and names of each week, divided by a semi-colon, as set in Options|Time.

[Weeks]
1=1;08-16
2=1;08-23
3=1;08-30
...
41=1;05-23
42=1;05-30

If this section or its fields are missing, they are replaced with the current default values in Mimosa.

[Blocks]

[Blocks] is an optional special section which stores the block numbers used only in selection Tools|Block scheduling.

[Blocks]
1=
2=
3=
...
41=
42=

If this section or its fields are missing, they are replaced with the current default values in Mimosa.

[Courses]

[Courses] section contains the event categories and texts used in bookings, separated by "$" plus the default booking number as set in Options|Categories.

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

If this section or its fields are missing, they are replaced with the current default values in Mimosa.

[Components]

[Components] section contains the resource categories and text used in bookings, separated by "$" plus the default booking number as set in Options|Categories. The values in "NoTimetables", "NoGaps" and "Rooms" correspond the selections "Prevent conflicts for", "Count gaps for" and "Category for rooms" in tab Options|Timetables.

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

If this section or its fields are missing, they are replaced with the current default values in Mimosa.

[Coursedata]

[Coursedata] lists all events: code, name, category number and the maximum number of periods delimited by semicolons, and optionally code indicating if the event is locked or not (0/1) plus the colour code if user has set a colour for the event.

123=(EventCode);(EventName);(EventCategoryNumber);(PLANNED);(Locked:0/1);(ColourCode)

[Coursedata]
1=COM609;Computer Science II;3;387;0;55295
2=COR765;Corporate Identity;2;311;0;65535
3=DIS639;Distribution Rights;1;334;0;11200750
4=ENV449;Environmental Education;1;398;0;11200750
5=INV37;Inventory and Warehousing;2;288;0;65535
...
48=PRI824;Principles of Mathematics;2;319;0;65535
49=SOC479;Social Welfare;2;324;0;65535

When you import or add events to Mimosa, you need only enter the four first fields, such as:
123=(EventCode);(EventName);(EventCategoryNumber);(PLANNED)
1=COM609;Computer Science II;3;387

[Componentdata]

[Componentdata] lists all resources: code, name, category number and the maximum number of periods delimited by semicolons, and optionally the colour code if user has set a colour for the resource. The PLANNED number of periods is the sum of the maximum number of periods of related events when this file was created; when this file is imported or added, the value of this PLANNED field has no effect (and can be set to zero), since it is automatically recalculated by Mimosa.

123=(ResourceCode);(ResourceName);(ResourceCategoryNumber);(Max);(ColourCode)

[Componentdata]
1=G106;G106;1;560;16436871
2=LineB;LineB;1;916;16436871
3=O112;O112;1;702;16436871
4=O114;O114;1;724;16436871
5=O115;O115;1;676;16436871
...
45=R335;ROOM 335;3;664;16760576
46=R246;ROOM 246;3;1286;16760576

When you import or add resources to Mimosa, you need only enter the four first fields, such as:
123=(ResourceCode);(ResourceName);(ResourceCategoryNumber)
45=R335;ROOM 335;3

[Collections]

[Collections] consist of all event resource combinations, as set in Resources or Events view. If an event has several resources (as typically is the case), each pair is listed here. The resources are added to events according to their order in this list, but otherwise the order of the items on this list is irrelevant. Mimosa checks that events cannot contain the same resource twice and that the total number of resources in each event does not exceed the maximum number 240.

The lines in this section refer to the event and resource codes presented in [Coursedata] and [Componentdata] sections and therefore [Collections] section should appear after them. Lines that contain missing event or resource codes, are omitted.

123=(EventCode);(ResourceCode)

[Collections]
1=ACQ747;G102
2=ACQ747;WYATT
3=ACQ747;R246
4=ADU171;G104
5=ADU171;CHRISTIAN
6=ADU171;R335
...
106=SOC479;FIELD
107=SOC479;R335

For example, the first three lines define that the event "ACQ747" consists of resources "G102", "WYATT" and "R246".

[Weeklectures]

[Weeklectures] lists all event codes and the periods allocated for each week. In this notation MinWeek is the first week number, MaxWeek the last week number, and NumOfPeriods is the allocated number of periods (>0) for all weeks from MinWeek to MaxWeek.

123=(EventCode);(MinWeek);(MaxWeek);(NumOfPeriods)

[Weeklectures]
1=COM609;23;24;18
2=COM609;25;25;19
3=COM609;26;26;21
4=COR765;1;1;12
5=COR765;2;2;9
...
1022=SOC479;25;25;15
1023=SOC479;26;26;19

The lines in this section refer to the event codes presented in the [Coursedata] section and therefore [Weeklectures] section must appear after [Coursedata] section.

[Weekbookings]

[Weekbookings] lists the used booking numbers of events. In this notation MinWeek is the first week number, MaxWeek the last week number, and BookingNumber is the booking type number (1-3) set for all weeks from MinWeek to MaxWeek.

123=(EventCode);(MinWeek);(MaxWeek);(BookingNumber)

[Weekbookings]
1=LAU895;18;20;1
2=LAU895;30;30;2
3=WAT184;18;20;3
4=WAT184;30;30;2
5=BAS376;18;20;2
...
26=EXT547;30;30;2
27=FOR75;18;20;2

The lines in this section refer to the event codes presented in the [Coursedata] section and therefore [Weekbookings] section must appear after [Coursedata] section.

[Tablelectures]

[Tablelectures] consists of a list of all scheduled event periods. Each line defines a "cube" having as its sides minimum and maximum week, minimum and maximum day, minimum and maximum slot number. Note that the scheduled periods are denoted by events, although users normally schedule, view and print timetables by resources. For instance, if event "ABC234" is scheduled in the first two slots in Thursday on the second week, it is denoted by "1=ABC234;2;2;4;4;1;2". When this data is imported, Mimosa automatically checks that they are not conflicting with each other.

123=(EventCode);(MinWeek);(MaxWeek);(MinDay);(MaxDay);(MinSlot);(MaxSlot)

[Tablelectures]
1=COM609;26;26;4;4;5;8
2=COR765;1;1;1;1;1;4
3=COR765;1;2;2;2;1;2
4=COR765;1;1;3;3;1;2
5=COR765;1;1;4;4;1;3
...
4987=SOC479;26;26;4;4;3;4
4988=SOC479;26;26;4;4;8;9

The lines in this section refer to the event codes presented in the [Componentdata] section and therefore [Tablelectures] section must appear after [Componentdata] section.

[Tablebookings]

[Tablebookings] consists of a list of all resource bookings set into timetables. Each line defines a "cube" having as its sides minimum and maximum week, minimum and maximum day, minimum and maximum slot number, plus the number of the booking (1-3) set in these slots.

123=(ResourceCode);(MinWeek);(MaxWeek);(MinDay);(MaxDay);(MinSlot);(MaxSlot);(BookingNumber)

[Tablebookings]
1=SARANDON;42;42;2;2;1;4
2=SARANDON;42;42;3;3;1;1
3=ROOM123;1;1;2;2;1;5
4=ROOM123;1;1;3;3;1;6
5=ROOM123;1;1;5;5;1;6
...
292=ROOM483;16;16;2;2;1;2
293=ROOM483;16;16;3;3;1;1

The lines in this section refer to the event codes presented in the [Componentdata] section and therefore [Tablelectures] section must appear after [Componentdata] section.

[Manualrooms]

[Manualrooms] consists of a list of all rooms assigned to event schedules "manually" in selection Tools|Select rooms manually.

123=(EventCode);(RoomCode);(WeekNum);(DayNum);(SlotNum)

[Manualrooms]
1=FOR744;R205;2;4;2
2=FOR744;R204;3;1;7
3=JOU744;R230;1;2;3
4=JOU744;R233;2;2;3
5=JOU744;R230;2;2;6
...
320=THE66;R111;9;1;5
321=THE66;R111;9;3;4

The lines in this section refer to the event and resource codes presented in [Coursedata] and [Componentdata] sections and therefore [Manualrooms] section should appear after them. Lines that contain missing event or resource codes, are omitted.

[Coursedates]

[Coursedates] is an optional section consisting of scheduled event periods, represented by start and end dates plus the number of periods. This section is created by Mimosa and it is added to make it easier for developers to interpret [Weeklectures] section in the case when Mimosa is aligned with the calendar and exported. When importing or adding data to Mimosa, this section is omitted, since the same information can be read from other sections.

123=(EventCode);(MinYYYYMMDD);(MaxYYYYMMDD);(Periods)

[Coursedates]
1=COR765;20110131;20110204;15
2=COR765;20110207;20110211;17
3=DIS639;20100816;20100820;18
4=DIS639;20100823;20100827;19
5=DIS639;20100829;20100902;18
...
1104=SOC479;20110130;20110203;15
1105=SOC479;20110207;20110211;19

[Tablecomments]

[Tablecomments] section lists all comments added to timetables in Timetables view. The time is represented in brackets as follows: [WWWDHH], where "www" is the week number, "D" is the number of day and "HH" is the number of slot. See the page Comment cell for more information about comments.

123=([WWWDHH]);(ResourceCode);(Comment)

[Tablecomments]
[015102];B207;Free periods
[015103];C207;Exception from normal timetable
[015104];D335;Exams
...

The lines in this section refer to the event codes presented in the [Componentdata] section and therefore [Tablecomments] section must appear after [Componentdata] section.

[Roles]

Roles are defined as triplets containing the event, resource and the attached role (see Edit|Manage roles).

123=(EventCode);(ResourceCode);(RoleName)

If a rolea are not attached to any events and resources, they are listed with hyphens (-) instead of codes:

123=-;-;(RoleName)

[Roles]
1=Paper-001;STANLEY;[Referee]
2=Paper-002;STEPHENSON;[Referee]
3=Paper-003;SUTTON;[Referee]
4=Paper-001;POWELL;[Contributor]
5=Paper-002;PRESTON;[Contributor]
6=Paper-003;REYNOLDS;[Contributor]
7=Paper-001;ALLISON;[Chairman]
8=Paper-002;ATKINSON;[Chairman]
9=Paper-003;AVILA;[Chairman]
10=-;-;[Interpreter]

[Holidays]

This section enables you to add Holidays or other daily activities to timetables, if you have checked Align Mimosa weeks with calendar in Options|Time. Since this section does not contain any dependencies on events, resources or timetables, you can store the contents of this section also in a separate .mxt file and add it to the current Mimosa file by using the selection File|File Add.

123=(YYYYMMDD);(Description);([BookingNumber])

If the date is valid, Mimosa makes a booking to all free slots in all timetables of this date (using the [BookingNumber]), and adds the description as a comment to all slots of this date and it is shown in timetables and printed or published reports. The functionality is the same as in Make all day activity in Options|Limits. The default value of the [BookingNumber] is 1, if this field is not specified.

[Holidays]
1=20140101;New Year;3
2=20140114;Prophet Muhammad's Birthday
3=20140117;Thaipusam
4=20140131;Chinese New Year
5=20140201;Chinese New Year
6=20140501;Labour Day
7=20140513;Wesak Day
8=20140607;Agong's Birthday
9=20140715;Nuzul Al-Quran
10=20140728;Hari Raya Aidilfitri
11=20140831;Merdeka Day
12=20140728;National Day
13=20141005;Hari Raya Haji
14=20141006;Hari Raya Haji
15=20140728;Awal Muharram
16=20140823;Deepavali
17=20141211;Sultan of Selangor's Birthday
18=20141225;Christmas

[Remove]

You can remove existing events and resources from your Mimosa file by adding them to [Remove] section. You need to list only the codes of the events and resources and they are removed at the time when Mimosa reads the lines in this section by using the selection File|File Add. The contents of this section can be read also from a separate text file.

123=(Event|Resource code)

[Remove]
1=HINDI
2=KG-E
3=ADUTTA

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

What you need to provide when importing data to Mimosa?

Note that you do not have to provide all that information in the text file that Mimosa creates when it exports its data to a text file via File|File Export. Also the order of the sections in the text file is more or less arbitrary, but you must declare the section [Time] before all other sections and [Collections] after the sections [Coursedata] and [Componentdata].

When importing data, the numbers on the left of "=" sign need not to be in increasing order. They are used to identify the items only in sections [Timeperiods] and [Weeks], whereas in other sections items are added in the order they appear.

You need to include at least the following sections in order to create a new working Mimosa file:

[Time]
...
[Coursedata]
[Componentdata]
[Collections]
...

If you have allocated periods to weeks, scheduled them or made bookings, you have to include also the following sections:

...
[Weeklectures]
[Weekbookings]
[Tablelectures]
[Tablebookings]
[Manualrooms]

If you also want to import names and properties of the categories, names of time periods and weeks, you have to include also:

[Timeperiods]
[Weeks]
[Courses]
[Components]

These sections should follow the [Time] section.

When you add data from the text file into Mimosa with selections File|File Add or File|Network|Read from Network, all matching events and resources are replaced with those of the imported file, and all new resources and events are added to the lists of existing codes.

Example of a Mimosa text file (.mxt)

Below is a truncated sample file generated from a Mimosa file using the selection File|File Export.

[Header]
Version=6.1.4
OriginalFile=
SourceFile=
FileId=
Created=20131016 20:23:41
Customer=Mimosa Scheduling School
Department=Timetabling Department
Copyright=[C] Mimosa Software Ltd.
Comment=
Description=

[Time]
MaxWeeks=1
MaxDays=5
MaxLectures=10
Date=41505
YYYYMMDD=20130819
FirstWeek=1
WeekSum=1
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 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 events$e:Events 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 events
   2 List of resources
   3 Schedules
   4 Events by resources
   5 Resources by events
   6 Compact schedules
[Months]
[Base]
37004
[Mode]
0
[Words]
   1 COURSES$COMPONENTS$#:$CODE$NAME$*$PLANNED$WEEKS$OK$LINKS$LEFT$

Mimosa profile files (.mpf)

In selection File|Profile you can save the current Mimosa settings with another name and file extension .mpf and read it again into the Mimosa, if you want to use it later on for different purposes. These profile files are copies of the settings.ini file, which contains the settings which are automatically read into Mimosa when it is invoked and where latest settings are stored when Mimosa is exited. This file contains among other preferences, all print format, font and colour selections.