pipeline work

Papa tools refactoring/pipeline work

With Papa, we will be refactoring the code into three general layers:

Asset Management: This includes asset creation, renaming, utility code, etc. Also creating a specific API that future Pipeine gurus can connect to when they want to use different applications or different data structures.

Application-Specific: This involves code connecting into the asset database such as checkin/checkout, as well as code specific to an application (Alembic exporting for Maya, texture support for Mari, etc.)

Data Storage: This is code involving how data/assets/shots are stored in the pipeline. We wish to separate this code so that the asset management is not dependent on the asset management.

In addition to this refactoring, we will be restructuring how the data will be stored in our file systems, so that assets and shots will be better organized for our current file system. These changes will be built into the data storage and asset management layers.

Below are other initial improvements we want to work into the pipeline:

• Better Mari integration. Connect models from Maya into Mari.
• Integration of Mari projects over the system, so that multiple people can have access to the assets. This will be further discussed.