Anatella fully supports collaborative work.
For example, one of the largest Anatella-based project contains about 500 Anatella-Graph-Files. This project has a dozen analysts that are simultaneously & collaboratively working full-time on it.
Collaborative work can happen at different levels:
1. The Analysts can work on the different Anatella graph files and share their work using a versioning system (or using a simpler synchronization software such as “Google Drive” or “DropBox”).
The most established versioning system is currently “Git”. One limitation of Git is that it only supports text files saved in the “utf-8” character encoding (other text file encodings only appear as “binary” files). Please refer to the section 7.1. to know how to save your .anatella files in an optimized format (UTF-8) to get a perfect Git integration.
A Git project nearly always include these 2 files (or some files with an equivalent usage):
…with the “config.cfg” file inside the .gitignore file.
Typically, the program first load all the settings inside the “default_config.cfg” file and thereafter it loads the settings from the “config.cfg” files (possibly over-writing some settings from the “default_config.cfg” file). Thus, every developer can “tune” all the project’s settings using its personal “config.cfg” file, to adapt them to the local machine. To follow this idea inside Anatella, you can include inside your graph:
•Manage the users that are allowed to edit/run the graphs
•Save the .anatella file in a format optimized for a version control system (such as git).
This optimized format has the following properties:
oNo file encryption
o(optional): No special users for the .anatella file
See the section 9.7. and the section 9.8. to know more about this subject.
4.The deployment and monitoring of the correct execution of your .anatella graphs can also be done in a collaborative way. More precisely: Anatella integrates with Slack: using the Action. This means that you can easily send to Slack some monitoring messages that are therafter dispatched (by Slack) to the proper members of your team (to their email, cell phone, etc.).
If you don’t want to work with Slack, you can also use a simpler “email”-based approach for monitoring: For example, this sends a simple “coucou message” to “email@example.com”: