docs(2-bm): fold the scheduling answers, keep only the PII-classification residual (SCHED)#302
Merged
Merged
Conversation
…tion residual (SCHED) Staff answered SCHED-1/2/3 (#269). Folded into the open-questions design basis: - SCHED-1: a scheduled beamtime window is immutable once users are on-site (mid-run outages are Run-level annotations, not schedule changes). - SCHED-2: CORA's earlier assumption was WRONG. The local contact is a beamline-side assignment, distinct from the proposal user list; model it as a separate beamline-assigned field, not by scanning proposal users. - SCHED-3a: badge numbers are unique and never reused, and ORCID is also required in the proposal system. Per-person identity uses ORCID (primary, cross-institution, already CORA's actor key) + badge (APS-internal join key). No (badge, time-window) compounding needed. The scheduling integration itself is a future slice; these are its inputs, recorded in the questions page design-basis note. Leaves SCHED-3b open (reframed): whether the badge is classified as deletable personal data under APS data governance still routes to data-management. Resolves SCHED-1, SCHED-2, SCHED-3a. Addresses SCHED-1/2/3 (#269). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Coverage report
This PR does not seem to contain any modification to coverable code. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Folds the SCHED staff answers (#269). I'd parked these as "blocked" earlier — they were not; only one sub-part is.
What
These are inputs to a future scheduling-integration slice (CORA has no scheduling model yet), captured as a design-basis note on the questions page. Verified the wrong SCHED-2 assumption was not encoded in the Visit/actor model — only in the question's "CORA assumes" column — so this is a docs fold, no code change.
Stays open
SCHED-3b (reframed): whether the badge is classified as deletable personal data under APS data governance still routes to data-management. That's the only genuinely external-pending part.
mkdocs --strictclean.Addresses SCHED-1/2/3 (#269).
🤖 Generated with Claude Code