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
Preserve the ownerUser field in Job Schema, as it checked and must be a valid SciCat user, while the owner in the Dataset schema can be any string. Naming them differently signifies this difference. Lastly, ownerUser should be a required field
I think the logic was that the ownerUser is not a required property. For instance, admin can create a job for someone and it need not be restricted to a specific user but just a group.
files
property whether changingto
job.datasetIds = ["pid1", "pid2" ]
would still work for them (seesrc/app/datasets/admin-tab/admin-tab.component.ts
)JobClass
extendsOwnableClass
, but is fieldisPublished
needed for a job?Should
ownerUser
in the Job schema be renamed toowner
(to matchDataset.owner
) and should it be required?Up to now I think the backend was backwards-compatible with v3. We should clearly indicate in the README that it requires scicat-backend-next.
_Originally posted by @sbliven in #1585
The text was updated successfully, but these errors were encountered: