You can change the name of objects in the repository. Renaming an object does not ordinarily affect its relationships with other objects.
Unlike a file system, Astoria tracks objects and object relationships using a unique object ID rather than the file name. It is generally safe to change the file name of objects.
Administrators can control what users have permission to change a file name. If authorized, you can manually change a file name by viewing the object properties . The Global Substitution tool also provides a substitution rule that allows you to rename structured documents. See Rename Folder Item Substitution Rule.
Administrators can view information about repository folders and folder objects that have been renamed.
Considerations for Renaming Folders
- Objects that are deleted from a folder that is subsequently renamed are restored to the renamed folder by default. A user can override the folder location by selecting a different folder in the cabinet.
- Translation cabinets generally mimic the source folder structure at the time the documents are first translated. Subsequent changes in a folder name does not change the folder location of previously translated files. New translated topics from a renamed source folder will be placed in a new folder with the changed name.
Considerations for Renaming Structured Documents
- In general you should not change the file extension of a structured document. Doing so may cause the file to stop working properly.
- Translated topics use the file name of objects at the time the objects are first translated. If a source object is renamed, subsequent translations will not change the file name.
Considerations for Renaming Unstructured Documents
- In general you should not change the file extension of a unstructured file. Doing so may cause the file to stop working properly.
- When you check in a replacement file, such as for a graphic, you can replace the existing file with a file with a different name.