Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

M:N relationship between Methods and Instruments #2274

Open
ramonski opened this issue Oct 13, 2017 · 1 comment
Open

M:N relationship between Methods and Instruments #2274

ramonski opened this issue Oct 13, 2017 · 1 comment

Comments

@ramonski
Copy link
Contributor

ramonski commented Oct 13, 2017

Description (from Slack)

I would like to re-visit the m:n relationship between Methods and Instruments and how results are captured in AR Analyses.
In my opinion the whole process can be simplified as follows:

  • Methods define always the possible Instruments
  • The user must therefore only select one or more Methods in the Analysis Services
  • In a specific Analysis of an AR, the user can select a Method, and the Instrument field filters accordingly (and vice versa).
  • The user can always capture the results manually by selecting a Manual option in the Instrument selection (in case if the instrument is defect)
  • If the result comes in from the instrument, the analysis contains an “Instrument Origin” flag to allow back-traceability
  • If the result was captured manually before an Instrument import, the Analysis is cloned with the instrument imported result, and the manual entry is deactivated.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant