Using Record Routing Types
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
The Records Center Web service description includes one concept to ensure your records are stored in the proper location and that they contain the necessary information: the record routing type.
Using Record Routing Types to Organize Record Storage
The Records Center Web service uses the concept of a record routing type as a means to organize storage of similar types of records. At its simplest, a record routing type name can correlate to a specific storage location for files. Files submitted to the Records Center Web service with a given record routing type name can be stored in the same storage location. For example, if you want to store all your contracts together in the records center, you could create a record routing type named Contract.
Record routing types help organize content in the records center. In addition, using record routing type names, rather than passing explicit storage locations to the records center interface, adds another level of indirection. This indirection provides the following advantages:
Users do not need to know anything about the records center structure to submit files. Record managers can organize the records center as they want, and then simply provide record routing type names and descriptions that the users can understand.
Record managers can control how submitted files are processed, without having to change the underlying structure of their records center.
Each record routing type consists of the following metadata:
Name The name of the record routing type, such as Contract or Product Spec.
Description Optional. A short description of the record routing type.
Location The storage location where files of this record routing type are stored.
Aliases Optional. You can associate multiple aliases to a single record routing type. This enables files submitted with an alias as their record routing type name to be stored in the record routing type location. For example, for a Product Spec record routing type, you might specify Spec and Feature Spec as aliases. Files submitted with either of these aliases are then stored in the Product Spec location.
The exact implementation of how that application routes the file to the appropriate record routing type location may vary, depending on the application acting as a records center, and are of course not visible to the Web service itself.