- Tutorials: swift mapping tool tutorials (YouTube videos)
- Effectively and efficiently create mappings
- Change requests for ICAO codes and liveries
- Mapping hints and FAQs
- Problems creating mappings? Some hints.
In order to create mappings you need to login within the swift datastore: In the mapping tool, go to the "Settings and Login" tab, and login with the DB. After the login you can see your roles as explained in swift mapping roles
Models which already have a database mapping are indicated by a database icon. You can see that in the screenshot. Normally you need to create mappings only if it not yet exists.
It can also happen, that your data are outdated and in the meantime someone has created a mapping for model, which is not yet shown with the database icon. You can read more about data consolidation here.
Another good reason to change an existing mapping is if it is wrong. In this case you can correct the mapping. The procedure (for you) is the same, regardless if you create a new mapping or modify an existing one.
Users with "bulk" update right and higher (see swift mapping roles) can directly write to the DB. Other users will be able to create change requests. For you as a user there is almost no difference in creating the mapping, only the release process is different.
- Normal users: publish change request confirmed in DB
- Direct updates:
- new mappings: publish in DB
- changed mappings: publish change request confirmed in DB
After you have successfully published your mappings you will see a "confirmation screen". You can remove those published models (if you like) from the stash. Doing so allows you to publish step by step.
It does not make sense to publish mappings identical to an existing one in the DB. This would only create unnecessary change requests and work history entries. Therefor publishing identical entries is rejected. You will see a message like this in such a case: