-
Notifications
You must be signed in to change notification settings - Fork 7
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
What are example use cases? #11
Comments
Use cases or "user stories" are documented in this google doc. We should probably pull some of these out into the docs. |
Just following up on this, @ahwagner did you find that document useful? Do you think it's worth the effort to pull those stories out and put into the seqcol website? |
I think it would be helpful to highlight how SeqCol solves a common problem. I am more familiar with the spec now than I was 9 months ago. The user stories in that document (most of which are covered by SeqCol) get at useful functions of the specification. However, I think what really needs to happen is to put the most common envisioned use case (in a concrete scenario) front and center in the RTD site. For example, you may describe a story of adding a SeqCol identifier to a SAM header, and using that to validate that alignments refer to the same underlying genomic reference sequence set. Perhaps make the example a little more complex, and show how a group may include decoy sequences to remove contaminant sequence, and as those decoys and or reference contigs are updated over time the corresponding sequence collection identifiers remain compactly stored within the alignment file headers for quick and easy validation between alignment files. You may then describe how this is a better situation than simply using the existing That said, this might not be a problem for the average user that finds their way to the SeqCol RTD. |
The docs (from what I could find) do not provide common scenarios where collections are useful. This is probably self-evident to the team. However, for people that have less clear notions about how this might be used, it would be good to see some examples of the specification as intended by the developing team.
Am I missing this, or is this just yet to be documented?
The text was updated successfully, but these errors were encountered: