allow assets to be made public / private

[sync-by-unito]

allow dashboard to set assets as either public or private

┆Issue is synchronized with this Asana task by Unito
┆Created By: Ethan Wu

[sync-by-unito]

➤ Ethan Wu commented:

where do we want to put this feature? my initial thoughts are to put it in the edit window.

what are your thoughts Kenny Hung?

also when assets are made public or made private does it consume NUM to do this?

[sync-by-unito]

➤ Sherry Chung commented:

I think Edit window is a good choice.

For setting public or not, will it also update the assettree and adding a commit for the change? If there is an additional commit in mainnet, than it'll consume NUM

cc Tammy Yang

[sync-by-unito]

➤ Kenny Hung commented:

Ethan WuTammy Yang For this task, my proposal is

add a toggle on asset detail page. How do you think?

Text: Enable Public Accessibility for Asset

description: Once enabled, anyone with the asset's Nid can easily locate and view it.

[sync-by-unito]

➤ Sherry Chung commented:

Kenny HungEthan Wu I won’t suggest to put a toggle under asset detail.

This section if for “information showing”. Not for “action taken”

If we have 2 “action taken” in 2 different place. One in top right corner for “Publish”, another under the detail information. As I know it’s not a good UX design.

And the toggle also can’t fix in one place if we put this under detail page. Because user will expand the detail information. This also cause the distraction in UX

[sync-by-unito]

➤ Sherry Chung commented:

I would suggest we think this from user’ behavior. When will user want to set the assets to public/private. Is it one-time change or we allow user to change this many times?

And where do we have similar “action taken” step for users

I’m thinking put this under either “Edit” function or “Publish” action.

We can discuss which make more sense.

[sync-by-unito]

➤ Kenny Hung commented:

Sherry Chung (cc Ethan Wu)

I think it's feasible to include this feature in either the edit function or publish drop list. My question is, what form should this feature take in these areas? Do you have a recommended approach?

[sync-by-unito]

➤ Sherry Chung commented:

Ethan WuKenny Hung I have some thought. Let’s also move this to next sprint. I’ll purpose the flow first (cc Tammy Yang )

[sync-by-unito]

➤ Ethan Wu commented:

Sherry Chung when oyu have time can you please share your thoughts on this? thanks!

[sync-by-unito]

➤ Sherry Chung commented:

Ethan WuKenny Hung I 've made some suggestion on subtask. However, since we'll have some scenario need to clarify.

I would suggest we also skip this FR in current sprint. I'll work with Tammy Yang to finalize it.

[sync-by-unito]

➤ Sherry Chung commented:

Focus on presidential election & end-to-end flow for sprint 24-01-01. I'll move this to next sprint