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
data_session
data_groups
project
sample
scan_id
time
uid
group
owner
projections
hints
I propose to remove any validation/restrictions on:
project
sample
group
owner
The owner and group are documented as meaning associated "UNIX" owner/group. In practice, this is a rare (unused?) way to mark up ownership in Bluesky. It's often associated with proposals (or analogous entities) rather than individuals, and with some account other than a UNIX one.
We insist on sample being a string or a dict. I don't think we had a very good reason for this. Samples certainly could be numerical.
Finally, project is also unused and somewhat undefined. Individual deployments can define what this means.
I think that, with hindsight, this system is either too much validation or not enough. Should we take a lighter touch?
The text was updated successfully, but these errors were encountered:
Just want to say that I would like this to happen! I'm waiting for this so that I can re-work my beamline's run metadata. I would like to see restrictions removed on all 4 of the mentioned keys.
The reserved words in the RunStart document are:
I propose to remove any validation/restrictions on:
The
owner
andgroup
are documented as meaning associated "UNIX" owner/group. In practice, this is a rare (unused?) way to mark up ownership in Bluesky. It's often associated with proposals (or analogous entities) rather than individuals, and with some account other than a UNIX one.We insist on
sample
being a string or a dict. I don't think we had a very good reason for this. Samples certainly could be numerical.Finally,
project
is also unused and somewhat undefined. Individual deployments can define what this means.I think that, with hindsight, this system is either too much validation or not enough. Should we take a lighter touch?
The text was updated successfully, but these errors were encountered: