Master Projects Overview
This lesson provides an overview of Master Projects within the GenRocket web platform for your Organization.
Important: Master Projects should be used sparingly.
What is a Master Project?
- A Master Project is a Project with limited functionality and whose Project Versions can be inherited by other Projects, Project Versions within your Organization.
- A Project Version of a given Project can inherit from the Master Project, so that it contains the information generated by the common Domains, but not necessarily the same Parent/Child/Sibling Relationships.
When should Master Projects be used?
- Master Projects should be used when you have multiple databases or applications that share a common Domain or set of Domains.
Who can create and manage Master Projects?
- Data Architect Persona
- Any user who has been assigned the Organization Admin Role
Rules for Master Projects
- A Master Project can only contain Master Domains containing Master Attributes.
- A Project whose Project Versions inherit from a Master Project Version is called a Child Project.
- A Master Project’s Domain inheritance cannot be modified once referenced by even one Child Project.
- Attributes within a Master Domain can be added, modified, and deleted.
- Generators within a Master Attribute can be added, modified, and deleted.
- Changes made to a Master Project Versions’ Master Domains, Master Attributes, and Master Generators are immediately refactored to any Child Project Versions.
- Master Domains, Master Attributes, and their Generators cannot be modified within Child Project Version.
- A Master Project cannot inherit from another Master Project.
Project Dashboard Icons
Master Project – This icon will be displayed within the Project Dashboard for any Master Project, Master Project Version, and Master Domain.
Project – This icon will be displayed within the Project Dashboard for any Project that is not a Master Project.