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
As the ''default policy specified'' for the project can be applied downstream, allow the propagation option for the ''tags'' , ''creators'', ''publications'' regarding the information already stored in the associated Assay (or higher layers if no Assay is defined, see #106). Browser access primary as it was not yet tested using API.
The text was updated successfully, but these errors were encountered:
The default policy is applied at the time of the object creation. You can change the default policy, but this will not affect the policy associated with existing objects. This is probably not the behaviour expected by most users; I didn't expect it.
Mentioned ''Default policy specified for the project applied downstream '' contains (in my case) only ''licence'' and ''sharing permission''; while creating documents and data files there are fields: tags, creators, organism, publications - each of them needs to be filled manually (FAIRDOMHub browser access) disregarding what was defined for the corresponding Assay or project (i.e. for organism)...
It can be exhaustive labor to manually set all mentioned fields for all the files.
Is there a method to add mentioned fields to default policy?
As the ''default policy specified'' for the project can be applied downstream, allow the propagation option for the ''tags'' , ''creators'', ''publications'' regarding the information already stored in the associated Assay (or higher layers if no Assay is defined, see #106). Browser access primary as it was not yet tested using API.
The text was updated successfully, but these errors were encountered: