It's all about the answers!

Ask a question

RAM Library management and reporting

Dana Gantt (642) | asked May 05 '10, 1:58 p.m.
Is there a way got get a report or listing of which assets exist in RAM that have no association with any active library? Libraries seem to be specialized asset types with membership managed via a (hidden) asset relationship to the library. There doesn't seem to be a robust syntax for much reporting on libraries within the current product that I can find.

From a best practice standpoint, should all assets generally be unassociated from their containing library after being imported into RAM then re-associated to a library at export or versioning?


Should assets maintain an associated with a library over their useful life.

2 answers

permanent link
Gili Mendel (1.8k56) | answered May 09 '10, 10:41 a.m.
Libraries are meant to enable one to save an informational model (types, relationships, attributes ...). You can include assets in a library, but these assets (in the library) will not contain information like (change/lifecycle) history, owner, forums ... etc.

The typical reasons for assets in a library is to have some sample assets that reflect the informational model they are saved with.

Why would you want to associate all assets in libraries?

permanent link
Dana Gantt (642) | answered May 20 '10, 10:46 a.m.
Gili, thanks for the reply. We were using libraries to group assets and model constructs by communities to facilitate transportability form region to region. They seemed a logical construct to aggregate and manage asset information in addition to models. That being said, you have led to my next question.

As you pointed out, (critical) asset change/life cycle information is not migrated with the library. What is the correct process to migrate/replicate assets, models and life cycle information from repository to repository. This administrative type of activity was not covered in the RAM training we did through Rational but that is a whole different thread.

The online documentation refers to a "batch upload utility" but doesn't elaborate on its use other than to say use it to migrate. Perhaps we gravitated to us of the library facility incorrectly. Additional guidance on the preferred/correct method of migration repository info for instance to instance would be greatly appreciated.

Your answer

Register or to post your answer.