Collaborate effectively with your team without complexity and the need for extra training. We've made the publishing process naturally intuitive for all our users, whether they're technical or business-oriented.
In the Coginiti system, the project publishing process is designed to optimize code storing, management, and reuse. This system, specifically created for teams, not only simplifies collaboration but also ensures the security and reliability of project data.
The publication flow for projects in our system effectively addresses potential issues and boosts overall code management:
- Maintaining the integrity of published content and preventing unauthorized changes. This is ensured as only users with the "Publisher" role, assigned by an admin, are allowed to publish new projects or update existing ones.
- Preserving the stability and reliability of ongoing projects that rely on older versions. Earlier versions of projects are not overwritten, allowing users who have used these versions in other projects or scheduled events to continue their work uninterrupted.
- Facilitating easy sharing and collaboration. Once a project is published, it becomes accessible to all users with access to the folder where it's stored, streamlining the sharing process within the authorized user group.
- Allow experimentation and testing of changes without impacting the stability of the originally published project. Users can work with working copies of published projects, thus safeguarding the original version.
- Ensuring each published version remains a consistent and unaltered version of the project at that particular stage. Direct changes to an already published version are not permitted. For modifications, users need to revise the original project or its working copy and then publish a new version.
To Publish a New Project:
- In the left sidebar, navigate to the 'Personal' section of the Catalog.
- Find the Project you wish to publish and right-click on it to open the context menu.
- Select 'Publish' to initiate the publishing process.
In the pop-up window:
- Enter the name of the project.
- Set the project version number.
🔎 NOTE: Use the same system for numbering versions that your team usually uses. This makes it easier to keep track of and understand the changes.
- Choose the location for publishing.
- Describe the project or describe any big changes you've made.
- Click 'Publish'.
By following these steps, you ensure that your project is published effectively, thus making the latest and most pertinent data available to your team and other stakeholders.
⚠️ Once published, the project will be accessible to all users with access to the folder where the project is published.
Modify and Publish a New Version of the Project:
- In the left sidebar, go to the ‘Package Hub’ section in the Catalog.
- Locate the Project you want to modify and right-click on it to access the context menu.
- Choose ‘Create Working Copy’ to make a modifiable copy of the project.
Enter details for the working copy:
- Use the 'Project name' field to rename the project if needed.
- In the 'Project description (optional)' field, provide a brief description of your working copy.
- The 'Project location' drop-down allows you to select the copy's path in the 'Personal' section of the Catalog.
- Click 'Create'.
🔎 NOTE: You can invite other team members to collaborate on this working copy. Especially if you lack a 'Publisher' access level, invite a user with that role to publish the modified working copy.
Once you've completed the modifications of your working copy:
- Find the working copy you intend to publish, right-click on it, and open the context menu.
- Select 'Publish' to start the publishing process.
In the pop-up window:
- Specify the project version number.
🔎 NOTE: Follow the version numbering system your team typically uses for consistency and easy tracking of changes.
- Describe the new version of the project, or highlight any major changes you've made
4. Click 'Publish'.
⚠️ If you change the location for the new version, it will create a new, separate project in the selected location, independent of the original project. As well as you choose ‘Publish as a new Project’.
Tips for Publishing Projects
- Before publishing a project, thoroughly review all changes. Ensure everything is in order and the project is ready for wider visibility or use.
- Use the ability to work on copies of published projects for experimentation. This allows you to test changes without affecting the live version of the project.
- When publishing a project, consistently follow the version system that is used in your team. This practice helps you track changes and understand the evolution of a project over time.