Summary

Within the Opus platform, Core Bundles can be created by adding custom bundle entries to a normal folder in the shared area. The custom bundle entries act as bookmarks to the original documents uploaded in the shared bundle, therefore reflecting the metadata and any work product applied to the original document. 

More information on custom bundle entries can be found here.

We've set out below our approach for creating Core Bundles alongside how to instruct Opus.  

Core Bundle Approach

Before proceeding with setting up the Core Bundle in this way we wanted flag a few points with this approach:

  1. Folder Location - The Core Bundle would be created as a top-level folder, rather than existing within the main bundle. 
  2. Custom Bundle Entries - The Core Bundle can only be comprised of custom bundle entries of documents that already exist elsewhere on the platform. This means that if a new document needs to be added to the Core Bundle that is not yet on the platform, it will need to be uploaded to the main Bundle first and then added as a copy to the Core Bundle.
  3. De-Duplicated - The Core Bundle can only contain one copy of each document (the same document cannot be added at two locations in the Core Bundle).
  4. Whole Documents - The Core Bundle would be comprised of full copies of the original documents rather than specific page ranges. 
  5. Page Numbering & Metadata - The Core Bundle cannot be sequentially paginated. The page number for each document would match that of the original file and this cannot be changed. The documents in the Core Bundle would reflect the same metadata as the original, including the Document Name. 
  6. Core Bundle/Core Tab References - If required, we can set up a Core Bundle and Core Tab field on the platform so that the documents in the Core Bundle can be assigned a secondary referencing system, for example CB/1 to CB/20.
    1. Stamp - These values would be stamped in the top right-hand corner of the page on the platform. 
    2. Secondary Reference - We are unable to set up a second Core Bundle with a further referencing system, meaning the only two referencing systems in place would be Bundle/Tab and Core Bundle/Core Tab. 
  7. Exported Documents - By default are named Bundle_Tab by the platform. For documents included in the Core Bundle this would take the format Bundle_Tab_CoreBundle-CoreTab. For example, a document at A/7 include on the Core Bundle at CB/1 would be titled A_7_CB-1. 
  8. EPE Referencing at the Hearing - All documents during the hearing can be called out using their original Bundle/Tab values. If Counsel intend to refer to the Core Bundle/Core Tab value, they will need to make this clear before reading the reference out. For example, "please can we show the document at Core Bundle CB, Core Tab 1".

Instructing Opus

For Opus to create the Core Bundle, the parties should send an Excel Index detailing: 

  1. Unique Identifier - Either the Bundle/Tab value or the Magnum ID of the documents to be included.
  2. Core Bundle & Core Tab- The Core Bundle and the Core Tab value. 
    1. Only include these additional values if the extra referencing system is required. If they are no required, the unique identifiers will need to be included in the relevant sort order. 

If a folder structure is required for the Core Bundle, we would ask that this be indicated in the email instructions, otherwise we will assume the Core Bundle is to be one straight run of documents in the folder. 

The template email should be used for ad hoc requests falling in line with the above. If the instructions fall outside this scope, a standard load file will be required to ensure tasks are actioned accurately and efficiently.

Select the relevant Excel icon to download the populated example Index template for each unique identifier. 
Bundle_Tab:Magnum ID: