...
Please go through this for the key terminology, problem statement and the solution. Please go through this for the user roles in sourcing solution.
...
Any project to seek assets for target collections has five stages as defined in the following sections. The project moves from one stage to the other stage by admin explicitly moving it to the next stage.
Note:
Sourcing orgs can create multiple projects to seek assets for the same target collection. However collections that are in “working in progress” state cannot be added as target collections.
...
When a collection is added as target collection, if there is no draft version of the collection, a draft version is automatically created by the system.
None of the changes made to the collection structure are reflected in any of the other existing projects where this collection is a target collection.
The changes made to the collection structure are reflected in the master draft version of the collection.
The collection (existing or newly created) can be modified as long as the project is in the prepare target collections stage. Once it is moved from this stage to next stage, there cannot be any modifications done.
UI Mock ups:
Project page:https://invis.io/R710G4G7Z38A
Collection creator view to create collections:
https://invis.io/RF10I1RODZAE
Stage 1: Prepare target collections
...
Stage 2: Define Scope and Schedule
...
When a project comes to this stage, a version of the collections local to this project is created. All contributions are linked to this local version only by default.
When an linked asset is approved, it is linked to the
...
master draft version of the collection.
None of the changes made to the collection structure from another project are reflected here in the local version.
Stage 3: Seek assets for target collections, review, publish
Note
When the assets are approved, they are published to consumption repo (if not already published).
Stage 4: Publish target collections
...
When a user tries to review and publish a collection, the system shows the global master draft version. Hence it will have all the assets linked to it across all the projects, not just this project.
...
Seeking assets not for any target collection consists of only three stages as described in the following sections. The flow is exactly same as that of seeking assets for target collections - without the stages of preparing target collections and publishing target collections.
Currently the asset categories that can be selected are only non-collection categories.
Framework values come from the frameworks configure in the sourcing organization.
UI Mockups: https://invis.io/J410I1KBDFGX
Stage 1: Define Scope and Schedule
...
Stage 2: Seek assets
...
, review, publish
...
Note
When the assets are approved, they are published to consumption repo (if not already published).
Improve existing assets
This is a project to improve existing assets - which consists of reviewing, updating if required and publishing. It can also include deleting existing assets.
UI Mockups: https://invis.io/2R10G4GAV4QP
Stage 1: Define Scope and Schedule
...
Stage 2: Improve assets
...
Assets published by the sourcing organization can only be added.
...
Deleting asset should retire the asset in sourcing and consumption repos.
Work in progress state of an asset
...
The asset is published for contributionconsumption
The asset is created or added as a target collection to a project and the project is moved to define scope “Seek assets” stage from prepare target collections “Define Scope and Schedule” stage
Deletion of a collection folder and collection
The folder in a collection hierarchy cannot be deleted if the collection is a target collection in any open project.
If a collection is a target collection in any open project, the collection cannot be deleted.