-
Notifications
You must be signed in to change notification settings - Fork 13
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
adding optional fields in schema #110
Merged
Merged
Conversation
This file contains 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
Collaborator
mwalzer
commented
Dec 3, 2020
•
edited
Loading
edited
- on top-level: readMe, contanctName, contactAddress
- metadata: labelName
* contactName/Address, because it is good practice to have. Esp. for the store and archive use case. (And most other PSI formats have a contact field btw.) * labelName, because in settings with multiple setQualities we need a group identifier that also lends itself to axis labels in a plot. (And it does not hurt to have that for runs, too)
cbielow
reviewed
Dec 4, 2020
cbielow
reviewed
Dec 4, 2020
cbielow
reviewed
Dec 6, 2020
bittremieux
reviewed
Dec 7, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just have some minor naming comments.
I remember that we had contact information in a qcML version way back. Apparently, just like comments, those didn't survive the transition. I don't remember why not though.
TODO:
|
as discussed, virtually all purposes will be taken over by the label and description tags
also moved schema figure pptx to figures folder
moved figure and pptx from doc to schema folder, too
takes care of #11 with up-to-date examples in v1.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.