Manage Packages Through Roles
Working with packages in a deployment that includes Spotfire, Spotfire Server, and (optionally) Spotfire Statistics Services can add layers of complexity to management policies.
The job of synchronizing package versions among your development computers, your testing computers, and your servers is an important package management concern for an organization. You can reduce the risk of confusion and streamline your processes by defining roles in your organization for dealing with packages. Ensure processes and rules are established to manage packages.
Additionally, you can develop and use an in-house package repository from which all users install the same package versions. See Package Repositories for additional guidance.
- Developer Role
The developer is an R programmer or statistician who develops packages using TERR or open-source R. - Guru Role
The curator maintains the standards and lists of officially-sanctioned packages. The curator keeps all of the package versions synchronized. The curator might be the same person who fills the developer role. - Administrator Roles
The Spotfire administrator manages packages on the Spotfire Server and on Spotfire Statistics Services.
- Developer Role
The developer is an R programmer or statistician who develops packages using TERR or open-source R. - Guru Role
The curator maintains the standards and lists of officially-sanctioned packages. The curator keeps all of the package versions synchronized. The curator might be the same person who fills the developer role. - Administrator Roles
The Spotfire administrator manages packages on the Spotfire Server and on Spotfire Statistics Services.