search

bluesky / event-model

data model for event-based data collection and analysis
https://blueskyproject.io/event-model
BSD 3-Clause "New" or "Revised" License
13 stars 30 forks source link

Proposal: remove restrictions on some RunStart document keys #225

Open danielballan opened 2 years ago

danielballan commented 2 years ago

The reserved words in the RunStart document are:

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?

cjtitus commented 1 year ago

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.

prjemian commented 1 year ago

Should we take a lighter touch?

My upvote is for lighter.