|Creating, Registering, Moving, Copying, Renaming, and Deleting SAS Metadata Repositories|
The access mode of a metadata repository is the repository's intended access state. When the metadata server is online, the access state of a repository is equal to its access mode. When the metadata server is paused to an Offline state or an Administration state, the access state of a repository can change temporarily (see How the Access State of the Metadata Server Affects the Access States of Metadata Repositories). When the metadata server is resumed, the repository's access state returns to its registered access mode.
A repository's access mode is recorded in the Access attribute of the repository's metadata definition. When you create a new repository, you can place it in any of the following access modes:
Clients can read, write, and update metadata. This access level is the default for new repositories.
Clients can read metadata but cannot write, update, or delete metadata.
|Example Use Case||If work on a project is complete, you can assign an access mode of ReadOnly to the project's repository so that users can continue to access the metadata without updating it.|
Only users who are in the Metadata Server: Unrestricted role can read or write metadata. (For information about this role, see Overview of Initial Roles, Groups, and Users.)
|Example Use Case||If metadata problems occur (for example, if the metadata in a repository becomes corrupted), you can assign an access mode of Administration while the issue is being analyzed and repaired.|
Clients can neither read nor write metadata to the repository.
|Example Use Case||If work on a project is complete and users no longer need to access the metadata, you can assign an access mode of Offline to free server memory. If the metadata is needed in the future, the access mode can be changed back to ReadOnly or Online.|