Libraries are document containers. Each library has its own specific configuration.
In AODocs, library administrators can create libraries by copy. Your new library is preconfigured according to an existing library. Only the configuration of the source library is created, the documents and permissions are removed.
Note: You can also:
– Create a library from scratch
– Create a library from a template
– Create a library by copying the configuration and its content by API – contact the AODocs Support team by email at email@example.com or open a ticket.
– Create a library by copying a library from your test domain to your AODocs production domain – contact the AODocs Support team by email at firstname.lastname@example.org or open a ticket.
Important: What type of library can I create by copy?
– You can create any type of library using Google Drive by copy.
– You can create Document Management libraries using other storage platforms from scratch or by copy, but not from templates.
Important: Who can create which type of library?
Google users can create any type of library. Microsoft users can create only Document Management libraries.
You must be library administrator of the library you want to copy.
In addition, you must be one of the following:
– a user defined as a library creator at the AODocs tenant level; learn more: Manage library creators
– an AODocs super administrator
– an individual user or group given the right to select an AODocs storage account; learn more: Create an AODocs storage account (Only for option)
To copy an existing library:
2. Click the Create library button.
3. In the Create library panel, click Copy library.
4. In the Copy library configuration dialog, enter the name of your new library.
Note: The library name can contain any kind of character (including special characters) but it must be unique. Two libraries can't have the same name.
5. Select the library you want to copy.
– The list of libraries displayed depends on the storage platforms activated on your domain. Learn more: Where is my content stored?
– The new library will use the same storage platform as the source library, for example, Google Drive, Google Cloud Storage (GCS) or Microsoft Azure Blob storage.
– If the source library uses AODocs managed buckets (GCS), the new library also uses AODocs managed buckets.
– If the source library uses a bucket created and managed by your organization, you can use the same bucket or select a different bucket for your new library.
6. Select an AODocs storage account for your new library.
– If only one AODocs storage account is configured on your AODocs tenant, it's selected by default.
– If several AODocs storage accounts have been configured, select the AODocs storage account you want to assign to this library from the list. This list includes only AODocs storage accounts for which the current user is included in the availability setting.
7. If available (see note in step 5), you can use the same bucket as the source library or change the URI of the bucket where you want to store all the attachments of your library.
This bucket must exist already and be correctly configured, for example, AODocs must be able to create, update, get, and delete objects in the bucket.
8. Click Create library. Your library is now created.
When you create:
- Document Management libraries and Secure Folders, you're redirected to the library homepage in the AODocs user interface
- Team Folders, you're redirected to the root folder of your library in the Google Drive interface.
– In Team Folders and Secured Folders you can switch between the AODocs interface and Google Drive.
– For large Team Folders or Secured Folders, there may be a delay in seeing the new library in Google Drive. If the creation process takes too long, the system may display a message informing you that you can't see your new library on Google Drive for the moment. You can still open your library in AODocs by selecting: Open with > AODocs.
8. Apply permissions and start using your preconfigured library.
Important: When you copy a library:
– The copied library is shared only with the library creator. All existing permissions on the source library are removed.
– The library configuration is copied in the new library. This includes document classes, folders and views.
– Documents from the source library aren't copied in the new library.
– A new library sequence ID and new document class sequence IDs are generated – learn more: What is the sequence ID?