Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This article will be explaining the exact relationships between the Libraries and content, for regular libraries and cloned libraries

So first, what is a project library?

A Project Library is a dedicated space for all Collections and consequently content that are part of these collections, that is to be uploaded onto the Rumie App ( which can include the Rumie Tablet) or any Android device with the Rumie App.

In Rumie Management Center, Project Managers can have multiple projects in which they have been provided with the ability to use the same existing library or the majority of the content of the library in some other project on the fly.

This would be a real benefit to the user since initially, they would have had to create a new library from scratch and add collection populated with content one by one, which is very time-consuming. Hence, to reduce the time constraint and allow users to create a new library from an already existing library with just one click, we added this new functionality called "Cloning" We have released this functionality with the release of version 3.8.0 +.

Cloning a project library can be beneficial when wanting to create a new library which will have the same or similar content/ collection as an existing one. After a library has been cloned, it can be added under a new or existing project under the same organization that you are part of.It is important to note that once the library has been cloned, it will have a “Cloned” label which will differentiate it from the original library it was cloned from.To explain further, let's dig a little deep into what is the relationship of a library(regular library) and a cloned library in regards to the content they have.

Let's say we clone an existing library A in a newly created Project B. The regular Libray A is already existing in Project A. Both these projects (Project A and Project B)

Project A → Regular Library A

Project B → Libary A (Cloned)

Let's say, we add content to Libray A in Project A. This will not affect the Cloned library in project B. Thay are independent of each other. Similarly, if we add content to the cloned Library in project B it will not affect the already existing regular library A from which it was coned in Project A. They both are completely independent of each other. This is done so that there are no dependencies between libraries Also in a scenario when an old library is inactive in a project then a user can create a new one and clone it again to be used in different projects as per their use case





  • No labels