Identifying Collection data in Staging Explorer

This section helps to identify the components of the folder information within the Staging pane of the Staging Explorer as it relates to the Collections setup fields.

Use the sample screen below as a general guide for each data source type.

Here is a breakdown of the folder components within the Staging pane of the Staging Explorer:

\\files\<T####>\ProcessingSource\Collections\<WorkspaceID>\<CollectionName>_<CollectionArtifactID>\<DataSourceArtifactID>

• The Processing Source Location from the Collections page becomes the file location for the data in Staging Explorer. It contains a sub-folder for Collections to house the Collection data. Using the above example, it would be:
  
  \\files\T002F\ProcessingSource\Collections
   
  
• The Workspace ID folder in the Staging pane corresponds to the Workspace ID number listed after the “AppID=” in the URL. For example, 1187585 would be the Workspace ID from this URL: kcura.relativity.one/Relativity/RelativityInternal.aspx?AppID=1187585...
  
  \\files\T002F\ProcessingSource\Collections\1187585
   
  
• The Name of the Collection from the Collections page and the Collection Artifact ID become the folder name within the Workspace ID folder. Using the above example, it would be:
  
  \\files\T002F\ProcessingSource\Collections\1187585\GCE Logistics_3819941
   
  
• The Artifact ID of the data source used becomes the sub-folder. Using the above example, they would be:
  
  \\files\T002F\ProcessingSource\Collections\1187585\GCE Logistics_3819941\3819948
  \\files\T002F\ProcessingSource\Collections\1187585\GCE Logistics_3819941\3819949
  
  In the case of grouped collections, such as Teams and Slack, there will be a folder within the collection folder corresponding to the data source type. Using Teams as an example, the file structure would be:
  
  \\files\T002F\ProcessingSource\Collections\1187585\GCE Logistics_3819941\Teams