I'm looking for a bit of development advice. We have a need to provide end users with the ability to upload a number of documents to Content Server at one time.
1. Users use the regular Content Server web interface / UI for their daily work.
2. Adding documents one at a time - functionality works just fine. However, it's cumbersome for (say) 100 documents (we have three categories that need to be completed).
So we are envisaging a process something along the lines of:
1. User clicks an "Add Multiple Docs" button that we add to the Content Server UI; this brings up a File Open dialog, allowing the user to navigate to a network folder and select one or more (or all) docs from that network folder.
2. A grid type UI would then appear, listing the selected documents, and with columns for the various attributes that need to be supplied as the docs are added to Content Server. There is some complexity around how the attributes interrelate (things like parent / child relationships between attributes etc). This grid-like UI will allow the user to fully populate the metadata for the batch of documents, before they are submitted.
3. Use then presses an "Upload" button and the documents and associated metadata are loaded to Content Server. As each doc is loaded, we would like to indicate on the grid that it's been loaded. Finally, the grid then disappears and the Content Server folder refreshes.
So - we are all good with items 1 and 2.
The real question is around item 3 - the uploading of the documents. Content Server provides quite a few different ways to upload documents - Object Importer, LLAPI, web services etc. We would appreciate some advice as to what approach might be best for this particular set of requirements?
