Using the data created on the filesystem by the cmis tests write bulk import tests.
1A - Using the embedded bulk importer of Alfresco import the documents directly from the path where they were created.
1B - Move the documents from their location to a place inside the contentStore (this can be a manual step if the Alfresco is remote) and with the embedded bulk importer of Alfresco perform the inplace import of the document.
2A - Using the latest version of the bulk importer (https://github.com/pmonks/alfresco-bulk-import) import the documents directly from the path where they were created.
2B - Move the documents from their location to a place inside the contentStore (this can be a manual step if the Alfresco is remote) and using the latest version of the bulk importer (https://github.com/pmonks/alfresco-bulk-import) perform the inplace import of the document.
In the future, Pentaho will provide a comparison between both results.
Using the data created on the filesystem by the cmis tests write bulk import tests.
1A - Using the embedded bulk importer of Alfresco import the documents directly from the path where they were created. 1B - Move the documents from their location to a place inside the contentStore (this can be a manual step if the Alfresco is remote) and with the embedded bulk importer of Alfresco perform the inplace import of the document. 2A - Using the latest version of the bulk importer (https://github.com/pmonks/alfresco-bulk-import) import the documents directly from the path where they were created. 2B - Move the documents from their location to a place inside the contentStore (this can be a manual step if the Alfresco is remote) and using the latest version of the bulk importer (https://github.com/pmonks/alfresco-bulk-import) perform the inplace import of the document.
In the future, Pentaho will provide a comparison between both results.