-
Notifications
You must be signed in to change notification settings - Fork 79
1084 qiita pet #1207
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
1084 qiita pet #1207
Conversation
…ad to 'raw_data_tab'
|
Tests should pass now in this PR. Ready for review once all the previous PR have been reviewed and merged. |
|
@biocore/qiita-dev In this PR I've changed the interface a lot. I would suggest first downloading the code and check the interface before actually doing the code review. The idea is that if the interface needs to change, we don't waste time reviewing code that is going to change. |
|
Thanks for the heads up, will do! On (May-28-15|10:20), josenavas wrote:
|
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.
'assertItemsEqual' would be better here, since it would eliminate the sorting.
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.
Other checks in this tests depend on these 2 lists being in the same order. Leaving the sort.
qiita_db/test/test_data.py
Outdated
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.
Same as above
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.
Done
|
Few comments. |
|
The code seems to work just fine i. e. I was able to create a study and process the sequences up to an OTU table. |
qiita_db/test/test_data.py
Outdated
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.
This should be self._clean_up_files.extend([.....
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.
Good catch, done
|
This looks really nice and like @ElDeveloper said it works. Sore general comments:
Gonna check the code now. |
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 would almost prefer that this loop plus the other loop were done in a single SQL query.
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.
Thoughts?
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.
See my comment above. If we introduce finer control over the study visibility, this kind of functions will be added as User attributes.
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.
Got it.
On (May-28-15|19:21), josenavas wrote:
+filepath_types = [k.split('', 1)[1].replace('', ' ')
for k in get_filepath_types() +fp_type_by_ft = defaultdict(if k.startswith('raw_')]- lambda: filepath_types, SFF=['sff'], FASTA=['fasta', 'qual'],
- FASTQ=['barcodes', 'forward seqs', 'reverse seqs'])
+def get_accessible_raw_data(user):
- """Retrieves a tuple of raw_data_id and the last study title for that
- raw_data
- """
- d = {}
- for sid in user.user_studies:
See my comment above. If we introduce finer control over the study visibility, this kind of functions will be added as User attributes.
Reply to this email directly or view it on GitHub:
https://github.com/biocore/qiita/pull/1207/files#r31294962
|
The code looks good to me, 👍 after the comments are addressed. |
|
When showing the Would be nice if the size was fixed. The This should probably just be a bootsrap table: For some extra Yoshiki-points, we probably want to convert the dropdown that's shown in Looks good otherwise! |
|
@ElDeveloper thanks for the suggestions! I want all the extra Yoshiki-points (worth 🍻 ??). Weirdly enough, the <select class="chosen-select" id="previous-raw-data-{{pt_id}}" data-placeholder=" ">And I cannot find why is not working properly... |
|
Changes Unknown when pulling 10a69d8 on josenavas:1084-qiita-pet into * on biocore:fix-1084*. |
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.
Another thing ... there's no tests for these functions, which I think we are ok as this is a transitive step, but I wanted to highlight this in case someone else has stronger feelings about it.
|
🍻 indeed, thanks for making the changes! I think you need to activate the dropdown with JavaScript: On (May-28-15|20:22), josenavas wrote:
|
|
BTW, I'm 👍 for the most part now. @squirrelo, do you have any other comments, or others? Would be great to get this merged ASAP. |
|
I'm still meh on the accordion for Raw Data, but for the sake of having this functionality in 👍 on this code and we can do interface changes later. |
|
RE accordion: I actually like it. |


Built on top of #1206
This PR refactors the interface so now the user has to upload first the prep template before he can add the raw data. This is how the database works and this is the normal workflow when using Qiita.
This is still a work in progress PR. I had to completely rewrite some parts of the interface code, and I've still not removed the old code, as it was useful for reference.
It would be great if people can pull down this branch and check which things are missing in the interface, and which things can be improved. I'll be able to work on it tonight and tomorrow morning, so the entire interface is consistent with the new DB layout. After that, I will be able to finally add the QIIME mapping file parsing, which shouldn't impact the interface and it's only a backend change!