Mass uploads
One of the challenges a SharePoint user almost always encounters with mass uploads is the need to populate specific metadata for each document. In some cases entire document sets share the same value for a metadata (e.g., Division). In others, each document requires individual human attention.
If you upload a large set of documents as major versions with approval and check-in disabled, a Hyper.Net transformation request will be created for each document and a publication corresponding to each document will be immediately released for use in your WCMS application. This can lead to problems for two reasons:
| |
· |
It may be that each document must go through an approval process first to ensure its content is correct for the given context and also that its metadata is correct for the organization.
|
| |
· |
The resulting publications will have no metadata other than the values specified in Hyper.Net's document type profile for the content type, or in the Default Values within the Hyper.Net schema associated with the document type profile, or "global" metadata values that have been applied to all documents that were uploaded. This means that your readers may not have the information they require. Your WCMS application may also not have the information it needs to present the content properly. Information such as categories and reader security notations may not be present and view selections may not function as expected. As a result, your WCMS application may not behave correctly.
|
It is thus usually beneficial to enable the check-in function when you do a mass upload—at the very least during the upload effort. Upload the documents and leave them checked out. Modify the metadata and then check the documents in.