You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We were talking about setting permissions per resource type, but the current API calls don't have a way of figuring out which type a given ingested asset would belong to.
The simplest idea would be to allow users to declare a type in the ingest screen, but this leaves room for user error. Need to discuss whether this is acceptable.
The text was updated successfully, but these errors were encountered:
Confirming that it will be determined by a users home department. It's going to be used more for restrictions on asset types, so doesn't need to be super granular (film scan vs video xfer vs audio recording)
We were talking about setting permissions per resource type, but the current API calls don't have a way of figuring out which type a given ingested asset would belong to.
The simplest idea would be to allow users to declare a type in the ingest screen, but this leaves room for user error. Need to discuss whether this is acceptable.
The text was updated successfully, but these errors were encountered: