Import project wizard

[mkolar]

Is there an existing issue for this?

• I have searched the existing issues and added correct labels.

Please describe the feature you have in mind and explain what the current shortcomings are?

Server FE wizard UI that walks first time users through the full process of importing ftrack projects to AYON.

Suggested implementation?

No response

Describe alternatives you've considered:

No response

[iLLiCiTiT]

Front end wizard suggestion

Page 1

• ftrack server url
• username
• api key

Ask server if are valid, if not tell what's wrong.

• e.g. invalid url
• invalid credentials
• API key cannot be used for import because does not have admin permissions? (NOTE this might not be true if we won't create anything in ftrack)

Possible enhancement

Expect only ftrack server and use ftrack's way how to generate api key based on currenly logged in user -> can explain more in detail. This is "nice to have" feature.

Page 2

Custom attributes. We need basic mapping of ftrack > AYON attributes.
2 columns - left with ftrack attributes (cannot be changed by user), right column comboboxes with AYON attributes and 2 more options (< Create > and < Skip >). FE must ask backend for the values as backend also pre-fills some mappings based on best guess.

Page 3

Select project/s to import. Ask server to get list of ftrack projects. I guess we expect user will select one (or more?) projects to import. When submitted backend will create event and probably return it's id in response. The progress of import will be propagated to the event -> we have to define how (same will be used for other import too).

Page 3/4

Finished, show possible warnings related to import? I don't collect them now, but there might be some, e.g. that project name is not "Project A" but "ProjectA" in AYON etc.

Questions

1. How the ftrack credentials will be handled, should FE keep ftrack credentials and pass it in each request, or BE should handle that part? Where to store them, somewhere on server?
2. At this moment, import logic expects that AYON custom attributes are in ftrack. Question is if we need to? Caviads are: We have to create the custom attributes, which requires admin permissions. If we won't create attributes, we won't have ids mapping for possible future sync. This requires some discussion because we can support all of the options, but I think all of them should be propagated to user. E.g. if he's not admin of ftrack we should warn him that we will skip some parts of import which might have issues with future sync, if he's admin we should ask if it is ok to create new custom attributes in ftrack.