A manufacturing company uses a document type called Invoice. Several metadata is defined for this document type, for example
Invoice Number,
Customer Name,
Project Number. The company has already stored 10 million documents in the Collector archive with the defined metadata.
The company uses StreamStudio Collector to access the documents. Since Project Number is never used in the Collector searches, the company wants to remove this metadata from the Collector web application and release the corresponding space in the Collector archive.
The consultant logs in to Control Center as the management gateway administrator user. When the Archiver application has finished all ongoing archiving tasks, the consultant stops the application. Before redeploying the Project, the consultant ensures there is a complete backup of the runtime repository. At the redeploy, the Compare Document Types tool opens, informing that the document type has been changed. The consultant completes the redeploy operation by forcing the updated document type into the runtime repository. The updated document type, without the
Project Number metadata, is then stored in the enterprise repository and the runtime repository.
To release space in the Collector archive, the Project Number metadata must be deleted from the archive. To delete the metadata, the consultant contacts the database administrator for the company. Using the DBMS (Database Management System), the database administrator deletes the metadata from the archive.
The Invoice document type is now identical in all three repositories.
The consultant restarts the applications and runs the Project. The processed documents are stored in the Collector archive without the
Project Number metadata. The
Project Number metadata does not appear in Collector, and is not related to any old documents in the Collector archive.