Strategy for Workbook Version Control

SWSearcy

I'm sorry if this has been addressed before, but I couldn't find a similar post.

First, we are just wrapping up our NSAW implementation and are therefore still very new to OAC. We are iteratively improving our initial core set of workbooks and are looking for a strategy to manage new versions being developed and past versions in case we find a change introduced problems. Are there any strategies others in the community would like to share on how best to go about this?

Thanks,
Scott

SteveF-Oracle

Hi,
Since a Datavisualization Archive (.DVA) is a file, you could use your own version control repository (i.e. Git,Subversion, OCI Code Repository service, CVS, etc.)

There is an Idea Lab request (enhancement), that is marked as planned, but it is not yet listed in the Public roadmap.

https://community.oracle.com/products/oracleanalytics/discussion/10249/built-in-version-control-of-catalog-objects-git-svn-bitbucket-etc

I would encourage you to up-vote and comment on it with your usecase.

Leaving this here for others to comment on their strategies.

SWSearcy

Thanks for the quick reply @SteveF-Oracle. I'll take a look at the DVA export and if that looks viable set up a GIT repository for our workbooks.

Thanks again!

SteveF-Oracle

To add, you could also make copies in your catalog with a naming convention , but the downside is your catalog may get too large if it is not kept tidy/purged periodically. This could cause issue/delays when performing snapshot exports.

The Classic catalog page has the option to export Workbooks to a catalog archive file (.catalog).
+ any REST/SOAP API, CLI options (see Developer's Guide for those).

Other comments, most welcomed.